Skip to main content

Hosted MCP Resource Server (OAuth — no API keys)

For a client that supports remote MCP servers with OAuth 2.1 + PKCE (e.g. Claude Code, Claude.ai connectors), connect directly to https://mcp.motorical.com instead of running the local package — no mk_live_/ak_live_/MOTORICAL_JWT to manage. The first tool call triggers a normal OAuth consent screen in the browser.

Scoped servers​

Five scoped servers, each a distinct RFC 8707 audience — a token minted for one is rejected by every other, so connecting a narrow one genuinely reduces what the client can do:

ServerURLTools
Main (everything below)https://mcp.motorical.com/v1/motorical/mcpall of the below
Transactionalhttps://mcp.motorical.com/v1/motorical_transactional/mcpsend_email, get_message, get_message_events, get_send_status
Analyticshttps://mcp.motorical.com/v1/motorical_analytics/mcplist_motor_blocks
Domainshttps://mcp.motorical.com/v1/motorical_domains/mcpdomain_add, domain_list, domain_verify, domain_check_dns
Sandboxhttps://mcp.motorical.com/v1/motorical_sandbox/mcpdeclared, not yet functional over OAuth — see below

Account-wide vs. Motor-Block-scoped​

Domain tools and list_motor_blocks are account-wide: no Motor Block selection needed, works from a brand-new account before any Motor Block exists (a Motor Block is created from a verified domain, not the reverse). Every other tool is bound to whichever Motor Block(s) the OAuth grant covers.

The domain tools each call the same Public API route documented under AI Agent Quickstart: motorical_domain_list → GET /api/public/v1/domains, motorical_domain_add → POST /api/public/v1/domains, motorical_domain_verify → POST /api/public/v1/domains/{id}/verify, motorical_domain_check_dns → POST /api/public/v1/domains/{id}/check-dns.

What's not here yet​

Not available over OAuth today: motorical_sandbox_* and motorical_web_handoff are dashboard-session-only (MOTORICAL_JWT) — sandbox creation is intentionally a CLI/dashboard-first experience, not part of this resource server. Calling them through an OAuth-connected client fails closed with an explicit error rather than a confusing 401. Use the local server for these.

Public API surface with no MCP tool yet: webhooks (create/list/test/deliveries/stats), exports, and most analytics endpoints (deliverability, reputation, anomalies, metrics, motor-block config/health, account rate-limits) are reachable via the Public Analytics API but have no MCP tool. Growing — this list shrinks as tools are added, check back or see openapi.json for the full route inventory.