byline.fyi

fyi.bylinePublished by byline.fyiOfficial publisherv0.1.0Updated Nov 1, 2026

Brand memory for creators: your voice profile, past work and content ideas in your AI tools.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryMedia & Design

Overview

AI-generated overview

byline.fyi is a remote MCP server that gives AI tools a creator's brand memory: voice profile, past work and content ideas.

What you can do
  • No tools are listed in the manifest, so capabilities are inferred from the description.
  • The server is described as brand memory for creators, holding a voice profile, past work and content ideas.
  • It makes that material available inside connected AI tools, so assistants can draw on a creator's established voice and prior output.
  • It is a hosted remote endpoint reached over streamable HTTP with OAuth sign-in.
When to use it
Worth considering if you are a creator who wants AI assistants to write or brainstorm in your own voice, grounded in your past work and existing content ideas, rather than starting from scratch each time.
Requirements
A remote endpoint at byline.fyi over streamable HTTP; no local package or runtime is needed. An OAuth sign-in is required, and the manifest declares no environment variables or headers.
Before you install
Sign-in is via OAuth, so the server receives access tied to your byline.fyi account. Your voice profile, past work and content ideas are stored with and served by a third party; check what it retains and who can see it before connecting. No tool list is published, so what the assistant can read or change is not documented here.

Installation

In SourceWeft

  1. Open byline.fyi in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/fyi.byline%2Fbyline/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "byline-fyi": {
      "type": "http",
      "url": "https://byline.fyi/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestNov 1, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.