Feeder’s MCP server lets Claude, ChatGPT, Codex, Cursor, and other Model Context Protocol clients read your feeds, search posts, and manage collections, straight from your account. Here’s how to connect it.<\/p>\n
https:\/\/feeder.co\/mcp<\/code><\/li>\n<\/ul>\nFor most clients there are no tokens to copy. However you connect, your client sends you to Feeder to log in and approve access.<\/p>\n
One URL to remember.<\/strong> https:\/\/feeder.co\/mcp<\/code> is the only address most clients need. When a setup screen asks for a server URL, an MCP URL, or an endpoint, that is the one to paste. The Authorization URL and Token URL further down this page are different addresses for a different job, and using one of those as the server URL is the most common reason a connection never reaches the approval screen.<\/p>\nOption 1: Paste the server URL<\/h2>\n
Best for clients with a built-in connector screen, like Claude and ChatGPT.<\/p>\n
\n- Open your client’s connectors or integrations settings.<\/li>\n
- Add a custom connector and paste
https:\/\/feeder.co\/mcp<\/code>.<\/li>\n- Log in to Feeder when prompted and approve access.<\/li>\n<\/ul>\n
In Claude this lives under Settings > Connectors. In ChatGPT it’s under Settings > Connectors too, and you may need to turn on developer mode first. Custom connectors are a paid feature in both apps.<\/p>\n
Option 2: Paste the config snippet<\/h2>\n
Best for Claude Desktop and Cursor. Add this to your client’s MCP config file:<\/p>\n
{\n \"mcpServers\": {\n \"feeder\": {\n \"url\": \"https:\/\/feeder.co\/mcp\"\n }\n }\n}<\/code><\/pre>\nYour client will prompt you to log in to Feeder and approve.<\/p>\n
Option 3: Connect from the command line<\/h2>\n
Best for Codex CLI and Claude Code, where a single command wires up Feeder.<\/p>\n
Codex CLI<\/h3>\ncodex mcp add feeder --url https:\/\/feeder.co\/mcp\ncodex mcp login feeder<\/code><\/pre>\nThe login command opens Feeder in your browser, so you can sign in and approve access.<\/p>\n
Claude Code<\/h3>\nclaude mcp add --transport http feeder https:\/\/feeder.co\/mcp<\/code><\/pre>\nThen type \/mcp<\/code> inside Claude Code to log in to Feeder and approve.<\/p>\nAdvanced: create a Client ID and secret<\/h2>\n
Most clients register themselves when you paste the server URL, so you can skip this section entirely. It is here for the few that can’t, like Elvex and Azure AI Foundry, which ask for a Client ID and Client Secret up front. For those, generate a pair in Feeder and paste them in.<\/p>\n
\n- In Feeder, open your MCP settings under Settings > Account and expand Advanced.<\/li>\n
- Under Create a Client ID and secret, paste the Redirect URL your client uses, if you have it. Your client’s setup screen shows it. Add a name if you like.<\/li>\n
- Select Create Client ID and secret.<\/li>\n
- Copy the Client Secret right away. For your security, Feeder shows it only once. The Client ID stays available.<\/li>\n<\/ul>\n
The pair you create uses client_secret_basic<\/code>, so that is the answer when a client asks how it should send its credentials.<\/p>\nThe Redirect URL is optional. If your client only shows it once the Client ID and secret are saved, leave the field empty and add the URL afterwards. A pair without a real Redirect URL can’t finish an authorization, so it is worth coming back to. Every pair you create is listed under Your Client IDs in the same Advanced section, where you can edit its redirect URL or delete it.<\/p>\n
Some clients ask for these two addresses by name. Fill one in only where a field asks for it, and keep using the server URL above everywhere else:<\/p>\n
\n- Authorization URL:
https:\/\/feeder.co\/1\/oauth2\/authorize<\/code><\/li>\n- Token URL:
https:\/\/feeder.co\/1\/oauth2\/token<\/code><\/li>\n- Scope:
mcp<\/code><\/li>\n<\/ul>\nEach Feeder account needs its own Client ID and secret, so create a pair per account.<\/p>\n
Azure AI Foundry<\/h3>\n
Foundry only shows you its redirect URL once the connection is saved, so there is nothing to paste into Feeder up front. Do it in this order:<\/p>\n
\n- In Feeder, create a Client ID and secret with the Redirect URL field left empty. Copy both values.<\/li>\n
- In Foundry, add the MCP tool with the server URL
https:\/\/feeder.co\/mcp<\/code> and choose OAuth. Paste the Client ID and Client Secret, set the Auth URL and Token URL to the ones above, and set the scope to mcp<\/code>. Foundry marks the Client Secret as optional, but Feeder needs it. If there is a Refresh URL field you can leave it empty, Feeder’s access tokens last a year.<\/li>\n- Save the connection, then copy the Redirect URL Foundry shows. It looks like
https:\/\/global.consent.azure-apim.net\/redirect\/<\/code> followed by an ID.<\/li>\n- Back in Feeder, find the pair under Your Client IDs, paste that address into its Redirect URL field, and select Save.<\/li>\n
- Connect in Foundry and approve access when Feeder asks.<\/li>\n<\/ul>\n
If Foundry hands you a new redirect URL later, for example after you edit the connection, paste the new one into Feeder the same way.<\/p>\n
If your client never reaches the approval screen<\/h2>\n
When the login never opens, or your client loops without ever asking you to approve, it is almost always the server URL.<\/p>\n
\n- Check that your client has
https:\/\/feeder.co\/mcp<\/code>, and not the Authorization URL or the Token URL.<\/li>\n- Remove the Feeder server from your client, add it again, and start the login. In Codex CLI that is
codex mcp remove feeder<\/code>, then the two commands in Option 3. In Claude Code, claude mcp remove feeder<\/code>, then add it again. In Claude or ChatGPT, delete the connector and add it back.<\/li>\n- If you created a Client ID and secret without a Redirect URL, add the real one under Your Client IDs before you try again.<\/li>\n<\/ul>\n
Your client may also tell you Feeder needs a Client Secret. It doesn’t. Claude, ChatGPT, Codex, Claude Code, and Cursor all register themselves from the server URL alone, and none of them needs anything from the Advanced section.<\/p>\n