Use EveryFeed with Claude

claude.ai and Claude Desktop connect over MCP — the standard way AI apps plug into outside tools, so there is nothing to install. Claude Code can instead run the EveryFeed CLI through the skill. Either way, once connected you do not need to call the tools yourself: describe what you want to Claude in natural language. (Not sure which connection fits your setup? See which connection do I need.)

Pick the flow that matches how you use Claude — you need only one of the two.

Connect claude.ai or Claude Desktop

In EveryFeed, open Settings → Developers → Access. Under MCP Client Configuration, keep OAuth (Recommended) selected and copy the MCP server URL.

In Claude, open Settings → Connectors → Add custom connector, paste the URL, and choose Connect. Sign in to EveryFeed and approve access for the workspace you want — no API key is required.

Start a new conversation and ask Claude to list your EveryFeed channels. If the tools are unavailable, reconnect and approve access again.

Connect Claude Code

In EveryFeed, open Settings → Developers → Access and find the CLI & AI Skills card. Pick Claude Code — it shows the same three steps as below.

Install the CLI — the tool that talks to EveryFeed from your terminal:

npm install -g everyfeed

Connect your EveryFeed account — this opens EveryFeed in your browser; sign in, choose the organization, and approve the device shown in your terminal:

everyfeed auth login

Install the EveryFeed skill for Claude Code — a separate piece: the playbook that teaches Claude Code when and how to use that CLI:

npx skills add VoltAgent/everyfeed-agent

Start a new Claude Code session and ask it to list your EveryFeed channels. If it can't, check that the skill is installed and everyfeed auth status reports your account.

Alternative: Claude Code over MCP

A separate option, not part of the flow above — use it if you'd rather not install the CLI. Switch MCP Client Configuration to API Key (Manual), pick Claude Code, and copy the ready command:

claude mcp add --transport http everyfeed \
  "https://api.everyfeed.ai/mcp" \
  --header "Authorization: Bearer YOUR_EVERYFEED_TOKEN"

Verify the connection with claude mcp list.

Can't send an Authorization header at all (some CI systems and hosted runners)? The CI / Remote Servers block of the same card offers a key-in-URL endpoint (…/mcp/<key>) — the key is part of the URL, so treat the whole URL as a secret.

Running in CI or on a remote server

No browser on the machine? The CI / Remote Servers tab of the CLI & AI Skills card shows the same three steps with one swap: instead of everyfeed auth login, authenticate with your workspace API key as an environment variable:

export EVERYFEED_API_TOKEN="YOUR_EVERYFEED_TOKEN"

What to ask

List my connected channels in EveryFeed.

Prepare a LinkedIn launch post in EveryFeed. Do not publish it yet.

Adapt this copy for LinkedIn and X, then validate both drafts: [paste copy]

Schedule the approved post for tomorrow at 10:00 in Europe/Istanbul.

Show me the status of my recent EveryFeed posts.

Generate an image for this post in EveryFeed and attach it: [describe the image].

Import this image or MP4 into EveryFeed from a URL and attach it: [paste URL].

Generate a short video in EveryFeed for this post, then attach it once ready.

Turn this into a 3-post thread for X in EveryFeed, then validate it.

Find the next available slot and schedule the approved post there.

For a client-specific request, include the client group name. For scheduling, include an exact date, time, and time zone whenever possible. AI image and video generation run only after you confirm and use your organization's AI allowance; video is prepared in the background and attached when it is ready.

Review and approval

Claude resolves the connected channels, checks each provider's rules, and validates the draft. Before creating an immediate or scheduled post, it shows the destination channels, copy, media, publishing mode, exact time and time zone, and short-link behavior.

Nothing is created until you explicitly approve that exact review. If anything changes, Claude validates the new version and asks for a fresh approval.