AI & MCP · Agent-native email

Give your agent a sending stream, not your production credentials.

Motorical runs hosted Model Context Protocol servers. An agent in Claude or Cursor can provision an isolated sandbox, send a test message, verify a domain, and read that Motor Block's own delivery analytics — without touching the account you send production mail from.
Sandbox before DNS

The sandbox gives you a Motor Block on *.sandbox.motorical.com with outbound locked to an allowlist. Send real mail to yourself before you own a domain, then convert onto a verified one.

Dry run by default

Sends default to a dry run, and a real send needs a second, explicit confirmation — two signals, so an agent cannot mail your users by accident. Destructive Motor Block actions are confirmation-gated too.

Scoped servers, not one master key

Separate servers cover sending, analytics, domains, sandbox, webhooks and Motor Block management. Connect only what the task needs; access is granted per Motor Block.

The agent can read the spec

The server registers the live OpenAPI document as an MCP resource, alongside llms.txt. Your agent works from the current contract instead of guessing at it.

Per-block analytics, not a shared feed

Message timelines and delivery events are scoped to the Motor Block the agent is working in. Debugging one project never means reading another project’s traffic.

Domain setup is a tool call

The agent adds a domain and gets the exact DNS records back, verifies ownership, and checks DNS until the domain is send-ready.

How it works

1

Connect

Add the hosted server to your agent and sign in with OAuth. There is nothing to install.

2

Provision

Ask the agent to provision a sandbox — an outbound-locked Motor Block with its own credentials.

3

Send

A dry run validates the payload. Confirm to actually deliver, then read the message timeline back.

4

Graduate

Add your domain, verify it, check DNS, and convert the sandbox Motor Block onto it.

Connect in one line

Claude Code shown — other MCP clients take the same URL. The full, always-current tool catalogue for every server is in the MCP docs.

claude mcp add --transport http motorical https://mcp.motorical.com/v1/motorical/mcp

Frequently asked questions

Any MCP client that supports remote servers with OAuth — Claude and Cursor are the common ones. A local stdio package, @motorical/mcp, is also available for clients that only run local servers.

No. The hosted servers need only a URL and an OAuth sign-in. The local package is optional.

Only deliberately. Sends are dry-run by default, and a sandbox Motor Block is outbound-locked to an allowlist you control, so the blast radius before you convert to a real domain is limited to addresses you have approved.

No. The developer sandbox is unpaid. Converting a sandbox Motor Block onto a domain you own requires an active plan.

Give your agent a sending stream, not your production credentials.