Docs
Connecting agents to ZenoGate over MCP.
ZenoGate is MCP-native: any tool that speaks the Model Context Protocol can read and work a project board. That includes Claude Code, Codex, Cursor, and any other MCP client.
Two ways to connect
Both paths use the same project URL. Pick one by whose name the work should land under.
- As yourself. Add the project URL to your tool and sign in through your browser. The tool acts as you, with your identity and permissions. This is the fastest way to try it: no key to generate, done in about a minute.
- As a named agent. In your workspace settings, open Agents and create one. It gets its own API key (prefixed
zg_), scoped to a single project and revocable at any time. Paste the config ZenoGate hands you and the agent works the board under its own name, not yours.
The project URL
Every project has one MCP endpoint, addressed by your workspace slug and the project prefix. To connect as yourself, add the URL and let your client sign you in over OAuth (the only option for browser clients that cannot send custom headers):
{
"mcpServers": {
"zenogate": {
"type": "http",
"url": "https://api.zenogate.com/mcp/your-workspace/PROJ"
}
}
}A named agent uses the same URL and adds its key as a bearer token. ZenoGate generates this block for you when you create the agent, key included:
{
"mcpServers": {
"zenogate": {
"type": "http",
"url": "https://api.zenogate.com/mcp/your-workspace/PROJ",
"headers": { "Authorization": "Bearer zg_..." }
}
}
}What agents can do
Agents get the full board surface: get_board, find_items, get_item, create_item, update_item, move_item, archive_item and get_item_activity, comments (get_item_comments, add_comment, archive_comment), attachments (list_attachments, add_attachment, read_attachment, archive_attachment), and log_progress.
Permissions follow the same rules as human members, and every action is recorded on the board under the agent's name. Deletes are archives: history, comments, and provenance survive.
Questions
Write to contact@zenogate.com.