MCP connections

MCP works in two directions: external agents can query Iterel, and Iterel can inject scoped tools into a Build-engine run.

Open beta guideJump to first section

External agents connect to Iterel

The project MCP server exposes permitted context, tasks, frames, Project Map data, and saved artifacts to tools such as Claude Code, Cursor, Zed, and Claude Desktop. Manage keys from project integrations.

Iterel connects tools to engines

For outbound Build runs, Iterel starts a short-lived loopback MCP gateway scoped to one task and project. Supported engine adapters receive that endpoint automatically. The token dies when the run ends.

Keep the directions separate

The project MCP key is for an external client connecting to Iterel. The run gateway is for Iterel's child engine process. The engine's own vendor subscription token is a third, parallel authentication channel that Iterel does not extract or reuse.