MCP server

Zapinner speaks the Model Context Protocol, so AI agents can call all 79 capabilities as tools. Each tool maps to the same v1 endpoint the REST API and SDKs use, so agent calls authenticate, meter, and bill exactly like any other request.

Hosted endpoint (recommended)

The hosted server uses the Streamable HTTP transport. Point any MCP-capable client at the endpoint and authenticate with your Zapinner API key as a Bearer header:

MCP endpoint

https://zapinner.com/mcp

Typical remote-server client config:

mcp config (remote)

{
  "mcpServers": {
    "zapinner": {
      "url": "https://zapinner.com/mcp",
      "headers": { "Authorization": "Bearer zap_live_..." }
    }
  }
}

Local stdio bridge

The hosted endpoint above is live and needs no install. The @zapinner/mcp stdio bridge is implemented and package-ready but not yet published to npm, so the npx config below will not resolve until it ships. Prefer the remote endpoint meanwhile.

For clients that only support local servers, the @zapinner/mcp package bridges stdio to the hosted endpoint with your key attached. It runs via npx — no global install:

mcp config (local)

{
  "mcpServers": {
    "zapinner": {
      "command": "npx",
      "args": ["-y", "@zapinner/mcp"],
      "env": { "ZAPINNER_API_KEY": "zap_live_..." }
    }
  }
}

The bridge is a thin proxy: it forwards protocol messages to https://zapinner.com/mcp and injects your API key, so the tools and behavior are always identical to the hosted endpoint. Set ZAPINNER_BASE_URL to target a self-hosted deployment.

Available tools

The server exposes one tool per capability. Call tools/list to discover them and their input schemas at runtime:

normalize, dedupe, match, compare, explain, anomalies
score, verify, analyze, reconcile, revenue_leak, lead_recovery

Probe it with curl

tools/list

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

Auth & billing

Tool discovery needs no key; running a tool requires a valid Zapinner key and consumes records from your monthly allowance exactly like the REST API. MCP traffic appears under the Access methods breakdown in your dashboard.