Rocketreach MCP Server

Rocketreach MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for RocketReach API integration. Features include finding professional and personal emails, enriching company data, and finding phone numbers.

What you get

This is a Model Context Protocol (MCP) server that integrates with the RocketReach API to provide email finding, phone number finding, and company enrichment capabilities.

• Find professional emails for individuals
• Find personal emails for individuals
• Enrich company data
• Find phone numbers for individuals

What the assistant can call

Once Rocketreach is connected, these are the calls the assistant has available:

• rocketreach_find_professional_email — Find a professional email for an individual
• rocketreach_find_personal_email — Find a personal email for an individual
• rocketreach_enrich_company — Enrich company data
• rocketreach_find_phone — Find a phone number for an individual

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need one environment variable: ROCKETREACH_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Rocketreach's toolset — rocketreach_find_professional_email, rocketreach_find_personal_email, rocketreach_enrich_company and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Meerkats-Ai; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the rocketreach mcp server does with a few real requests.