MCP connector

01What this is

MightyAutomation ships a remote MCP server — the open protocol AI clients like Claude, Grok, and Cursor use to call external tools. Connect it once and your AI assistant can work your CRM directly: find and create contacts, tag and take notes, send emails, enroll automations, create booking links, and manage event webhooks.

• Endpoint — https://mcp.mightyautomation.com/api/mcp (the bare host https://mcp.mightyautomation.com works too — POSTs there reach the same endpoint)
• Transport — Streamable HTTP (JSON-RPC 2.0, stateless)
• Auth — Bearer API key, project-scoped (mva_mcp_…)
• Registry — listed as com.mightyautomation/mcp in the official MCP Registry · plugin source on GitHub

Every tool call acts on the workspace your key belongs to — there is no workspace parameter, so a key can never address another tenant.

02Setup — 2 minutes

1. Get your MCP key

1. Sign in to MightyAutomation and open your project.
2. Go to Integrations → Zapier & other tools → AI connectors (MCP).
3. Click Generate MCP key and copy it — it is shown once. Keys look like mva_mcp_….

2. Add the connector in your client

Grok Bot — install the MightyAutomation plugin (mightymikereid/mightyautomation-plugin) or add a custom connector with the endpoint URL and an Authorization: Bearer <key> header.

Cursor — install the mightyautomation plugin and set the MA_MCP_KEY variable in Plugins → Configure, or add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "mightyautomation": {
      "url": "https://mcp.mightyautomation.com/api/mcp",
      "headers": {
        "Authorization": "Bearer mva_mcp_YOUR_KEY"
      }
    }
  }
}

VS Code — find Mighty Automation in the MCP server gallery (from the official registry), or add the same mcp.json block to your workspace settings.

Claude (claude.ai / Desktop) — Settings → Connectors → Add custom connector:

Name:  MightyAutomation
URL:   https://mcp.mightyautomation.com/api/mcp
Headers:
  Authorization: Bearer mva_mcp_YOUR_KEY

ChatGPT — enable developer mode and add the endpoint as a custom MCP server with the Bearer header. OAuth 2.1 sign-in (one click, no key pasting) is in progress for Claude, ChatGPT and Copilot — API keys work everywhere today.

Clients that only speak stdio — bridge with mcp-remote:

npx mcp-remote https://mcp.mightyautomation.com/api/mcp \
  --header "Authorization: Bearer mva_mcp_YOUR_KEY"

3. Test it

Ask your AI: “Who am I connected as?” — it should call whoami and answer with your project name. Then try “find the contact jane@example.com”.

03Example prompts

What a connected agent can do for you:

• “Create a contact for jane@acme.com, tag her ‘webinar’, and add a note that she asked about pricing.”
• “Find everyone tagged ‘lead’ created this week and move them to the Nurture stage.”
• “Email mike@example.com about his upcoming appointment.”
• “Enroll jane@acme.com in the Welcome automation.”
• “Create a booking link for next week and text me the URL.”
• “Show me my credit balance and recent spend.”

04Tools

The connector exposes the same surface as the REST API — reads and writes land identically either way. Read-only tools are free; successful writes are billed per call (see pricing).

Read — free

Write — billed per successful call

05Troubleshooting

• 401 unauthorized — the key is missing, mistyped, or revoked. Keys look like mva_mcp_…; make sure the whole token is in the Authorization: Bearer … header. Rotate under Integrations → AI connectors (MCP) if unsure.
• 403 insufficient_scope — your key's scope does not cover this surface. MCP keys (mva_mcp_) only work on the MCP endpoint, never on the REST API — generate the right key type for the surface you are calling.
• Insufficient credits / plan required — write calls need a paid plan and a positive credit balance. Read-only tools stay free, but the plan gate applies to every call. Check your balance with get_credit_balance.
• Rate limited (429) — ~60 requests/minute per key. Back off a few seconds and retry; batching writes with natural pacing avoids this.
• Validation errors — arguments are checked against each tool's schema before anything runs: wrong types, bad emails/uuids, missing required fields and out-of-range values all fail fast with a named error and cost nothing.
• A call that failed charged no credits — is that right? Yes. Only successful writes are billed.

06Pricing

• Plan — the connector requires a paid MightyAutomation plan ($97 setup, includes $100 in credits — credits never expire and are non-refundable).
• Read-only tools — always free, including whoami and get_credit_balance.
• Write tools — $0.005 of Mighty credits per successful call; import_file is $0.025 (file ingest + storage); send_email additionally bills the standard per-email rate.
• Failed calls are free — validation errors, not-found, and errors never debit.
• Lapsed plan — calls are rejected until billing is restored; keys stay valid.

07Security model

• Project-scoped — a key only ever sees its own workspace's data.
• MCP-only — mva_mcp_ keys authenticate on the MCP endpoint only; they cannot be used to call the REST API directly (that surface takes agent/zapier keys).
• One active MCP key per project — generating a new one rotates it; revoke any time from Integrations.
• Rate limit — ~60 requests/minute per key.
• Safety rails on writes — send_email refuses do-not-contact and previously-bounced addresses; delete_hook is the only destructive tool and it is idempotent.
• Stored hashed — we only keep the key's SHA-256; the plaintext is shown once at generation.

OAuth 2.1 sign-in (PKCE) is in progress for the directory listings that require it — API keys remain supported for Cursor, Grok Bot and direct use. Treat the key like a password: don't paste it into chats or commit it to a repo.

Verify with curl

curl -X POST https://mcp.mightyautomation.com/api/mcp \
  -H "Authorization: Bearer mva_mcp_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

08Privacy & support

Tool calls are logged for abuse prevention and debugging (tool name, latency, error flag — never email bodies or note contents beyond what the CRM already stores as your data). Data handling is covered by the privacy policy.

Questions or a bug: support@mightyautomation.com · full support page at /support.