Spin one up from Cursor, the CLI, or the API in under a minute, and send test mail before you touch DNS.
A client's newsletter starts collecting spam complaints. It shares a sending account — and a reputation — with your production app. Within days, the app's password-reset emails start landing in spam too.
Pooled analytics make this invisible until support tickets pile up: the account-wide delivery rate still looks fine, because the newsletter's volume dilutes the one number that actually matters.
A Motor Block per project means the newsletter's reputation problem stays the newsletter's problem. Your production app keeps its own domain, its own sending rate, and its own reputation score — unaffected by what another project does.
One bad sender doesn't take the rest of your projects down with it.
A Motorical SMTP Motor Block is an isolated sending stream for one project — app, staging env, tenant, or experiment. Specs, auth, observability, and automation stay yours. Nothing is shared with unrelated traffic.
Reputation isolation isn't a new idea — SendGrid subusers, Amazon SES tenant isolation, and similar features exist for exactly this reason. The difference is who they're built for: those are enterprise-tier features or something you architect yourself on AWS. A Motor Block is self-serve from the free plan, created in seconds, for the workflow a solo developer or small team actually has — separating your own side projects, staging environments, and client work, not managing tenants for other people's accounts.
Domain, auth method (password, API key, OAuth 2.0, or mTLS), API keys, and SMTP credentials — set once per Motor Block, not once per account.
Delivery logs, signed webhooks, and a reputation score scoped to this project — not averaged with everything else you send.
Sending rates and automation rules you set for this app, staging environment, or experiment — independent of every other Motor Block.
From an agent, a terminal, or a single HTTP call — pick whichever fits how you already work.
Add Motorical to Cursor or Claude Desktop. The server ships 13 tools, a prompt, and two resources — including the live OpenAPI spec, so your agent reads the current contract instead of guessing at it.
{
"mcpServers": {
"motorical": {
"command": "npx",
"args": ["-y", "@motorical/mcp"],
"env": { "MOTORICAL_MK_API_KEY": "mk_live_..." }
}
}
}Abbreviated — full template at motorical-mcp.cursor.json.The CLI twin. Same surface, from a shell — good for CI or a quick manual test.
npm install -g https://docs.motorical.com/motorical-cli.tgz motorical signup you@example.com motorical verify 123456 motorical sandbox provision motorical send --to you@example.com --real
One HTTP call. Validate first with a dry run, then send for real.
curl -X POST https://api.motorical.com/v1/send \
-H "Authorization: Bearer mk_live_..." \
-d '{"to":"you@example.com","subject":"Hello","text":"Hi","dryRun":true}'Every Motor Block chooses its own authentication method — a staging environment doesn't have to use the same credential type as production.
Simple SMTP auth for scripts and quick setups.
mk_live_ keys for send, ak_live_ keys for analytics — scoped per Motor Block.
Full authorize / token / validate flow for delegated, third-party access.
Mutual TLS for infrastructure that authenticates by certificate, not credential.
Every number below is scoped to one Motor Block — not an account-wide average that hides what one bad project is doing to the rest.
Provision an unpaid sandbox Motor Block on *.sandbox.motorical.com — outbound-locked to an allowlist you control — and send a real test message before you own a domain. Convert it onto a verified domain of your own whenever you're ready.
Full working examples for Node.js, Python, PHP, Go, Java, and C#.
curl -X POST https://api.motorical.com/v1/send \
-H "Authorization: Bearer mk_live_..." \
-H "Content-Type: application/json" \
-d '{"to":"you@example.com","subject":"Hello","text":"Hi from Motorical"}'Three products on one platform. Start with transactional send — add campaigns or mailboxes when you need them.
One Motor Block per project — own auth, domain, rates, logs, webhooks, and automation. HTTP send or SMTP relay.
Marketing campaigns, contact lists, and click/open tracking on infrastructure isolated from transactional streams.
Encrypted business mailboxes with webmail, mobile sync, and custom domains — powered by Gluo.
Each Motor Block has its own reputation, credentials, and logs.
Signed mail by default; webhooks and timelines when you automate.
Infrastructure and data stay in the EU, GDPR compliant.
Adding a domain that already sends via Google Workspace or M365? We detect it and merge SPF instead of overwriting it.
Create a Motor Block, pick auth, and send — with full observability from day one.