Feeds

Use Feeds from an AI agent (MCP)

Feeds runs a remote Model Context Protocol server. An agent connected to it can estimate costs, create trackers with a monthly cap, read new posts, and register webhooks. It uses the same credits and limits as the REST API.

https://usefeeds.com/mcp

The transport is Streamable HTTP. It accepts two kinds of credential:

  • OAuth, for assistants such as Claude.ai and ChatGPT: add the URL as a custom connector and sign in. You choose what the assistant can do, and you can disconnect it under API keys in the console.
  • An API key, for developer tools: send Authorization: Bearer fm_live_…. Create a key in the console.

New accounts get 1,000 free credits when they confirm their email.

Try it without an account

A second endpoint needs no sign-in, so an agent can try Feeds first:

https://usefeeds.com/mcp/try

It has two free tools: estimate_cost, the monthly cost of following an account, and preview_posts, the 3 latest posts of an X account or LinkedIn page. Previews are limited to a few a day. To follow accounts, connect https://usefeeds.com/mcp.

Connect a client

Claude.ai, Claude Desktop, and ChatGPT

Add a custom connector with the URL https://usefeeds.com/mcp. The assistant opens Feeds to sign in; approve the access it asks for.

Claude Code

claude mcp add --transport http feeds https://usefeeds.com/mcp \
  --header "Authorization: Bearer fm_live_…"

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "feeds": {
      "url": "https://usefeeds.com/mcp",
      "headers": { "Authorization": "Bearer fm_live_…" }
    }
  }
}

VS Code (.vscode/mcp.json)

{
  "servers": {
    "feeds": {
      "type": "http",
      "url": "https://usefeeds.com/mcp",
      "headers": { "Authorization": "Bearer fm_live_…" }
    }
  }
}

Keep the key out of shared repositories. Clients that support OAuth can omit the header and sign in instead.

Tools

Tool What it does Credits
get_account The organization of the key and its balance Free
estimate_cost Credits a month for one tracker Free
list_trackers Every tracker, with its cap and spend this month Free
create_tracker Follows an account at an interval, with a required monthly cap Setup, then each check and post
update_tracker Pauses, resumes, or changes a tracker Free
delete_tracker Deletes a tracker Free
get_posts Stored posts of a tracker, newest first Free
query_account Latest posts of any account, once As a one-off query
list_webhooks Webhook endpoints Free
create_webhook Sends each new post to an HTTPS URL Free

Credits per operation are on the pricing page. Each tool’s description also lists them, so the agent can tell you the cost before it acts.

Spend and safety

  • create_tracker requires monthlyBudgetCredits. A tracker stops checking for the rest of the month when it reaches its cap.
  • Read-only tools carry the MCP readOnlyHint annotation, and delete_tracker carries destructiveHint, so clients can ask you before a change.
  • Posts are written by third parties. The server returns them in an untrustedPosts field, and tells the agent to treat their text as data, never as instructions.
  • The MCP server shares the API’s rate limit of 120 requests a minute per organization.

Discovery

The server card is at /.well-known/mcp/server-card.json. OAuth metadata is at /.well-known/oauth-protected-resource/mcp and /.well-known/oauth-authorization-server; /auth.md explains both kinds of credential. The API catalog at /.well-known/api-catalog and /llms.txt list the server and the docs.