MyFeedInDocs
Get MyFeedIn
View .md

Any MCP client

The generic configuration

MyFeedIn is a remote MCP server over Streamable HTTP with OAuth sign-in (dynamic client registration). Any client that supports that only needs the URL.

  1. 1

    Use the server URL

    Transport: Streamable HTTP (sometimes labelled HTTP). Authentication: OAuth, no API key.

    https://mcp.myfeedin.co
  2. 2

    Pick your client's config shape

    The key that holds the URL changes from one client to the next.

    mcp_config.json
    {
  "mcpServers": {
    "myfeedin": { "serverUrl": "https://mcp.myfeedin.co" }
  }
}

    Raycast and n8n use a form: choose HTTP (n8n: HTTP Streamable) and OAuth with dynamic registration, then paste the URL. Use the stdio entry for clients that can only start a local process; it needs Node 18 or later.

  3. 3

    Sign in when the client asks

    Your browser opens on myfeedin.co. Sign in, choose the account or workspace to connect and the access level to grant.

Check it worked

Ask your assistant to call the get_connection_info tool: it answers with the MyFeedIn account it is connected to.

If something is off

mcp-remote keeps an old sign-in
Delete ~/.mcp-auth and restart your client to sign in again.
Test the server without a client
Run npx @modelcontextprotocol/inspector, choose Streamable HTTP and paste the URL.