---
updatedAt: 2026-10-08T14:30:35.000Z
agentTools:
  projectIndex: https://docs.rocketreach.co/llms.txt
---

# Quick Start

This guide walks through connecting an MCP client to RocketReach and making your first tool call. It assumes you have a RocketReach account with API access.

## MCP server URL

```
https://mcp.rocketreach.co/mcp
```

Point your MCP client at this URL. It will initiate the OAuth flow automatically on first use.

## Connecting a client

Most MCP clients discover auth and register automatically once you provide the server URL. The general steps are:

1. Add the MCP server URL to your client's configuration (see client-specific guides below).
2. On first use, the client opens a browser window to the RocketReach authorization page.
3. Log in with your RocketReach credentials and approve the access request.
4. The client stores the token and begins forwarding tool calls.

**Client guides:**

* [Claude Code](claude-code-setup) — covered in detail below
* Claude Desktop, Cursor, ChatGPT — use the same MCP server URL; refer to each client's documentation for configuration steps

## Verifying connectivity

Once connected, ask your agent to call the `ping` tool or use `account` to confirm auth is working:

> "Check my RocketReach account status"

The agent will call `account` and return your plan, credit balances, and rate-limit state.

## Your first search

> "Find VPs of Engineering at Series B SaaS companies in New York with more than 200 employees"

The agent maps this to a `person_search` call with the appropriate facets and returns matching profile summaries. No credits are consumed.

## Credit-consuming operations

`person_search` and `company_search` return profile summaries only — no contact information. Four tools consume credits:

| Tool                     | Credits                                                                      | What you get                                    |
| ------------------------ | ---------------------------------------------------------------------------- | ----------------------------------------------- |
| `person_lookup`          | 1 lookup credit + 1 person export                                            | Contact info (emails, phones) for one person    |
| `profile_company_lookup` | 1 lookup credit + 1 person export + 1 company export                         | Contact info + full company details in one call |
| `company_lookup`         | 1 company export                                                             | Full company profile                            |
| `email_verify`           | 1 email verification credit (refunded if `unknown` or incorrectly formatted) | Deliverability verdict for one email address    |

`email_verify` draws on a separate `email_verification` credit balance, not your lookup credits.

The data returned by `person_lookup` depends on which lookup credit type your plan issues: `standard_lookup` returns email only; `premium_lookup` returns email + phone; `phone_lookup` returns phone; `person_enrich` returns profile metadata with no contact info.

Check your credit balance with the `account` tool before running bulk lookups. The tool returns a `credit_usage` array with one entry per credit type — `allocated: 0` means that credit type is not available on your plan.

## Rate limits

MCP calls share your existing RocketReach API rate limit budget. There is no separate MCP-specific limit — the daily API usage and limits reported by the `account` tool reflect **combined** usage across MCP tool calls and direct API calls. If you use both heavily, they compete for the same quota.

The `account` tool returns your current limits and usage under `rate_limits`. If you hit a 429, the tool returns a `rate_limited` error with a `retry_after_seconds` hint.