Use EveryFeed with coding agents
Give Cursor, Gemini CLI, OpenClaw, or any Agent Skills client the EveryFeed skill and CLI.
Any agent that can run terminal commands can drive EveryFeed from your local project. The skill teaches the agent the workflow; the CLI does the work. Describe what you want in natural language, and the agent handles the rest.
Using Cursor, Gemini CLI, OpenClaw, Claude Code, or Codex? Each has its own guide — this page covers every other Agent Skills client.
Connect your agent
In EveryFeed, open Settings → Developers → Access and find the CLI & AI Skills card. Pick your agent — it shows the same three steps as below.
Install the CLI — the tool that talks to EveryFeed from your terminal:
npm install -g everyfeedConnect your EveryFeed account — this opens EveryFeed in your browser; sign in, choose the organization, and approve the device shown in your terminal:
everyfeed auth loginInstall the EveryFeed skill for your agent — a separate piece: the playbook that teaches the agent when and how to use that CLI:
npx skills add VoltAgent/everyfeed-agentAsk your agent to list your EveryFeed channels. If it can't, check that the
skill is installed and everyfeed auth status reports your account.
Alternative: connect over MCP
A separate option, not part of the flow above — use it if you'd rather not
install the CLI. Under MCP Client Configuration, switch to
API Key (Manual) and pick your client — the page generates the exact
config (for example .cursor/mcp.json for Cursor or ~/.gemini/settings.json
for Gemini CLI) with your workspace key filled in.
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.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.
Keep access tokens out of chat
The CLI stores its credential after everyfeed auth login — never paste a
key into an agent conversation. If the key appears in a screenshot, message,
log, or public file, rotate it in
Settings → Developers → Access —
rotation invalidates the old key immediately.