Agents
Work with your agents in the same workspace.
Bring drafts into the same workspace where you review, schedule and follow published posts.
Choose the workspaces it can reach
Connect a supported client and grant access to the relevant workspaces. Disconnect it in Settings > Agents to revoke its tokens.
Get the work back as a link
Ask the agent to draft, adapt or request review. Piece and post results include a link to the content page, so you can inspect what changed.
Treat approval as a state
If sign-off is required, a comment is not enough: the current version needs approval. An agent can request review, but cannot sign off or create the review link.
Keep requests visible
Proposed schedules wait in Updates for a person by default. A person confirms publishing by default. A workspace owner can explicitly enable auto-publish for a particular agent in a particular workspace.
Understand the cost
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.
Choose your agent
- Claude
- ChatGPT
- Claude Code
- Codex
- Cursor
- Gemini CLI
- VS Code
- Grok
Connection guidance; compatibility not yet confirmed.
Connection details
- MCP server
- https://heyeveryone.ai/mcp
- API reference
- OpenAPI document
Check the connection
Ask your agent to list the workspaces it can access, then draft a post without scheduling it. Open the returned content link and review the draft.
Troubleshooting
- 401 with `WWW-Authenticate: Bearer resource_metadata=...`: the client has no valid token. Chat apps start sign-in from this. A CLI with a personal access token means the token was revoked or mistyped.
- 403 "Requests from the origin ... are not allowed": a browser-based client on a plain-http, non-local page. Serve it over https or from
localhost. - The consent page says "unverified" or warns about a local redirect: this is normal for CLIs (Claude Code, Codex, Gemini CLI, Inspector), which receive the sign-in on your own computer.
- A redirect URI is refused: heyeveryone accepts
httpsredirect URIs, andhttponly onlocalhost,127.0.0.1or[::1](any port). Custom schemes such ascursor://are refused; use a personal access token with such clients. None of the clients above needs one. - 429 "Too many requests. Try again in N seconds.": a rate limit (see "Rate limits"). Wait the
Retry-Afterseconds; a loop that keeps calling is the usual cause. - Tools you expected are missing: agents never see people-only tools (confirming schedules, sign-off, tokens, billing). Calling one by name gets the MCP error "Unknown tool".