ShipMyForm MCP ServerVerifiedFeatured

What is ShipMyForm MCP Server?

ShipMyForm MCP Server is the official remote MCP server for ShipMyForm, a form backend for static sites. It lets a coding agent create form endpoints, paste ready-made markup into your site, route submissions to tools like Slack or webhooks, and read submission stats without opening a browser.

ShipMyForm calls itself an AI-native form backend: everything the dashboard can do is a tool on the MCP server, plus a few things the dashboard cannot. An agent can even create and verify the account itself. Submissions are spam-filtered, stored and routed to email, Slack, Sheets and 20+ other tools. The free plan covers 100 submissions a month with no card.

How to use ShipMyForm MCP Server?

The server is remote (Streamable HTTP), so there is nothing to install. Every client needs three facts:

URL:        https://shipmyform.com/api/mcp
Transport:  Streamable HTTP (not SSE, not stdio)
Auth:       Authorization: Bearer smf_YOUR_KEY

Get an API key in Settings → API keys (every plan, including free), or let your agent call sign_up with your email. ShipMyForm emails a 6-digit code, and verify_account with that code returns the key. ShipMyForm recommends keeping the key in an environment variable such as SMF_API_KEY rather than in a committed file.

Claude Code

claude mcp add --transport http shipmyform https://shipmyform.com/api/mcp \
  --header "Authorization: Bearer smf_YOUR_KEY"

To share it through a project .mcp.json, which expands environment variables:

{
  "mcpServers": {
    "shipmyform": {
      "type": "http",
      "url": "https://shipmyform.com/api/mcp",
      "headers": { "Authorization": "Bearer ${SMF_API_KEY}" }
    }
  }
}

Claude Desktop / claude.ai

The "Add custom connector" dialog is built for OAuth and has no API-key header field, and ShipMyForm does not offer OAuth. On Claude Desktop, use the mcp-remote bridge (needs Node.js) in claude_desktop_config.json and restart the app:

{
  "mcpServers": {
    "shipmyform": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://shipmyform.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer smf_YOUR_KEY" }
    }
  }
}

On Team and Enterprise plans, an organization admin can add it as a custom connector with an authorization request header (an Anthropic beta).

Cursor

~/.cursor/mcp.json or .cursor/mcp.json:

{
  "mcpServers": {
    "shipmyform": {
      "url": "https://shipmyform.com/api/mcp",
      "headers": { "Authorization": "Bearer ${env:SMF_API_KEY}" }
    }
  }
}

VS Code

.vscode/mcp.json (top-level key servers). The input variable makes VS Code prompt for the key once and store it securely:

{
  "inputs": [
    { "type": "promptString", "id": "shipmyform-key", "description": "ShipMyForm API key (smf_…)", "password": true }
  ],
  "servers": {
    "shipmyform": {
      "type": "http",
      "url": "https://shipmyform.com/api/mcp",
      "headers": { "Authorization": "Bearer ${input:shipmyform-key}" }
    }
  }
}

ShipMyForm's docs also cover Codex CLI, Gemini CLI, Windsurf, Cline, Zed, opencode and JetBrains.

Key features of ShipMyForm MCP Server

• Agent-only onboarding: sign_up and verify_account create an account and return a key with no browser.
• Paste-ready snippets for HTML, React, Vue and plain fetch.
• Routing to email, webhooks, Slack, Discord, Airtable, HubSpot, Telegram and more.
• Hosted form pages on shipmyform.com for sites with no backend, plus an embed script.
• Scoped keys: presets wiring, triage, readonly and full. A key can never grant scopes it does not hold, so a narrow key is a real limit.
• Spam triage that trains the classifier when you label submissions.
• Rate limits of 30 requests a minute per key on free and 120 on paid plans.

ShipMyForm MCP Server tools

The live server exposes 29 tools in a few groups:

• Account and keys: sign_up, verify_account, resend_verification_code, get_account, create_api_key, list_api_keys, revoke_api_key. Use create_api_key to hand another agent a narrower key.
• Billing: start_upgrade returns a hosted checkout URL that a person completes; get_billing_portal links to plan and card management.
• Forms: create_form, list_forms, get_form, update_form (allowed domains, redirect, spam mode, validation, blocklist, auto-responder), delete_form and get_form_snippet.
• Delivery: list_connector_types, add_connector, test_connector, set_connector_active, remove_connector. OAuth connectors such as Google Sheets and Notion must be added in the dashboard.
• Hosted pages: publish_hosted_page, unpublish_hosted_page.
• Submissions: get_submission_stats works on every plan. list_submissions, get_submission, label_submissions, delete_submissions and export_submissions (CSV, up to 2,000 rows) need a paid plan.

Use cases of ShipMyForm MCP Server

• Contact form in one prompt: "Create a contact form called 'Portfolio contact' on ShipMyForm and add the React snippet to src/components/ContactForm.tsx."
• Setup from nothing: "Sign up with my email, verify it with the code from my inbox, create a 'Contact' form that emails me and send Slack alerts to #leads."
• Static site with no host: publish a hosted form page and embed it.
• Weekly triage on a paid plan: "Go through this week's submissions on the Contact form, mark the obvious spam, group the rest by topic and draft a reply to each real one."
• Quota checks: "How many submissions did my forms get this month, and how much quota is left?"

Troubleshooting ShipMyForm MCP Server

• 401 errors: the key is wrong, revoked or rate-limited.
• Connected but no tools: the client is probably using SSE. Use Streamable HTTP.
• Claude.ai custom connector won't take a key: use the mcp-remote bridge on Claude Desktop instead.
• Can't read submissions: reading, labeling and exporting submission content through MCP is part of the paid plans. Free keys can still see stats, and the dashboard always shows submissions.
• Header gets mangled in args: keep the value with the space in env, as in the Claude Desktop example.