Connecting your AI tool

Connecting takes one address and one sign-in.

The server address

https://mcp.automo.build/mcp

It is a Streamable HTTP server.

Setup by client

• Claude Code: run /plugin marketplace add Desygner/automo-build-mcp, then /plugin install automo-build.
• Claude.ai: Settings, Connectors, Add custom connector, then paste the address.
• Cursor: install the Automo Build plugin, or run npx automo-build connect cursor.
• Codex: run npx automo-build connect codex.
• Cline: add the JSON below to cline_mcp_settings.json.
• Any MCP client: add the address as a remote Streamable HTTP server.

{
  "mcpServers": {
    "automo-build": {
      "type": "streamableHttp",
      "url": "https://mcp.automo.build/mcp"
    }
  }
}

Signing in

The first time your tool uses the server, it opens your browser to sign in. There is no API key and no client registration.

You sign in to Automo Build and see one consent screen. It shows which app is asking and two groups of permission: Read and Act.

Access tokens last an hour and refresh automatically. They are scoped and can be revoked.

Permission scopes

Each token carries named OAuth scopes. A client can request only the scopes it needs. The list is also published as scopes_supported in the server's protected-resource metadata at https://mcp.automo.build/.well-known/oauth-protected-resource (mirrored at https://docs.automo.build/.well-known/oauth-protected-resource).

• workspaces:read — see your workspaces and switch between them.
• projects:read, projects:write — read projects, branches and diffs; create, wake and merge projects and branches.
• prompts:write — send prompts to a project's agents and builders.
• sessions:read, sessions:write — read and continue agent sessions.
• reviews:read, reviews:write — read reviews; run, approve, promote or cancel them.
• playbooks:read, playbooks:run, playbooks:write — read, run and save playbooks.
• deployments:read, deployments:write — read deployment history; propose a publish (a person still approves it).
• chat:read — read a project's chat.
• billing:write — billing-related actions on your workspace.

For read-only access, request only the :read scopes, or use the /mcp/observe address.

Managing access

Active connections appear on the Integrations page in the app, where you can revoke them.

Personal access tokens are a separate thing, for your own scripts. They are not used for MCP.