MCP Setup

The default is a URL and no key. Copy one connector per chat. Putting both in the same mcp.json loads mutation tools next to customer text. The client discovers OAuth, opens a browser, you approve. Details in OAuth.

Reader chat:

{
  "mcpServers": {
    "feedjolt-reader": {
      "url": "https://api.feedjolt.com/mcp/reader/"
    }
  }
}

Writer chat (a different Claude project, ChatGPT chat, or Cursor workspace):

{
  "mcpServers": {
    "feedjolt-writer": {
      "url": "https://api.feedjolt.com/mcp/writer/"
    }
  }
}

Combined https://api.feedjolt.com/mcp/ still works. Treat it as legacy and unsafe.

API key (alternative)

API keys are not deprecated. If you want a static fjk_ credential, use the snippets below. Create a key at API keys.

Claude Desktop

Open ~/Library/Application Support/Claude/claude_desktop_config.json and add one connector. This is Reader:

{
  "mcpServers": {
    "feedjolt-reader": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.feedjolt.com/mcp/reader/",
        "--header",
        "Authorization: Bearer fjk_YOUR_KEY"
      ]
    }
  }
}

Writer is the same block with feedjolt-writer and https://api.feedjolt.com/mcp/writer/. Put it in a different Claude project. Do not list both in this file.

Claude Desktop doesn't talk Streamable HTTP directly - mcp-remote is a tiny stdio↔HTTP bridge that the built-in Node runtime fetches on first launch. Restart Claude Desktop. The Feedjolt tools appear in the tool picker.

Cursor

In Cursor settings → MCP, add one connector per workspace. This is Reader:

{
  "mcpServers": {
    "feedjolt-reader": {
      "transport": "http",
      "url": "https://api.feedjolt.com/mcp/reader/",
      "headers": { "Authorization": "Bearer fjk_YOUR_KEY" }
    }
  }
}

Writer is the same with feedjolt-writer and /mcp/writer/, in a different Cursor workspace.

Windsurf

Same mcp-remote bridge as Claude Desktop. Path: ~/.codeium/windsurf/mcp_config.json.

Generic MCP client

The server speaks Streamable HTTP (MCP spec 2025-03-26). POST JSON-RPC envelopes to the URL. OAuth clients send a Bearer access token after consent. API-key clients send Authorization: Bearer fjk_... (or X-API-Key).