When byline isn't showing up

First check whether your AI tool supports a custom remote MCP connection on your host plan. If it does, add this endpoint using the tool's current instructions:

https://byline.fyi/api/mcp

The link is also on Sources in your byline dashboard. byline is not necessarily listed in a built-in connector directory, and host menu names vary. If your tool does not allow a custom remote MCP server, pasting the link elsewhere will not connect it.

Reauthorize a saved connection

If a saved host grant has expired, been revoked, or stopped working, use the host's connection management to remove or reconnect byline, re-add the URL if needed, and complete its sign-in and authorization flow again. The endpoint is unchanged, but keeping the saved link does not preserve authorization.

If no sign-in flow appears, check the full URL and the host's status for the connection. Re-add it and complete authorization if the host reports that it is disconnected. Host prompts and buttons are not identical across Claude, ChatGPT, Cursor, or other tools; use the host's current remote MCP instructions rather than looking for one exact label.

Connected, but no content?

Sign in to the byline account with membership in the workspace that holds the material. Ask the connected tool to list your byline workspaces and select the intended one before searching, especially on Studio. Signing in alone does not choose the right client workspace.
Check Sources for a connected source and its reading status. Create the email inbox before sending a note, or connect a supported channel; reading and profile generation happen in the background. A public URL added with Read a single URL is also queued, not immediately searchable.
Check Billing for confirmed payment and remaining reading allowance. Signup alone does not grant reading access, and exhausted limits or a payment issue can pause new reading.
Ask the AI tool explicitly to search byline for a known topic or retrieve your profile. A host may not choose to invoke byline automatically, even when the connection works.

If authorization succeeds, you have selected the right workspace, and content has finished reading but a specific query still fails, contact support with the symptom and the host name. Do not share access tokens, private drafts, or client data in a support request.