> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to the RocketReach MCP server

The RocketReach MCP connector routes your AI agent's tool calls to RocketReach's own MCP server through Scalekit. Each user signs in to RocketReach once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 13 tools.

**Authentication:** OAuth 2.1/DCR
**Categories:** CRM & Sales
**Tools:** 13: 6 read, 0 write, 7 destructive
**Users sign in with:** OAuth
**OAuth app:** Your own RocketReach MCP server app
**Built by:** Vendor MCP
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=ROCKETREACHMCP)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the RocketReach MCP connection

   In **AgentKit > Connections**, create a RocketReach MCP connection and copy its redirect URI. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Register an OAuth app

   RocketReach MCP server connections use your own OAuth app. Register one with RocketReach MCP server and add the redirect URI you copied.

   Then enter the app's Client ID and Client Secret on the RocketReach MCP connection.

5. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'rocketreachmcp'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize RocketReach MCP:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'rocketreachmcp_account',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "rocketreachmcp"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize RocketReach MCP:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="rocketreachmcp_account",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user signs in once. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'rocketreachmcp_account',
  toolInput: {},
  connector: 'rocketreachmcp',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="rocketreachmcp_account",
    tool_input={},
    connection_name="rocketreachmcp",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `rocketreachmcp_account`

Account · Read-only

Retrieve the authenticated user's RocketReach account info: plan name and limits, credit balances, lifetime usage, daily API call count and limit, and rate-limit status. The `credit_usage` field is a per-type breakdown showing which of the seven credit types are issued on this account (`standard_lookup`, `premium_lookup`, `phone_lookup`, `person_enrich`, `person_export`, `company_export`, `email_verification`) and how many are allocated, used, and remaining. `allocated: 0` means the user does not have that credit type issued: a user with only `standard_lookup` credits will not receive phone numbers from `person_lookup`; a user without `company_export` will receive `insufficient_credits` from `company_lookup` and `profile_company_lookup`; a user without `email_verification` will receive `insufficient_credits` from `email_verify`. The rollup field `person_export_credit_balance` may be the string `'inf'` — a v2 convention meaning "not tracked on this account; doesn't apply," not infinite credits available. No credits consumed.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `rocketreachmcp_check_person_status`

Check Person Status · Read-only

Check the status of in-flight person lookups returned with `status: "pending"` by `person_lookup`, `profile_company_lookup`, or `bulk_person_lookup`. Pass exactly one of: `profile_id` — a single id or an array of up to 100 — or `rr_request_id` — the batch id returned by `bulk_person_lookup`, which retrieves every profile in that batch in one call. Returns the current state for each profile: `complete` with full contact data, `pending` with profile metadata only, or `failed` if the search ran to completion but no contact info was found. A scalar `profile_id` returns a single record; an array or an `rr_request_id` returns `{ records: [...] }` — re-poll until no record is still `pending`. An `rr_request_id` returns one record per query, each with its `query_index` (its position in the bulk request); a `failed` record there carries a `failure_reason`: `no_match` (no profile matched the query), `suppressed` (the profile is on the team's suppression list), `not_processed` (the query was not attempted, e.g. the account ran out of credits), `profile_unavailable` (the matched profile is no longer available), or `no_contact_info`. Lookups typically resolve within ~5 seconds (longer for a bulk batch, or when the system is degraded). Wait at least 3 seconds between polls. No credits consumed and no changes to the user's RocketReach contacts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `profile_id` (`array`, optional): One or more RocketReach profile IDs to check. A single number or an array of up to 100. Omit when passing `rr_request_id`.
- `rr_request_id` (`string`, optional): The `rr_request_id` returned by `bulk_person_lookup`; returns every profile in that batch. Omit when passing `profile_id`.

Example input: `{}`

### `rocketreachmcp_company_search`

Company Search · Read-only

Search RocketReach for companies. Supports filtering by: identity (name, domain, website URL, email domain, social links, phone); classification (industry, primary industry, industry tags / keywords, SIC, NAICS, website category); size & financials (employee count, revenue, total funding, growth, publicly-traded indicator); location (HQ city/state/country with optional radius); technology (techstack); plus other signals (keyword, description, company_tag, news signals, hiring/job-posting signals, SEC filings, website-intelligence changes, product-review themes, website-traffic shifts, intent, competitors). Any facet can also be excluded via the `exclude` parameter. Numeric facets (employees, revenue, total_funding) support operators — 1000+, <5000, 100-500. Faceted fields (industry, primary_industry) match exact stored values only. `list_filter_values` returns the accepted values for each. Returns matching company summaries (name, domain, industry, employee count, company ID). No credits consumed and no changes to the user's RocketReach contacts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_tag` (`array`, optional): Tag applied to the company.
- `competitors` (`array`, optional): Companies named as competitors.
- `description` (`array`, optional): Match terms in the company description.
- `domain` (`array`, optional): Company website domain, e.g. acme.com (not exact; similar domains can match).
- `email_domain` (`array`, optional): Email domain the company uses.
- `employees` (`array`, optional): Employee count. Supports operators: 1000+, <5000, 100-500.
- `exclude` (`object`, optional): Exclude results matching these facets. Accepts the same keys as the top-level search facets, e.g. exclude: { name: ["Acme Corp"] }.
- `growth` (`array`, optional): Company growth metric.
- `id` (`array`, optional): RocketReach company ID(s).
- `industry` (`array`, optional): Industry classification. Valid values: `list_filter_values(field="industry")`.
- `industry_keywords` (`array`, optional): Industry-related keywords.
- `industry_tags` (`array`, optional): Industry tags.
- `intent` (`array`, optional): Purchase-intent signals.
- `job_posting_signal` (`array`, optional): Job postings for a given company. Value is a department-hiring category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Accounting Roles, Administration Roles, Business Development Roles, Corporate Communications Roles, Customer Services Roles, Design Roles, Engineering Roles, Facilities Management Roles, Finance Roles, Human Resources Roles, Information Technology Roles, Legal Roles, Logistics Roles, Machine Learning Roles, Marketing Roles, Operations Roles, Procurement Roles, Product Roles, Production or Manufacturing Roles, Project Management Roles, Public Relations Roles, Quality Assurance Roles, Recruiting Roles, Research and Development Roles, Retail Roles, Sales Roles, Skilled Trades Roles, Solutions Roles, Strategy Roles. Example: "Engineering Roles::one_month".
- `keyword` (`array`, optional): Free-text keyword matched across all fields.
- `link` (`array`, optional): Company social links (LinkedIn, etc.).
- `location` (`array`, optional): HQ location, e.g. "San Francisco, California". Optional radius: ::~50mi or ::~50km. Presets: `list_filter_values(field="location")`.
- `naics_code` (`array`, optional): NAICS code(s).
- `name` (`array`, optional): Company name.
- `news_signal` (`array`, optional): Company news event. Value is a news category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Attends Event, Award, Bankruptcy, Certification Achieved, Closes Offices, Competitor Identified, Decreases Headcount, Developing Product, Earnings Reported, Executive Departure, Executive Hire, Executive Promotion, Executive Retirement, Expands Facilities, Files Lawsuit, Funding, Increases Headcount, Integration, Invests Into, IPO, Launches Product, Lost Customer, Mergers & Acquisitions, New Customer, Partnership, Partnership Ended, Purchases Assets, Recognition, Revenue Reported, Security Incident, Sells Assets, Spin-off, Valuation Reported, Vulnerability. Example: "Funding::one_month".
- `order_by` (`string`, optional): Result ordering (default relevance; 'popularity' matches the Search web app). One of: `relevance`, `popularity`, `score`.
- `page_size` (`integer`, optional): Number of results to return per page (default 10, max 100).
- `phone` (`array`, optional): Company phone number.
- `primary_industry` (`array`, optional): Primary industry (when a company spans several). Valid values: `list_filter_values(field="primary_industry")`.
- `product_review_signal` (`array`, optional): Theme surfacing in customer reviews of the company's products. Value is a review-theme category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Active Churn, Competitor Mentions, Customer Support Complaints, Integration Problems, Missing Features, Pricing Concerns, Recurring Product Issues, Reliability Issues, Usability Issues. Example: "Pricing Concerns::three_months".
- `publicly_traded` (`array`, optional): Public-company indicator.
- `revenue` (`array`, optional): Annual revenue. Supports operators.
- `sec_filing_signal` (`array`, optional): Company filed an SEC form. Value is an SEC form type followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: 10-K Filing, 10-Q Filing, 20-F Filing, 6-K Filing, 8-K Filing. Example: "10-K Filing::three_months".
- `seo_website_traffic_signal` (`array`, optional): Month-over-month shift in the company's estimated website traffic. Value is a traffic-shift category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Sustained Decline, Sustained Growth, Traffic Decline, Traffic Surge. Example: "Traffic Surge::three_months". Shorter windows usually return nothing; use three_months or longer.
- `sic_code` (`array`, optional): SIC code(s).
- `start` (`integer`, optional): 1-based index of the first result, for pagination (default 1, max 10000).
- `techstack` (`array`, optional): Technologies the company uses.
- `total_funding` (`array`, optional): Total funding raised. Supports operators.
- `website_category` (`array`, optional): Website-category classification.
- `website_intelligence_signal` (`array`, optional): Change detected on the company's own website. Value is a website-change category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Acquisition, Branding Change, Community Engagement, Compliance Update, Contact Update, Customer Win, Event Announcement, Executive Change, Expansion, Feature Launch, Feature Update, Funding News, Geographic Expansion, Market Data, Marketing Campaign, Marketing Channel, Marketing Content, Marketing Shift, Media & Press, Operational Change, Other, Partnership Announcement, Pricing Change, Pricing Promotion, Product Expansion, Product Highlight, Product Launch, Product Removal, Product Update, Program Launch, Project Update, Recognition & Award, Service Update, Target Audience Shift, Team Expansion, Technical Update, Technology Adoption, Website Update. Example: "Product Launch::three_months". Shorter windows usually return nothing; use three_months or longer.
- `website_url` (`array`, optional): Full company website URL.

Example input: `{}`

### `rocketreachmcp_list_filter_values`

List Filter Values · Read-only

List the exact values a faceted search field accepts, fuzzy-matched against `query` (use one or two key words; leave it empty to list the field's values). Call this before `person_search` / `company_search` instead of guessing: a guessed value silently returns fewer results or none. Pass the returned `value` to the search field exactly; `label` is only for display. `country` takes the ISO code (US, GB). `state` takes a US/Canada region code and has no country, so a code like WA also matches Western Australia; add `country` to narrow. `location` lists presets but also takes free-text cities and zip codes. An industry group covers all its sub-industries; an unrecognized industry is silently remapped to the nearest one. `country`, `state`, `department` and `management_levels` exist on `person_search` only (`company_search` ignores them; use `location` for company HQ). Signal values also need a `::<timeframe>` suffix, as the search field describes. No credits consumed.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `field` (`string`, required): The search field to list values for, by its facet name. One of: `industry`, `company_industry`, `primary_industry`, `management_levels`, `department`, `country`, `state`, `location`, `news_signal`, `company_news_signal`, `job_posting_signal`, `company_job_posting_signal`, `sec_filing_signal`, `company_sec_filing_signal`, `website_intelligence_signal`, `company_website_intelligence_signal`, `product_review_signal`, `company_product_review_signal`, `seo_website_traffic_signal`, `company_seo_website_traffic_signal`, `job_change_signal`.
- `limit` (`integer`, optional): Maximum values to return (default 25, max 502).
- `query` (`string`, optional): Text to match, e.g. "united states", "vp", "engineering". Empty lists all values.

Example input: `{"field":"industry"}`

### `rocketreachmcp_person_search`

Person Search · Read-only

Search RocketReach for people by professional attributes. Supports filtering by: identity (name, profile ID); job & employer (current/previous title, current/previous employer, department, management level / seniority, years of experience, recent job-change signals); skills (any-of or all-of); education (school, degree, major); location (city/state/country, optional radius like "Boston"::~25mi); contact (email, email confidence grade, phone, phone confidence grade, contact method, LinkedIn URL); current-employer attributes (company size, revenue, industry, SIC/NAICS, tags, saved-list membership, competitors, intent signals, company news signals, hiring/job-posting signals, SEC filings, website-intelligence changes, product-review themes, website-traffic shifts); healthcare (NPI number, medical license, specialization, credentials); plus free-text keyword. Any facet can also be excluded via the `exclude` parameter (e.g., exclude a specific current employer). Numeric facets support operators — 1000+, <5000, 3-7. Faceted fields (company_industry, department, management_levels, state) match exact stored values only. `list_filter_values` returns the accepted values for each. Returns matching profile summaries (name, current title, current company, location, profile ID); does not return contact info. `person_lookup` returns emails and phone numbers. No credits consumed and no changes to the user's RocketReach contacts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `all_skills` (`array`, optional): Skills — AND logic, every listed skill must match.
- `city` (`array`, optional): City.
- `company_competitors` (`array`, optional): Companies named as competitors of the current company.
- `company_domain` (`array`, optional): Current company domain, e.g. acme.com (not exact; similar domains can match).
- `company_id` (`array`, optional): Current company's RocketReach ID.
- `company_industry` (`array`, optional): Current company industry. Valid values: `list_filter_values(field="company_industry")`.
- `company_industry_keywords` (`array`, optional): Keywords associated with the current company's industry.
- `company_intent` (`array`, optional): Current company's purchase-intent signals.
- `company_job_posting_signal` (`array`, optional): Hiring activity at the person's current company — the company is actively hiring for a department. Value is a department-hiring category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Accounting Roles, Administration Roles, Business Development Roles, Corporate Communications Roles, Customer Services Roles, Design Roles, Engineering Roles, Facilities Management Roles, Finance Roles, Human Resources Roles, Information Technology Roles, Legal Roles, Logistics Roles, Machine Learning Roles, Marketing Roles, Operations Roles, Procurement Roles, Product Roles, Production or Manufacturing Roles, Project Management Roles, Public Relations Roles, Quality Assurance Roles, Recruiting Roles, Research and Development Roles, Retail Roles, Sales Roles, Skilled Trades Roles, Solutions Roles, Strategy Roles. Example: "Engineering Roles::one_month".
- `company_list` (`array`, optional): Current company's saved-list membership, by list name.
- `company_list_id` (`array`, optional): Current company's saved-list membership, by list ID.
- `company_naics_code` (`array`, optional): Current company NAICS code.
- `company_news_signal` (`array`, optional): News event at the person's current company. Value is a news category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Attends Event, Award, Bankruptcy, Certification Achieved, Closes Offices, Competitor Identified, Decreases Headcount, Developing Product, Earnings Reported, Executive Departure, Executive Hire, Executive Promotion, Executive Retirement, Expands Facilities, Files Lawsuit, Funding, Increases Headcount, Integration, Invests Into, IPO, Launches Product, Lost Customer, Mergers & Acquisitions, New Customer, Partnership, Partnership Ended, Purchases Assets, Recognition, Revenue Reported, Security Incident, Sells Assets, Spin-off, Valuation Reported, Vulnerability. Example: "Funding::one_month".
- `company_product_review_signal` (`array`, optional): Theme surfacing in customer reviews of the current company's products. Value is a review-theme category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Active Churn, Competitor Mentions, Customer Support Complaints, Integration Problems, Missing Features, Pricing Concerns, Recurring Product Issues, Reliability Issues, Usability Issues. Example: "Pricing Concerns::three_months".
- `company_revenue` (`array`, optional): Current company annual revenue. Supports operators.
- `company_sec_filing_signal` (`array`, optional): The person's current company filed an SEC form. Value is an SEC form type followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: 10-K Filing, 10-Q Filing, 20-F Filing, 6-K Filing, 8-K Filing. Example: "10-K Filing::three_months".
- `company_seo_website_traffic_signal` (`array`, optional): Month-over-month shift in the current company's estimated website traffic. Value is a traffic-shift category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Sustained Decline, Sustained Growth, Traffic Decline, Traffic Surge. Example: "Traffic Surge::three_months". Shorter windows usually return nothing; use three_months or longer.
- `company_sic_code` (`array`, optional): Current company SIC code.
- `company_size` (`array`, optional): Current company employee count. Supports operators: 1000+, <5000, 100-500.
- `company_tag` (`array`, optional): Tag applied to the current company.
- `company_website_intelligence_signal` (`array`, optional): Change detected on the website of the person's current company. Value is a website-change category followed by a required time window via "::" (one_week, one_month, three_months, six_months, one_year). Categories: Acquisition, Branding Change, Community Engagement, Compliance Update, Contact Update, Customer Win, Event Announcement, Executive Change, Expansion, Feature Launch, Feature Update, Funding News, Geographic Expansion, Market Data, Marketing Campaign, Marketing Channel, Marketing Content, Marketing Shift, Media & Press, Operational Change, Other, Partnership Announcement, Pricing Change, Pricing Promotion, Product Expansion, Product Highlight, Product Launch, Product Removal, Product Update, Program Launch, Project Update, Recognition & Award, Service Update, Target Audience Shift, Team Expansion, Technical Update, Technology Adoption, Website Update. Example: "Product Launch::three_months". Shorter windows usually return nothing; use three_months or longer.
- `connections` (`array`, optional): LinkedIn connection count.
- `contact_method` (`array`, optional): Contact method(s) the person must have: "personal email", "work email", "mobile", "direct dial", or "office phone". Comma-separate for AND logic ("mobile,work email"), pipe-separate for OR ("mobile|direct dial").
- `country` (`array`, optional): Country as a 2-letter ISO code, e.g. US, GB. Full English names are converted. Valid values: `list_filter_values(field="country")`.
- `current_employer` (`array`, optional): Current employer / company name.
- `current_or_previous_title` (`array`, optional): Match either a current or a previous title. Pass alternatives as a list, not joined with 'or' or '|'.
- `current_title` (`array`, optional): Current job title. Pass alternatives as a list (e.g. ["VP Sales", "Head of Sales"]), not joined with 'or' or '|'.
- `degree` (`array`, optional): Education degree level.
- `department` (`array`, optional): Work department: C-Suite, Product & Engineering, Finance, HR, Legal, Marketing, Health, Operations, Sales, Education, or a sub-department like Software Development. Valid values: `list_filter_values(field="department")`.
- `email` (`array`, optional): Known email address.
- `email_grade` (`array`, optional): Minimum email confidence grade — A, A-, or B. Matches people whose best email is that grade or better. Optional modifier: A::professional only or A::personal only. Requires email-grade search to be enabled on the account.
- `employer` (`array`, optional): Match either a current or a previous employer.
- `exclude` (`object`, optional): Exclude results matching these facets. Accepts the same keys as the top-level search facets, e.g. exclude: { current_employer: ["Acme Corp"] }.
- `handle` (`array`, optional): Social-media handle.
- `health_credentials` (`array`, optional): Medical credentials.
- `health_license` (`array`, optional): Medical license.
- `health_npi` (`array`, optional): NPI number.
- `health_specialization` (`array`, optional): Medical specialization.
- `id` (`array`, optional): RocketReach profile ID(s).
- `job_change_signal` (`array`, optional): Recent job-change signal. Value is "Company Change" or "Promotion", followed by a required time window via "::" — one of one_week, one_month, three_months. Examples: "Company Change::one_month", "Promotion::one_week".
- `keyword` (`array`, optional): Free-text keyword matched across all profile fields.
- `link` (`array`, optional): LinkedIn profile URL.
- `location` (`array`, optional): City, state, or country. Optional radius: "San Francisco"::~50mi or "Paris"::~50km. Presets: `list_filter_values(field="location")`.
- `major` (`array`, optional): Education major / field of study.
- `management_levels` (`array`, optional): Seniority / management level: Founder/Owner, C-Level, Vice President, Head, Director, Manager, Senior, Individual Contributor, Entry, Intern, Volunteer. Valid values: `list_filter_values(field="management_levels")`.
- `name` (`array`, optional): Person name. Wrap a value in quotes ("Jane Doe") for an exact match.
- `order_by` (`string`, optional): Result ordering (default relevance; 'popularity' matches the Search web app). One of: `relevance`, `popularity`, `score`.
- `page_size` (`integer`, optional): Number of results to return per page (default 10, max 100).
- `phone` (`array`, optional): Known phone number.
- `phone_grade` (`array`, optional): Minimum phone confidence grade — A, A-, or B. Matches people whose best phone is that grade or better (A = valid phone + strong identity match, A- = valid phone but identity unconfirmed, B = possible / worth trying).
- `postal_code` (`array`, optional): Postal / ZIP code.
- `previous_company_id` (`array`, optional): A previous company's RocketReach ID.
- `previous_employer` (`array`, optional): A company the person worked at previously.
- `previous_title` (`array`, optional): A job title the person held previously.
- `profile_tag` (`array`, optional): Tag applied to the profile.
- `school` (`array`, optional): School or university name.
- `skills` (`array`, optional): Skills — OR logic, any listed skill matches.
- `start` (`integer`, optional): 1-based index of the first result, for pagination (default 1, max 10000).
- `state` (`array`, optional): State / region code as shown in profile locations, e.g. NY, ON. Full US and Canadian names are converted. Codes repeat across countries (WA is Washington and Western Australia), so add `country`. Valid values: `list_filter_values(field="state")`.
- `update_time` (`array`, optional): Last profile update (ISO 8601). Supports operators.
- `years_experience` (`array`, optional): Total years of work experience. Supports operators: 10+, <5, 3-7.

Example input: `{}`

### `rocketreachmcp_ping`

Ping · Read-only

Liveness check. Takes no input and returns the server name, version, and "pong".

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `rocketreachmcp_bulk_person_lookup`

Bulk Person Lookup · Destructive

Look up contact information for up to 100 people in one call. Each entry in `queries` identifies one person the same way as `person_lookup`: RocketReach profile ID, email, LinkedIn URL, NPI number (US healthcare), or name plus current employer (optionally narrowed with `title`), plus an optional per-query `lookup_type` and `metadata`. Each query is charged exactly as a single `person_lookup` would be (1 lookup credit, type depending on the user's plan or the forced `lookup_type`). Every query is validated before the batch is submitted: one invalid entry (e.g. no identifier) rejects the whole call with no credits charged. Resolved contacts are added to the user's RocketReach "My Contacts" and to the profile list named by `profile_list_name` (v2 default: "API Bulk Lookup"). Unlike `person_lookup`, bulk lookups can't apply tags. The batch is asynchronous: this returns `status: "pending"` with an `rr_request_id`. Pass that `rr_request_id` to `check_person_status` to retrieve every profile in the batch in a single call (polling is free — no credits); re-poll until no record is still `pending`.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `queries` (`array`, required): People to look up (1–100). Each needs one of: id, email, linkedin_url, npi_number, or name + current_employer.
- `profile_list_name` (`string`, optional): Name of a profile list to add the contacts to (v2 default: "API Bulk Lookup").

Example input: `{"queries":[]}`

### `rocketreachmcp_company_lookup`

Company Lookup · Destructive

Retrieve full details for a specific company — description, industry, employee count, revenue, founded year, tech stack, social links, and more — identified by domain, RocketReach company ID, name, stock ticker, or LinkedIn URL. Charges 1 `company_export` credit and requires the user to have `company_export` credits issued and available — if not, fails with `insufficient_credits` (`credit_type: "company_export"`). The `account` tool's `credit_usage` array reports whether the user has `company_export` credits issued. Adds the company to the user's RocketReach "My Companies" with default tags (`MCP Lookups` plus the AI client name) plus any tags passed via the `tags` parameter.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, optional): Company website domain, e.g. acme.com.
- `id` (`integer`, optional): RocketReach company ID.
- `linkedin_url` (`string`, optional): Company LinkedIn URL.
- `name` (`string`, optional): Company name.
- `tags` (`array`, optional): Tags to apply to the resolved company, in addition to the MCP default tags.
- `ticker` (`string`, optional): Stock ticker symbol.

Example input: `{}`

### `rocketreachmcp_email_verify`

Email Verify · Destructive

Verify a single email address with RocketReach's email verifier: it checks the address's format, confirms the domain accepts mail, and probes the mailbox on the receiving mail server. Example prompt: "Verify john@acme.com". Charges 1 `email_verification` credit — except when the result is `unknown` or the email is incorrectly formatted (`checks.format_valid` is `false`), where the credit is refunded and `credits_charged` comes back 0. `status` is one of: `valid` (the mailbox exists and accepts mail), `invalid` (the mailbox does not exist, the domain rejects mail, or the address is malformed — don't send to it), `catchall` (the domain accepts mail for any address, so this specific mailbox can't be confirmed either way — the same state `person_lookup` reports as `accept-all` in an email's `smtp_valid`), or `unknown` (the receiving server gave no usable answer, so the result is inconclusive; at most one retry, later, is worth attempting — an immediate retry will not resolve it). `checks` reports the individual signals behind that status, each `true`, `false`, or `null` when it couldn't be determined: `format_valid` (syntactically well-formed), `domain_valid` (the domain exists and accepts mail), `disposable` (a throwaway/temporary email provider), and `catchall` (the domain accepts any address). `mx_record` is the domain's primary MX host, or `null` when the domain publishes none. Verifies one address per call. If the user has no email verification credits the call fails with `insufficient_credits` and a message carrying a link to their RocketReach account; the `account` tool's `credit_usage` array reports the `email_verification` balance.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, required): Email address to verify.

Example input: `{"email":"<email>"}`

### `rocketreachmcp_person_lookup`

Person Lookup · Destructive

Look up contact information for a specific person, identified by RocketReach profile ID, email, LinkedIn URL, NPI number (US healthcare), or name plus current employer (optionally narrowed with `title`). NPI number is a standalone identifier — use it for any US healthcare lookup. Charges 1 lookup credit, of a type that depends on the user's plan, only when it finds contact info that credit covers: `standard_lookup` returns email only and charges for an A or A- email; `premium_lookup` returns email + phone and charges for an A or A- email or phone; `phone_lookup` returns email + phone and charges for an A or A- phone; `person_enrich` returns profile metadata only, no contact info, and charges whenever the profile is found. 1 `person_export` credit follows the same condition when the user has them issued (skipped otherwise). A lookup that matches no one is not charged. `lookup_type` forces a specific lookup credit type; omit to use the user's configured order. Adds the resolved contact to the user's RocketReach "My Contacts" with default tags (`MCP Lookups` plus the AI client name) and any tags passed in `tags`; `profile_list_name` additionally adds it to a named profile list. Arbitrary key/value `metadata` can be attached to the lookup record. The lookup is asynchronous: this returns either complete contact data, or `status: "pending"` with a `profile_id` to retrieve via `check_person_status` once it resolves (polling is free — no credits).

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `current_employer` (`string`, optional): Current company name. Used with `name`.
- `email` (`string`, optional): Known email address.
- `id` (`integer`, optional): RocketReach profile ID.
- `linkedin_url` (`string`, optional): LinkedIn profile URL.
- `lookup_type` (`string`, optional): Force a specific lookup credit type. Omit to use the user's configured order. An unissued type fails with insufficient_credits. One of: `standard_lookup`, `premium_lookup`, `phone_lookup`, `person_enrich`.
- `metadata` (`object`, optional): Caller-supplied key/value metadata stored with the lookup. Values: strings or integers.
- `name` (`string`, optional): Person's name. Requires `current_employer`.
- `npi_number` (`integer`, optional): Public 10-digit National Provider Identifier (NPI) assigned by CMS to healthcare providers. NPIs are publicly searchable in the NPPES registry and are used for professional provider identification. This field does not request an SSN, passport number, driver’s license number, patient identifier, or other private personal information. Standalone identifier — sufficient on its own.
- `profile_list_name` (`string`, optional): Name of a profile list to add the contact to (created if it doesn't exist).
- `tags` (`array`, optional): Tags to apply to the resolved contact, in addition to the MCP default tags.
- `title` (`string`, optional): Current job title — disambiguates when name + employer match multiple people.

Example input: `{}`

### `rocketreachmcp_profile_company_lookup`

Profile + Company Lookup · Destructive

Retrieve contact information for a person and full details for their current company in a single call. Total cost is up to 3 credits depending on the user's plan and what is found. The person side charges like `person_lookup`: 1 lookup credit, plus 1 `person_export` credit if the user has them issued, only when it finds contact info that lookup credit covers (`person_enrich` charges whenever the profile is found), and nothing when no one matches. The company side charges 1 `company_export` credit (required — fails with `insufficient_credits` if the user has no company exports issued or available). Adds the person to the user's RocketReach "My Contacts" and the company to "My Companies", both with default tags (`MCP Lookups` plus the AI client name) plus any tags passed via the `tags` parameter. `person_lookup` and `company_lookup` are the equivalent single-side calls; this combined tool charges the credits for both sides. The company side is resolved immediately; the person side is asynchronous and may return `status: "pending"` with a `profile_id` — when that happens, the company data is already included in the response and the `profile_id` resolves to contact data via `check_person_status` once ready.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `current_employer` (`string`, optional): Current company name. Used with `name`.
- `email` (`string`, optional): Known email address.
- `id` (`integer`, optional): RocketReach profile ID.
- `linkedin_url` (`string`, optional): LinkedIn profile URL.
- `lookup_type` (`string`, optional): Force a specific lookup credit type. Omit to use the user's configured order. An unissued type fails with insufficient_credits. One of: `standard_lookup`, `premium_lookup`, `phone_lookup`, `person_enrich`.
- `metadata` (`object`, optional): Caller-supplied key/value metadata stored with the lookup. Values: strings or integers.
- `name` (`string`, optional): Person's name. Requires `current_employer`.
- `npi_number` (`integer`, optional): Public 10-digit National Provider Identifier (NPI) assigned by CMS to healthcare providers. NPIs are publicly searchable in the NPPES registry and are used for professional provider identification. This field does not request an SSN, passport number, driver’s license number, patient identifier, or other private personal information. Standalone identifier — sufficient on its own.
- `profile_list_name` (`string`, optional): Name of a profile list to add the contact to (created if it doesn't exist).
- `tags` (`array`, optional): Tags to apply to the resolved contact and company, in addition to the MCP default tags.
- `title` (`string`, optional): Current job title — disambiguates when name + employer match multiple people.

Example input: `{}`

### `rocketreachmcp_report_issue`

Report Issue · Destructive

Report a RocketReach tool result that looks wrong so the RocketReach team can fix it. Use it when a RocketReach tool returned an unexpected empty or questionable result: a search returned nothing despite valid inputs, a record was not found when it should exist, or the data looks incorrect, stale, contradictory or malformed. Do not use it for results that look right, expected empty results (such as a deliberately narrow search or a lookup record with `status: "failed"`), or errors the tool returned as an `error_code`, except a `not_found` for a record that should exist. Report each distinct problem once per conversation. Describe only the tool result; leave out the conversation and the user's personal details. Briefly tell the user you reported it. If the user asks to send feedback, use `send_feedback` instead. No credits consumed.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `issue_type` (`string`, required): empty: returned nothing when it should have returned something. wrong: returned something incorrect, stale or contradictory; give the evidence in `observation` (e.g. the email domain doesn't match the current employer). error: the tool responded, but the output was malformed or missing expected fields; do not report timeouts, server errors, auth failures or credit limits. other: explain in `observation`. One of: `empty`, `wrong`, `error`, `other`.
- `observation` (`string`, required): What you expected, what the tool returned, and why it looks wrong. Describe only the tool result. At most 2000 characters.
- `tool_input` (`object`, required): The exact arguments you passed to that tool call, or `{}` if it took none.
- `tool_name` (`string`, required): The RocketReach tool whose result looks wrong. One of: `account`, `person_search`, `person_lookup`, `bulk_person_lookup`, `check_person_status`, `company_search`, `company_lookup`, `profile_company_lookup`, `email_verify`, `list_filter_values`.

Example input: `{"issue_type":"empty","observation":"<observation>","tool_input":{},"tool_name":"account"}`

### `rocketreachmcp_send_feedback`

Send Feedback · Destructive

Call this tool ONLY when the user has explicitly asked to send feedback about RocketReach or the RocketReach MCP tools. Do NOT call it proactively or as a side effect of normal tool use. No credits consumed.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `category` (`string`, required): data_quality: wrong, missing or outdated data. missing_feature: something RocketReach can't do yet. confusing_behavior: a tool did something unexpected. other: anything else. One of: `data_quality`, `missing_feature`, `confusing_behavior`, `other`.
- `feedback` (`string`, required): The user's feedback, in their own words. At most 2000 characters.
- `context` (`string`, optional): Optional. A brief description of what the user was working on when they sent the feedback, e.g. the company, person, or search it relates to. Summarize rather than paste the conversation, and leave out anything the user didn't ask to share.

Example input: `{"category":"data_quality","feedback":"<feedback>"}`

## Related

Other CRM & Sales connectors ([all 174](/agentkit/connectors/?category=crm-sales)):

- [Salesforce](/agentkit/connectors/salesforce/): Scalekit connector, OAuth, 74 tools
- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Close](/agentkit/connectors/close/): Scalekit connector, OAuth, 103 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
