Heizen MCP | Heizen

Connect Claude Code, Codex, Cursor and other MCP clients to Heizen Studio — 123 tools and 12 prompts behind a browser sign-in.

Heizen MCP is a remote Model Context Protocol server built into the Studio API. MCP clients connect over HTTP and get 123 tools and 12 prompts covering projects, bugs, stories, QA, docs, meetings and integrations — so an agent in your editor can read and update Studio without you switching to the browser.

Endpoint: https://api.studio.heizen.work/mcp

Tools ship with the API, so new ones appear the next time your client connects. There’s nothing to install and nothing to upgrade.

Get connected

claude mcp add --transport http heizen https://api.studio.heizen.work/mcp \
  -H "x-heizen-toolsets: all"
claude mcp login heizen

That’s Claude Code. Set up your client has the same three steps — add, log in, verify — for Codex, Cursor, VS Code, Gemini CLI, Claude Desktop and stdio-only clients.

In this section

Set up your client

Add, log in and verify, per harness. Read more →

Authentication

How the OAuth sign-in works and what you’re approving. Read more →

Toolsets

Which tools a connection sees, and how to narrow them. Read more →

Prompts

Twelve ready-made workflows. Read more →

Tools

What the tool surface covers, by domain. Read more →

API keys

The credential for CI and bots. Read more →

Known limits

30-second tool timeout, so LLM-backed tools (generate_requirements, generate_test_cases_from_story, resummarize_meeting) can time out on large inputs.
No elicitation. The server is stateless, so it can’t prompt you mid-call. Destructive tools are annotated instead, and your client asks for confirmation.
Single mcp scope — an access token acts as the user.
Screenshot and recorder tools aren’t available remotely — they drive a browser on your own machine.