Claude Code

Connect Claude Code to heyeveryone.

Prepare channel drafts from the same place you work through a brief or source material.

Connect with the shared guide

Follow the connection steps below, then choose the workspaces the agent may access. These steps are imported from the maintained agent guide.

Try a draft before a schedule

Example prompt: “Draft a post from these notes for the channels connected to my workspace. Show me the content link and any channel checks. Do not schedule or publish.” Review the result in heyeveryone, then ask Claude Code to request a review if needed.

What stays with a person

An agent cannot sign off, create review links, manage tokens or change billing. Schedule requests wait in Updates for confirmation by default. A person confirms publishing by default. A workspace owner can explicitly enable auto-publish for a particular agent in a particular workspace.

Credits and access

Agent access is included in every plan. MCP and API access does not cost credits; actions that run heyeveryone’s own AI do. See the credit cost before you run them. Your agent provider may charge separately.

Connect Claude Code

claude mcp add --transport http heyeveryone https://heyeveryone.ai/mcp

Then run /mcp inside Claude Code, pick heyeveryone and authenticate.

Without a local browser (for example over SSH), run claude mcp login heyeveryone --no-browser.
The consent page warns that the redirect goes to your own computer (http://localhost:<port>/callback). That's expected.

With a personal access token (CI, headless):

export HEYEVERYONE_TOKEN=hey_pat_...
claude mcp add --transport http heyeveryone https://heyeveryone.ai/mcp \
  --header "Authorization: Bearer $HEYEVERYONE_TOKEN"

To share it with a project, use --scope project. That writes .mcp.json at the repo root. Commit it with a variable, never the token:

{
  "mcpServers": {
    "heyeveryone": {
      "type": "http",
      "url": "https://heyeveryone.ai/mcp",
      "headers": { "Authorization": "Bearer ${HEYEVERYONE_TOKEN}" }
    }
  }
}

Notes:

Scopes: local (the default) and user go in ~/.claude.json.
Claude Code's v2 runtime asks the server whether it supports MCP 2026-07-28 and uses it if so (heyeveryone does).
To force the older handshake, set MCP_PROTOCOL_NEGOTIATION=legacy.

Source: code.claude.com/docs/en/mcp.

Prepare a channel post with this agent

Questions and answers

How do I revoke access?

Disconnect the agent in Settings > Agents. Its tokens stop working at once.