MCP

Feedigy has an MCP server. MCP (Model Context Protocol) lets an AI tool, such as Claude, work with your Feedigy account. The AI tool can read your feeds, posts, Auto-Publishers, channels and plan usage. It can also create draft feeds and draft posts, but only after a confirm step.

The MCP server uses the same tokens and limits as the API.

Connect an AI tool

1. In Feedigy, open Settings → API and create a token. Tick only the abilities the AI tool needs (see Tools). Copy the token: Feedigy shows it once.
2. In your AI tool, add an MCP server with these settings:

Setting	Value
URL	https://api.feedigy.com/mcp
Transport	Streamable HTTP
Header	Authorization: Bearer <your token>

For example, in Claude Code:

claude mcp add --transport http feedigy https://api.feedigy.com/mcp --header "Authorization: Bearer <your token>"

The AI tool must be able to send a bearer token header. Feedigy does not use an OAuth sign-in for MCP.

The API tab in Settings appears when API access is on for your account.

Tools

The AI tool sees only the tools that its token’s abilities allow.

Tool	What it does	Ability
my_content.search	Search your feeds by title, description, type, status or tag.	feeds:read
feed.summary	Summarize one feed.	feeds:read
feed.items	List the content of one feed. Original Feed posts also need posts:read.	feeds:read
tag.list	List your tags and how often each is used.	feeds:read
post.get	Read one stored post.	posts:read
auto_publisher.list	List your Auto-Publishers with status, schedule and last result.	publishers:read
auto_publisher.show	Show one Auto-Publisher with its feeds and schedule.	publishers:read
auto_publisher.logs	Show the recent run log of one Auto-Publisher.	publishers:read
channels.list	List your connected channels. Never shows channel passwords or tokens.	channels:read
account.usage	Show your plan, credit usage and plan limits.	account:read
original_feed.create_draft	Propose a new Original Feed.	feeds:write
compose.create_draft_post	Propose a draft post in one of your Original Feeds.	posts:write
feedigy.confirm_action	Confirm a proposed draft.	the ability of the proposed tool
feedigy.action_status	Show the status of a proposal.	the ability of the proposed tool, or its read version

The MCP server cannot publish, delete, run an Auto-Publisher or use AI credits. To do those things, use Feedigy itself.

Create drafts: propose, then confirm

A write takes two steps, so nothing is saved by mistake.

1. Propose. The AI tool calls original_feed.create_draft or compose.create_draft_post. Feedigy saves nothing yet. It returns the status proposed and an action_run_id.
2. Confirm. The AI tool calls feedigy.confirm_action with that action_run_id. Feedigy creates the draft and returns it.

Rules:

• A proposal expires after 24 hours. Confirm it before then.
• Each propose call needs an operation_key: 1–255 printable ASCII characters that the AI tool chooses. If the AI tool sends the same request again with the same key, Feedigy returns the same proposal. The same key with a different request is refused.
• If the AI tool confirms the same proposal twice, Feedigy creates one draft and returns the same result both times.
• The confirming token needs every ability the proposed tool needs. A read-only token cannot confirm.
• feedigy.action_status shows the status of a proposal: proposed, running, completed, failed or cancelled. It never shows the original request.

Drafts count toward your plan limits. If you reached your feed limit, the confirm step tells you so and creates nothing.

Limits and security

• MCP calls share the per-account rate limit with the API. See API Policies.
• Feedigy removes passwords and secret-looking parameters (for example api_key or token) from links that the MCP server returns.
• To stop an AI tool, delete its token in Settings → API. Its next call is refused.
• Supported MCP protocol versions: 2025-06-18, 2025-11-25 and 2026-07-28.