FeedNest MCP Server

Your sources. Not the whole web. Ask your AI about your feeds - it already knows.

ChatGPT searches the internet. Perplexity crawls billions of pages. When you ask about your industry, your interests, your world - they give you everything except what matters.

FeedNest is different. Your AI works exclusively with the sources you choose: the blogs you trust, the publications you follow, the experts you believe in. No algorithmic noise. No black-box results. Intelligence grounded in your world.

This MCP server gives any AI assistant - ChatGPT, Codex, Claude, Gemini, Grok, Cursor, Windsurf, Cline, Le Chat, and more - direct access to your feeds, articles, highlights, notes, and tags through natural language.

What Your AI Can Do

Just ask. Your AI handles the rest.

• Morning briefings - Wake up to a summary of everything that happened overnight across your feeds
• Compare coverage - See how different sources report the same story, side by side
• Spot trends early - Your AI detects emerging patterns before they hit mainstream
• Deep-dive any topic - Get a comprehensive synthesis from every source you follow
• Track developing stories - Follow a narrative as it evolves across all your feeds
• Instant search - Find any article across all your sources in seconds
• Highlights and notes - Save what matters and annotate with your own thoughts
• Audio briefings - Turn any article or summary into something you can listen to

Quick Start

Prerequisites

1. A FeedNest account with a Pro subscription
2. An API key - generate one from Settings → Developer API in your dashboard

ChatGPT

Option A: Web UI (OAuth - recommended)

1. Go to Settings → Apps & Connectors → Advanced and enable Developer Mode
2. Go to Settings → Apps → Create. Name it FeedNest and set the URL to https://mcp.feednest.com
3. ChatGPT will redirect you to FeedNest - log in and authorize

No API key needed. ChatGPT handles the OAuth flow automatically.

Option B: Responses API

Include FeedNest as an MCP tool in your API request:

{
  "type": "mcp",
  "server_url": "https://mcp.feednest.com",
  "server_label": "feednest",
  "authorization": "fn_live_YOUR_API_KEY"
}

Codex

Option A: Plugin (recommended)

Open the Codex plugin directory and search for FeedNest:

codex
/plugins

The plugin bundles skills, MCP config, and brand assets in one install. See the Codex plugin README for local installation options.

Option B: MCP in config.toml

Add to ~/.codex/config.toml:

[mcp_servers.feednest]
url = "https://mcp.feednest.com"
bearer_token_env_var = "FEEDNEST_API_KEY"

export FEEDNEST_API_KEY="fn_live_YOUR_API_KEY"

Or via CLI:

codex mcp add feednest --transport http https://mcp.feednest.com

Claude

Claude.ai Web (OAuth - recommended)

1. Click profile icon → Settings → Connectors → Add custom connector
2. Set Name to FeedNest, Remote MCP server URL to https://mcp.feednest.com
3. Leave OAuth Client ID and Secret empty. Click Add and authorize.

Claude Code

claude mcp add --transport http feednest https://mcp.feednest.com \
  --header "Authorization: Bearer fn_live_YOUR_API_KEY"

Add -s user for global access across all projects.

Claude Desktop (requires bridge)

Claude Desktop only supports stdio-based servers. Use the mcp-remote bridge:

{
  "mcpServers": {
    "feednest": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.feednest.com",
        "--header", "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer fn_live_YOUR_API_KEY"
      }
    }
  }
}

Config path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows), or ~/.config/Claude/claude_desktop_config.json (Linux).

Cursor

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for global):

{
  "mcpServers": {
    "feednest": {
      "url": "https://mcp.feednest.com",
      "headers": {
        "Authorization": "Bearer fn_live_YOUR_API_KEY"
      }
    }
  }
}

Tip: Cursor supports env var interpolation: "Bearer ${env:FEEDNEST_API_KEY}". Do not add a "type" field - Cursor auto-detects from the "url" key.

Le Chat (Mistral)

Available on all plans, including the free tier.

1. Go to Sidebar → Intelligence → Connectors
2. Click + Add Connector → Custom MCP Connector
3. Set Name to FeedNest, Server URL to https://mcp.feednest.com
4. Set Auth type to API Token Authentication, Authorization to Bearer fn_live_YOUR_API_KEY

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "feednest": {
      "serverUrl": "https://mcp.feednest.com",
      "headers": {
        "Authorization": "Bearer fn_live_YOUR_API_KEY"
      }
    }
  }
}

Important: Windsurf uses "serverUrl" (not "url"). Using the wrong key causes a silent failure.

Cline

In VS Code, open Cline extension settings → MCP Servers configuration (JSON):

{
  "mcpServers": {
    "feednest": {
      "type": "streamableHttp",
      "url": "https://mcp.feednest.com",
      "headers": {
        "Authorization": "Bearer fn_live_YOUR_API_KEY"
      }
    }
  }
}

Critical: The "type": "streamableHttp" field is mandatory for Cline. Without it, custom headers may fail silently and authentication won't work.

Gemini CLI

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "feednest": {
      "httpUrl": "https://mcp.feednest.com",
      "headers": {
        "Authorization": "Bearer fn_live_YOUR_API_KEY"
      }
    }
  }
}

Note: Gemini CLI uses "httpUrl" (not "url"). The "url" field is reserved for SSE transport. CLI only - gemini.google.com does not support external MCP servers.

Grok (xAI)

Available through the xAI API/SDK only, not from the grok.com chat UI.

curl https://api.x.ai/v1/responses \
  -H "Authorization: Bearer $XAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "grok-3",
    "tools": [{
      "type": "mcp",
      "server_url": "https://mcp.feednest.com",
      "server_label": "feednest",
      "authorization": "Bearer fn_live_YOUR_API_KEY"
    }],
    "input": "What are my unread articles?"
  }'

Any other MCP client

Any client supporting Streamable HTTP can connect using:

• URL: https://mcp.feednest.com
• Header: Authorization: Bearer fn_live_YOUR_API_KEY

For stdio-only clients, use the mcp-remote bridge:

{
  "mcpServers": {
    "feednest": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.feednest.com",
        "--header", "Authorization:Bearer fn_live_YOUR_API_KEY"
      ]
    }
  }
}

Tools (26)

Articles

Read Status

Saving

Feeds & Structure

Tagging

Highlights

Read the full README on GitHub →