RocketReach

What the RocketReach MCP server does

The RocketReach MCP server gives AI assistants access to RocketReach data for contact discovery, company research, enrichment, and prospecting. People can be searched using fields such as name, title, employer, location, and other filters. Company searches support names, domains, and firmographic criteria.

Enrichment turns a person or company record into more complete information. Person results can include verified email addresses, phone numbers, and social profiles. Company results can include domain, employee size, location, revenue, industry, and other firmographic details. The service can also check whether an existing email address is deliverable and report account details such as remaining credits.

Pre-built Agent Skills provide guided workflows for enriching people, enriching companies, building filtered lists, finding decision-makers from an ideal-customer description, and verifying email addresses.

How it works

The RocketReach MCP server is exposed at https://mcp.rocketreach.co/mcp and uses OAuth rather than an API key stored in the repository. An MCP client registers the hosted endpoint, then starts an authorization flow in the browser. In Claude Code, the included plugin commands install the marketplace entry; Cursor can use the repository's MCP manifest and remote bridge configuration. Claude and Codex can use the direct HTTP registration described by the project files.

After connection, an assistant can call the underlying tools or invoke the packaged skills with commands in the /rocketreach:<skill-name> form. Search operations identify people or companies, while lookup and verification operations retrieve or validate additional data. The account and check_person_status tools provide account or lookup-status information.

Setup and configuration

For Cowork, install the RocketReach plugin from its marketplace link and restart Cowork. For Claude Code, add the RocketReach marketplace and install the RocketReach plugin with the documented /plugin commands, then restart Claude Code. Other clients can register the server using mcp.json or .mcp.json from the repository.

Once installed, run /mcp, choose RocketReach, and complete sign-in in the browser. No repository environment variable or API key is specified for authentication. The server uses OAuth at connection time.

Tools and capabilities

The RocketReach MCP server includes these tools:

• person_search for finding people with identity, role, employer, location, and related filters.
• person_lookup for retrieving a person's profile and contact information.
• company_search for finding companies by name, domain, and firmographics.
• company_lookup for retrieving a company's profile and firmographic details.
• email_verify for checking whether an email is deliverable.
• account for checking account information and remaining credits.
• check_person_status for checking person lookup status.

The included skills package these tools into workflows. enrich-person accepts identifiers such as a name, email, phone, LinkedIn URL, NPI number, or employer combination. enrich-company accepts a company name, domain, LinkedIn URL, or ticker symbol. build-list creates structured people or company lists from filters, while prospect ranks decision-makers against a plain-language customer description.

Limitations and notes

Person and company enrichment consume RocketReach credits. Email verification also consumes credits, and the client asks for confirmation before those operations run. Search and lookup results depend on the RocketReach account and available data.

The repository documents MCP registration for Cowork, Claude Code, Cursor, Claude, and Codex. Other clients may require their own MCP configuration format. Authentication is browser-based OAuth, so an interactive sign-in is required after installation.