Connect Feeder to your AI assistant with MCP

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.

What you’ll need

• A Feeder Plus, Professional, or Enterprise plan.
• An AI client that supports MCP.
• The server URL: https://feeder.co/mcp

For most clients there are no tokens to copy. However you connect, your client sends you to Feeder to log in and approve access.

One URL to remember. https://feeder.co/mcp 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.

Set up your client

Claude

On the web, desktop or mobile:

• Open Customize > Connectors and select Add custom connector.
• Paste https://feeder.co/mcp and add it.
• Claude sends you to Feeder. Log in and approve access.

On a Free Claude plan you can add one custom connector. On a Team or Enterprise plan, an Owner adds Feeder under Organization settings > Connectors first, and then each member connects their own Feeder account.

ChatGPT

• In ChatGPT, open the Plugins directory and search for Feeder.
• Select Feeder, then add it.
• ChatGPT sends you to Feeder. Log in and approve access.

There’s no developer mode to turn on and no server URL to paste.

Claude Code

claude mcp add --transport http feeder https://feeder.co/mcp

Then type /mcp inside Claude Code to log in to Feeder and approve.

Codex CLI

codex mcp add feeder --url https://feeder.co/mcp
codex mcp login feeder

The login command opens Feeder in your browser, so you can sign in and approve access.

Cursor and other clients

If your client has a connectors or integrations screen, add a custom connector there and paste https://feeder.co/mcp. If it reads a config file instead, add this to it. In Cursor that file is ~/.cursor/mcp.json.

{
  "mcpServers": {
    "feeder": {
      "url": "https://feeder.co/mcp"
    }
  }
}

Your client will prompt you to log in to Feeder and approve.

What your assistant can do

Every tool works on your own account, and only on what you already see in Feeder.

Tools that only read

• list_feeds: the feeds you follow, with unread counts.
• list_folders: your folders and how they nest.
• get_posts: the latest posts from a feed, a folder or everything, with unread and starred filters.
• expand_post: the full text of one post.
• search_posts: full text search across your posts, by feed, folder, date or read status.
• list_collections: your collections.
• search_feeds: finds the RSS feeds for a website or a name, so you can follow them. Given a website address, Feeder visits that page to look for its feeds.

Tools that change your account

• add_feed: follows a feed, in the folder you pick.
• create_folder: creates a folder.
• add_feed_to_folder: moves a feed into another folder.
• add_to_collection: saves a post to one of your collections.
• mark_feed_read, mark_folder_read and mark_all_read: mark one feed, one folder or everything as read. This can’t be undone, so most assistants ask you first.

Advanced: create a Client ID and secret

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.

• In Feeder, open your MCP settings under Settings > Account and expand Advanced.
• 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.
• Select Create Client ID and secret.
• Copy the Client Secret right away. For your security, Feeder shows it only once. The Client ID stays available.

The pair you create uses client_secret_basic, so that is the answer when a client asks how it should send its credentials.

The 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.

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:

• Authorization URL: https://feeder.co/1/oauth2/authorize
• Token URL: https://feeder.co/1/oauth2/token
• Scope: mcp

Each Feeder account needs its own Client ID and secret, so create a pair per account.

Azure AI Foundry

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:

• In Feeder, create a Client ID and secret with the Redirect URL field left empty. Copy both values.
• In Foundry, add the MCP tool with the server URL https://feeder.co/mcp 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. 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.
• Save the connection, then copy the Redirect URL Foundry shows. It looks like https://global.consent.azure-apim.net/redirect/ followed by an ID.
• Back in Feeder, find the pair under Your Client IDs, paste that address into its Redirect URL field, and select Save.
• Connect in Foundry and approve access when Feeder asks.

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.

If your client never reaches the approval screen

When the login never opens, or your client loops without ever asking you to approve, it is almost always the server URL.

• Check that your client has https://feeder.co/mcp, and not the Authorization URL or the Token URL.
• Remove the Feeder server from your client, add it again, and start the login. In Codex CLI that is codex mcp remove feeder, then the two commands under Codex CLI. In Claude Code, claude mcp remove feeder, then add it again. In Claude, delete the connector and add it back. In ChatGPT, remove the Feeder plugin and add it again.
• If you created a Client ID and secret without a Redirect URL, add the real one under Your Client IDs before you try again.

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.

Still stuck? Write to us at support@feeder.co and tell us which client you’re using and what the error says.

Manage connected apps

Open Feeder and go to Settings > Account to see everything you’ve connected, and disconnect any app in a click.

What to ask

Once you’re connected, try:

• “What are the headlines from my Tech folder today?”
• “Find an RSS feed for The Verge and add it to my Mornings folder.”
• “Save the three most interesting unread posts to my Read Later collection.”