Connecting a client
Every client uses the same URL, https://www.envpilot.dev/api/mcp, and no Authorization header. The client finds the sign-in on its own and opens your browser. For what happens next, see MCP setup.
Using an API key today? Follow Moving from an API key first.
Claude (web, Desktop, mobile, Cowork)#
- Open Customize → Connectors and choose Add custom connector. On Team and Enterprise plans an Owner adds it under Organization settings → Connectors.
- Enter
https://www.envpilot.dev/api/mcpas the server URL. Leave the OAuth client fields empty. - Select Connect and sign in to Envpilot in the window that opens.
Do not paste an Envpilot API key into an OAuth Client Secret field. That field authenticates an OAuth client during a token exchange; it never becomes the Authorization header on MCP requests.
Claude Code#
claude mcp add --transport http --scope user \
envpilot https://www.envpilot.dev/api/mcpRun /mcp in a session, choose envpilot, then Authenticate. A browser window opens for the Envpilot sign-in.
Choose the configuration scope deliberately:
--scope local(the default) keeps the server private to you in the current project.--scope projectwrites.mcp.jsonfor the team. It holds only the URL, so it is safe to commit; each person signs in for themselves.--scope usermakes it available to you across projects.
claude mcp list only confirms the server is saved. /mcp shows whether it is signed in and its tools loaded. claude mcp add does not overwrite an existing entry, so remove a key-based envpilot entry first with claude mcp remove envpilot.
Codex CLI, desktop, and IDE extension#
codex mcp add envpilot --url https://www.envpilot.dev/api/mcp
codex mcp login envpilotOr add it to ~/.codex/config.toml and run codex mcp login envpilot:
[mcp_servers.envpilot]
url = "https://www.envpilot.dev/api/mcp"Leave out bearer_token_env_var; that is the old key setup. If your Codex version has no codex mcp login, update Codex. Run /mcp to confirm the Envpilot tools are present.
Cursor#
Add the server to ~/.cursor/mcp.json, or .cursor/mcp.json for a project:
{
"mcpServers": {
"envpilot": {
"url": "https://www.envpilot.dev/api/mcp"
}
}
}Open Cursor's MCP settings. The server shows that it needs a login; select it and sign in.
VS Code#
Add the server to .vscode/mcp.json in a workspace, or to your user MCP configuration:
{
"servers": {
"envpilot": {
"type": "http",
"url": "https://www.envpilot.dev/api/mcp"
}
}
}Start the server from the MCP view and follow the sign-in prompt.
Other clients#
Any client that supports MCP authorization works: give it the URL and no header. It discovers the sign-in from the server's 401 response. A client that only supports static headers cannot connect; use the REST API or envpilot run for those jobs.
More than one organization#
If your account belongs to several organizations, pass organization (the organization's slug) to the project tools; envpilot_get_doc and envpilot_update_doc_draft take a doc id instead. The error message lists the slugs you can use.