leadsimple

leadsimple-mcp

Model Context Protocol server for LeadSimple. A thin stdio proxy in front of Zapier MCP that exposes only LeadSimple actions, renamed under the leadsimple_* prefix, so any MCP-compatible agent (Claude Desktop, Cowork, Claude Code, ClawBot) can drive LeadSimple in plain English.

Why this exists

LeadSimple does not publish a public REST API. Their official integration surface is Zapier — the "API key" their docs reference is explicitly scoped to the Zapier integration. So the right way to drive LeadSimple from an agent is:

Claude / Cowork  →  stdio  →  leadsimple-mcp  →  HTTPS  →  mcp.zapier.com  →  LeadSimple

Zapier already ships a remote MCP server at mcp.zapier.com that can expose any LeadSimple Zap action. This package is a small wrapper that:

• Connects upstream to your Zapier MCP server (Streamable HTTP)
• Filters Zapier's tool list down to LeadSimple-only actions
• Renames them under a configurable prefix (leadsimple_* by default)
• Re-exposes them over stdio so every MCP client can spawn it with one config block
• Refreshes the tool list on every list_tools call, so new actions you enable in Zapier show up without restarting the agent

Each agent has its own Zapier MCP URL → its own usage audit on Zapier → its own scoped action surface. Same multi-agent pattern as vestlaunch-mcp.

Quick start (per agent)

1. Get your Zapier MCP server URL

Open mcp.zapier.com:

1. Create a new server (one per agent — e.g. leadsimple-cowork, leadsimple-claude-code, leadsimple-clawbot).
2. On the Configure tab, click + Add tool and add the LeadSimple actions you want this agent to have. Common ones:
   • LeadSimple: Create Lead
   • LeadSimple: Update Lead
   • LeadSimple: Find Lead
   • LeadSimple: Find Contact
   • LeadSimple: Update Contact
   • LeadSimple: Create Process
   • LeadSimple: Add Note
   • LeadSimple: Move Lead Stage
3. On the Connect tab, copy the server URL. It looks like https://mcp.zapier.com/api/mcp/s/<long-token>/mcp and contains an embedded token — treat it like a password.

2. Configure your agent

Claude Desktop / Cowork

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "leadsimple": {
      "command": "npx",
      "args": ["-y", "leadsimple-mcp"],
      "env": {
        "LEADSIMPLE_ZAPIER_MCP_URL": "https://mcp.zapier.com/api/mcp/s/..."
      }
    }
  }
}

Claude Code

claude mcp add leadsimple -- env LEADSIMPLE_ZAPIER_MCP_URL=https://mcp.zapier.com/api/mcp/s/... npx -y leadsimple-mcp

Any other MCP client

Spawn npx -y leadsimple-mcp with LEADSIMPLE_ZAPIER_MCP_URL in the environment. Stdio in, stdio out.

3. Try it

In your agent, ask:

"Use LeadSimple to create a new lead in my Property Management pipeline for Jane Doe, [email protected], phone 555-867-5309, source 'Your Website'."

The agent will call the corresponding leadsimple_* tool, which routes to your Zapier MCP server, which calls LeadSimple.

Configuration

Env var	Required	Default	Purpose
LEADSIMPLE_ZAPIER_MCP_URL	yes	—	Your Zapier MCP server URL from mcp.zapier.com. Contains the auth token in the path.
LEADSIMPLE_MATCH_TERMS	no	leadsimple	Comma-separated, case-insensitive substrings used to identify LeadSimple tools in Zapier's tool list. Widen this if Zapier names something differently than you expect.
LEADSIMPLE_KEEP_META_TOOLS	no	true	Pass through Zapier's 14 meta-tools (execute_zapier_*, discover_zapier_actions, etc.). On by default because Zapier's "Other" preset routes ALL action invocations through them — dropping would render the proxy useless.
LEADSIMPLE_TOOL_PREFIX	no	leadsimple_	Prefix added to every exposed tool name. Set to "" to keep Zapier's original names.
LEADSIMPLE_LOG_LEVEL	no	info	silent | error | warn | info | debug. Goes to stderr (stdout is the MCP protocol).
LEADSIMPLE_TIMEOUT_MS	no	60000	Per-request timeout against the upstream Zapier MCP server.

Diagnostic probe

To verify which tools leadsimple-mcp would expose for your current config without running the full server:

LEADSIMPLE_ZAPIER_MCP_URL=https://mcp.zapier.com/api/mcp/s/... npm run probe

You'll get a side-by-side view of what's available upstream vs. what would be exposed under the LeadSimple filter — useful for tuning LEADSIMPLE_MATCH_TERMS.

How the proxy actually works

A note on the upstream shape — important because it affects how the agent uses LeadSimple via this proxy.

Zapier's generic ("Other") MCP preset does not surface each enabled action as its own MCP tool. Instead it exposes a fixed meta-tool API of 14 tools: