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 |
| Install | Yes — npm install -g or npx | No — just point a compatible client at a URL |
| Tool catalogue | All 16 tools, including sandbox provisioning and CLI→browser handoff | 10 tools across 5 scoped servers; sandbox and web-handoff are not available over OAuth |
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. If you need sandbox provisioning, CLI-driven onboarding, or a client that only speaks local stdio servers, use the local server.