FeedNest

What the FeedNest MCP server does

The FeedNest MCP server connects an AI assistant to sources selected by the user, including RSS feeds, YouTube channels, podcasts, and Google News sources. It exposes feed content and personal reading data through MCP, allowing an assistant to search articles, read full content, and work with annotations without leaving the configured client.

The service is suited to workflows such as briefing generation, comparing coverage across subscribed sources, finding articles on a topic, and following developing stories. It can also manage the user's reading workflow by changing read status, saving articles or URLs, and organizing content with tags.

How it works

FeedNest provides a remote MCP endpoint at https://mcp.feednest.com using Streamable HTTP. Clients authenticate either through an OAuth connection supported by the client or with a FeedNest developer API key sent as a bearer token. A client sends natural-language requests to the connected model, which selects the relevant MCP tool and returns feed or article data.

Article queries can use views such as the newsfeed, a specific feed or folder, tagged items, highlighted items, or noted items. Search, sorting, date ranges, unread-only filtering, and result limits are available where supported. When an RSS item is incomplete, the extraction tool can retrieve fuller content from its original URL.

Setup and configuration

A FeedNest account is required. OAuth connections are available for supported apps, including ChatGPT and Claude, without an API key. API-key configurations use a key created in FeedNest under Settings → Developer API; the README states that this option requires a Pro subscription.

For remote MCP clients, configure https://mcp.feednest.com and send Authorization: Bearer <key>. Codex, Cursor, Windsurf, Cline, Gemini CLI, and Claude Code each use client-specific configuration fields. Claude Desktop can use the connector, or connect through the mcp-remote bridge because its direct configuration runs stdio servers. Stdio-only clients can likewise use that bridge.

Tools and capabilities

The FeedNest MCP server supports these operations:

• List articles by feed, folder, tag, highlight, note, or general newsfeed view.
• Retrieve full article content, highlights, notes, and reading time.
• Extract article content from an original URL when an RSS item is truncated.
• Mark individual or filtered groups of articles as read or unread.
• Save or unsave articles and save external URLs for later.
• List feeds, folders, tags, saved items, recently read articles, and public output feeds.
• Create and delete tags, then add or remove tags on articles.
• Add, update, retrieve, and delete article notes and highlights.
• Return reading streaks, reading time, unread totals, and related statistics.

Limitations and notes

OAuth and API-key access have different plan requirements. On the Free plan, OAuth-connected apps can read feeds and articles with a stated limit of 20 requests per hour. The README says Plus and Pro plans add saving, tagging, highlighting, notes, and read-status changes for those connections; API-key access requires Pro.

The FeedNest MCP server is focused on the sources and content available in the user's FeedNest account. Gemini CLI supports the remote connection, while the README notes that Gemini's web interface does not support external MCP servers. Grok access is described for the xAI API or SDK, not the grok.com chat interface.