Model Context Protocol
Add Zapinner to your AI agent in 30 seconds
Give Claude, Cursor, and any MCP client 79 production-ready data tools — dedupe, PII detection, validation, JSON repair, and more. One line of config, no SDK to wire up.
Get an API key
Create a free Zapinner account and copy an API key from the dashboard. The free plan is enough to start calling tools immediately.
Point your client at the endpoint
Add Zapinner to your MCP client config. If your client supports remote (Streamable HTTP) servers, use the hosted URL — no install, no local process.
Ask your agent
Your agent now has Zapinner's tools. Ask it to dedupe a list, detect PII, validate emails, or repair JSON — it calls the API and hands you clean data back.
Recommended: the hosted endpoint
Works today with zero install. Point any remote-MCP-capable client at the hosted URL with your API key as a Bearer token — the tools, protocol, and billing all live server-side, so it stays in lockstep with the API.
{
"mcpServers": {
"zapinner": {
"url": "https://zapinner.com/mcp",
"headers": {
"Authorization": "Bearer zap_live_..."
}
}
}
}Local clients: the stdio bridge
For clients that only support local servers, the @zapinner/mcp bridge forwards stdio to the same hosted endpoint with your key attached.
{
"mcpServers": {
"zapinner": {
"command": "npx",
"args": ["-y", "@zapinner/mcp"],
"env": {
"ZAPINNER_API_KEY": "zap_live_..."
}
}
}
}Note: the hosted endpoint above works today. The npx @zapinner/mcp bridge is package-ready and ships to npm shortly — until then, prefer the hosted URL.
One key. Every tool your agent needs for clean data.
Discover the live tool set and input schemas at runtime with tools/list. New capabilities show up automatically — no client update required.