Do I need a separate MCP account or API key?

No. You connect with the same MatchKraft API key you'd use for the regular REST API — there's no separate MCP account or OAuth step to set up.

Does this work with tools other than Claude Desktop?

Yes. Anything that speaks MCP over HTTP can connect using the Authorization: Bearer header form. Claude Desktop is the one exception that only accepts a plain URL, which is why it uses the key-in-URL format instead.

What happens with large lists?

Large lists are automatically batched and processed as background jobs. The client gets the job back and can poll it with check_job_status until results are ready — you don't need to chunk anything yourself.

Is this a different product from the MatchKraft API?

No — it's a thin bridge on top of the same public API (app.matchkraft.com/api/v2). Nothing changes about your account, usage, or billing; it's just a new way to reach the same Domain Scan, Email Finder, and Email Validation your account already has.

Is my data shared with Anthropic or anyone else?

No. The MCP server only relays requests between your AI client and your own MatchKraft account, authenticated with your own API key — the same way any other API client would.

IntegrationsAugust 10, 2026

MatchKraft MCP Server: Connect Claude to Your Account

MatchKraft now works directly inside Claude and any other MCP-compatible AI assistant — no CSV exports, no copy-pasting between tools. Here's what it does and how to connect it.

What this actually means for you

MCP (Model Context Protocol) is the open standard AI assistants use to call outside tools. In plain terms: you can now ask Claude to find, verify, or scan emails using your own MatchKraft account, inside a normal conversation — instead of opening the app, exporting a CSV, and uploading it somewhere else.

For example, you could paste a list of 50 companies into Claude and say "find me a verified email for the VP of Sales at each of these" — Claude calls your MatchKraft account directly and hands back the results, live.

See it in action

A quick walkthrough of connecting the MatchKraft MCP server and using it inside Claude:

4 tools, available to any MCP client

Once connected, Claude has access to the same core capabilities as the MatchKraft app:

scan_domains

Find B2B contact emails from company domains.

find_emails

Find professional emails from names and companies.

validate_emails

Check email deliverability and validity.

check_job_status

Check the status of background jobs.

How it works

It uses your existing MatchKraft account to authenticate requests automatically — no separate OAuth setup is required.
Large lists are automatically batched and processed in the background, so a request for hundreds of contacts doesn't need to be chunked manually.
Results are returned directly to the MCP-compatible client you're using — Claude Desktop, Claude Code, or any other MCP client.

How to connect

You'll need a MatchKraft API key — grab yours from your account settings if you don't have one yet. There are two ways to connect, depending on the client:

Claude Desktop

Claude Desktop's connector UI only takes a plain URL, so your API key goes directly in the path. Go to Settings → Connectors → Add custom connector and paste:

https://mcp.matchkraft.com/mcp/<YOUR_API_KEY>

Claude Code, Claude.ai web connectors, and other MCP clients

Clients that support custom headers should connect to the base URL with a bearer token instead:

URL:     https://mcp.matchkraft.com/mcp
Header:  Authorization: Bearer <YOUR_API_KEY>

Frequently Asked Questions

Try MatchKraft inside Claude

Grab your API key and connect the MCP server in a couple of minutes. Free plan included.

Try it for free