Motorical MCP
There are two separate ways to give an AI agent MCP access to Motorical. They share the same underlying tool implementations, but they're different running things, authenticated differently, and deployed independently — a fix to one does not reach the other until it's separately released.
| Local server (npm package) | Hosted server (OAuth) | |
|---|---|---|
| What it is | A process you run yourself (npx, npm install -g, or a Cursor/Claude Desktop config) | An always-on service at mcp.motorical.com |
| Transport | stdio | Streamable HTTP |
| Auth | mk_live_/ak_live_ keys, dashboard JWT, or a locally-stored OAuth session | OAuth 2.1 + PKCE — no keys to manage, browser consent on first use; or none at all, for the signup handoff below |
| Install | Yes — npm install -g or npx | No — just point a compatible client at a URL |
| Tool catalogue | Every tool, including sandbox provisioning and browser handoff (listed on the local page) | 47 tools across 8 scoped servers, including production Motor Block lifecycle management (create, rename, type, domain, deactivate, delete); only the sandbox allowlist and web-handoff tools are unavailable over OAuth — sandbox status/provision/convert work over OAuth like any other account-scoped tool |
| Sandbox credentials | motorical_sandbox_provision returns the mk_live_ key directly, once | Never returned inline — credentialsAvailable:false on provision, a credentialsLocation dashboard link after motorical_sandbox_convert, which also lets you choose the production name/type and replaces the SMTP username |
No Motorical account yet? The hosted server has a dedicated, unauthenticated signup audience exposing only motorical_signup_handoff — it hands back a one-time URL that runs signup and OAuth consent in the same browser visit, with no credential of any kind returned to the agent. See Hosted MCP Resource Server for details. There's no local-server equivalent: a local install already has some credential configured, which is the scenario this bridges past.
Not sure which one you want: if your client supports remote MCP servers with OAuth (Claude Code, Claude.ai connectors), start with the hosted server — nothing to install, nothing to store, and it's the only path for a zero-credential cold start. If you need sandbox allowlisting, browser handoff, unmasked PII, or a client that only speaks local stdio servers, use the local server.