Skip to main content
Connect Director to any MCP-capable agent, then talk to it in plain language — the agent picks the right tool for what you ask.

Connecting

This signs you in, mints an API key, and writes a working config into your agent (Claude Code, Cursor, Claude Desktop, or others) pointed at Director’s hosted MCP endpoint over Streamable HTTP.
A stdio transport also exists for local/manual setups: it reads DIRECTOR_API_KEY and DIRECTOR_API_URL from the environment once at process start.

Tools

All tool arguments use snake_case.

The loginCommand convenience field

Any tool response that carries a pairing code (create_login_code, or a code embedded in another response) automatically gets a loginCommand field appended — a ready-to-paste director session <code> string. Hand this directly to a teammate; they don’t need to know anything about pairing codes or environments.

Errors

A failed tool call returns MCP’s standard isError: true, with a code, message, and remediation your agent can act on — see Errors for the full list.