MCP connector

01What this is

MightyAutomation runs a remote MCP server — the open protocol AI clients use to call external tools. Connect it and your AI assistant can work your CRM: find and create contacts, tag them and add notes, send emails, enroll automations, create booking links, add, reschedule and cancel calendar appointments, import files and manage event webhooks. It can also read your pipeline board, email campaign stats, automation steps, Content Calendar, Media Assets library and Mighty Dial call log.

• Endpoint — https://dev.mightyautomation.ai/api/mcp
• Transport — Streamable HTTP, stateless JSON-RPC 2.0 over POST. There is no SSE stream: GET and DELETE return 405 (a browser GET is sent to this page).
• Auth — a project-scoped API key (mva_mcp_…).
• Plugin source — mightymikereid/mightyautomation-plugin on GitHub.

The project is resolved from the key — there is no workspace parameter, so a key can never address another workspace.

02Setup with an API key

API keys are the supported way to connect every client below.

1. Get your MCP key

1. Sign in and open your project. MCP keys are a paid-plan feature.
2. Go to Integrations → Zapier & other tools → AI connectors — MCP.
3. Click Generate MCP key and copy it — it is shown once. Generating again rotates it (one active key per project).

The key can be sent as Authorization: Bearer <key>, as a bare Authorization: <key>, or in an x-ma-mcp-key header for clients that cannot set Bearer.

2. Add it to your client

Cursor — add to ~/.cursor/mcp.json (or the project's .cursor/mcp.json):

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

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

Name:  MightyAutomation
URL:   https://dev.mightyautomation.ai/api/mcp
Header:
  Authorization: Bearer mva_mcp_YOUR_KEY

ChatGPT — turn on developer mode and add a custom MCP server with the endpoint URL and the Authorization header above.

Grok Bot — install from the plugin repository, or add a custom connector with the endpoint URL and the Authorization header.

Copilot (VS Code), Gemini and other clients — any MCP client that supports remote Streamable HTTP servers with custom headers can connect with the endpoint URL and the Authorization header. In VS Code, the same url + headers block goes in your MCP server configuration.

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

npx mcp-remote https://dev.mightyautomation.ai/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 name your project. Or from a terminal:

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

03Sign in with OAuth (available on dev / rolling out)

Available on dev / rolling out. OAuth sign-in is shipped on the dev environment and is not yet the supported path — use an API key (above) for production workspaces.

• Add https://dev.mightyautomation.ai/api/mcp as a custom connector and leave the auth header empty. The client discovers the authorization server from the 401 challenge.
• OAuth 2.1 authorization code with PKCE; clients register themselves (dynamic client registration).
• You sign in, pick one project and click Allow. The app can then use the tools on that project only, billed exactly like an MCP key.
• The consent screen marks Claude and ChatGPT callback URLs as verified; other clients are shown as unverified.
• See and disconnect apps under Integrations → AI connectors — MCP → Connected AI apps.

04Example prompts

• “Who am I connected as?” — whoami
• “Create a contact for jane@acme.com, tag her 'webinar', and add a note that she asked about pricing.” — upsert_contact, add_tag, add_note
• “Show me every lead in the Qualified stage that has a phone number.” — list_pipeline_stages, search_leads
• “Move jane@acme.com to the Nurture stage and mark her lifecycle as prospect.” — find_contact, list_pipeline_stages, update_contact
• “Email mike@example.com a reminder about his appointment on Thursday.” — find_contact, send_email
• “Enroll jane@acme.com in the Welcome automation.” — list_automations, enroll_automation
• “Create a booking link for jane@acme.com and give me the URL.” — find_contact, create_booking_link
• “What appointments are booked for next week?” — list_appointments
• “What happened in my CRM today?” — list_events
• “Import this PDF into my media library: https://example.com/brochure.pdf” — import_file
• “Send contact_created events to https://example.com/hook.” — create_hook, list_hooks
• “What is my credit balance?” — get_credit_balance
• “How many contacts are in each stage of my pipeline?” — get_pipeline_board
• “Book a 30-minute call with jane@acme.com next Tuesday at 2pm, then move it to Wednesday.” — create_appointment, list_appointments, reschedule_appointment
• “How did my last email campaign perform?” — list_campaigns
• “What is on my content calendar this month?” — list_content_calendar
• “Show me today's missed inbound calls.” — list_dial_calls

05Tools

The server exposes 37 tools (18 read, 19 write). Each one maps onto the matching REST API route, so results are identical either way.

Read — free

Write — billed per successful call

06Troubleshooting

• 401 Unauthorized (JSON-RPC -32001, with a WWW-Authenticate header) — the key is missing, mistyped or revoked, or an OAuth access token is invalid or expired. Make sure the whole mva_mcp_… key is sent; rotate it under Integrations if unsure.
• 403 insufficient_scope — the key is not an MCP, agent or Zapier key (for example a voice-scheduling key). Generate an MCP key.
• 429 rate_limited — about 60 requests per minute per key. Every tool call in a batch counts. Wait a few seconds and retry.
• 503 “MCP is temporarily unavailable” — the server is not accepting tool traffic right now. Retry later.
• 400 Parse error — the body was not valid JSON-RPC 2.0. 405 — the request was not a POST.
• Plan or credit messages — these come back as a normal response (HTTP 200) whose tool result has isError: true and a message, not as an HTTP error code:
  • “plan doesn't include MCP access or the subscription is inactive” — a paid, active plan is required for every tool call, reads included.
  • “automatic credit top-up failed” — tools pause until billing is fixed.
  • “credit balance is too low”, “contribution policy” not accepted, or “temporarily paused for maintenance” — write tools are blocked; read tools still work.
• Validation errors — arguments are checked against each tool's schema before anything runs; a bad type, email or id fails with a named error and costs nothing.
• A failed call charged nothing — is that right? Yes. Failed calls are never charged.

07Pricing

• Plan — MCP requires an active paid MightyAutomation plan (see pricing).
• Read tools — free. That is all 18: whoami, find_contact, list_contacts, get_contact, search_leads, list_pipeline_stages, list_automations, list_appointments, list_events, list_hooks, get_pipeline_board, list_campaigns, get_automation, list_content_calendar, list_media_assets, list_dial_calls, get_credit_balance, grok_render_status.
• Write tools — $0.005 of Mighty credits per successful call; import_file is $0.025; grok_generate_audio is $0.025; grok_generate_video is $0.050; grok_publish_youtube is $0.025; grok_run_pipeline is $0.050.
• send_email — also bills the standard per-email messaging rate, on top of the tool fee.
• Failed calls are never charged — validation errors, not-found and other errors never debit credits.
• Credits are non-refundable — see the terms.

08Security model

• Project-scoped — a key only reaches its own project's data.
• MCP-only keys — mva_mcp_ keys work on the MCP endpoint only, not on the REST API.
• Stored hashed — only the key's SHA-256 hash is kept; the key is shown once.
• Safety rails — send_email refuses do-not-contact contacts; delete_hook is idempotent.
• Treat the key like a password: don't paste it into chats or commit it to a repository.

09Privacy & support

Each tool call is logged with the tool name, project, latency and error flag. Data handling is covered by the privacy policy.

Need help? See the support page.