> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/integrations/coresignal-mcp.md). # Coresignal MCP **Coresignal MCP v2** is a server that connects Coresignal's data directly to LLM-powered applications, including Claude, Cursor, and others. It gives AI assistants access to Coresignal's multi-source company, employee, and job data from within the chat interface. The server handles query construction, authentication, credit accounting, and result delivery, enabling an agent to work with large-scale data without manually building API calls. Find available information on [GitHub](https://github.com/Coresignal-com/coresignal-mcp). ## Features * ### Per-team OAuth Access requires sign-in, with users authenticating via the Coresignal dashboard. The server verifies the signed token for each request and retrieves the team's API key, ensuring no key is stored on the server. * ### Natural-language search Describe the data you want in simple language. The server creates a query and returns relevant results. It explains the search process and what's included in the results. You may also receive follow-up questions to refine your prompt for more accurate results. * ### Data field discovery Get data you need by searching for the right data fields. Discovery uses semantic search to find all matching top-level and nested data fields related to the keywords used in the prompt. This is useful for exploring what data is available for a given entity. Data field discovery requests incur no credit cost, allowing unlimited use during query formulation. * ### Credit reporting and consent before spend Each response shows the exact credits used for the request, providing detailed per-call spending information. Small, inexpensive data previews continue seamlessly, but requests with potentially high costs require a check-in first. Before performing a large or expensive data retrieval, the server pauses to verify the scope, including the record count and estimated credit cost. * ### Automatic file delivery Inline delivery is the primary mode of interaction: results are returned as a preview, which indicates whether your prompt is efficient. A file is created instead when you request the complete available record data. The response includes a link to the file, keeping large pulls, such as thousands of records, from overwhelming the conversation, while the complete data remains available for further processing. Remember that enabling downloads from third-party tools isn't universal: review each tool's documentation to set up the required permissions (e.g. [**Claude desktop**](https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude#h_152729314d)). ## Endpoint Use the following endpoint to connect to the Coresignal MCP server: | Setting | Value | | ---------------------- | ------------------------------------------------------ | | Endpoint | `https://mcp.coresignal.com/mcp/v2` | | Transport | Streamable HTTP | | Authentication | OAuth 2.1 sign-in via the Coresignal dashboard | | Local install required | No | | API key required | No. The server fetches your team's key live on request | {% hint style="info" %} An older endpoint, `https://mcp.coresignal.com/mcp`, remains supported and is documented at the bottom of this page under Legacy Coresignal MCP. It will eventually be deprecated, so new integrations should use v2. {% endhint %} ## Prerequisites Before you begin, ensure you have: * A Coresignal account. If you don't have one yet, you can register in Coresignal [dashboard](https://dashboard.coresignal.com/sign-up). * Available credits for search, record pull, and email enrichment actions. * An MCP-compatible client that supports remote servers over Streamable HTTP. * A browser for the one-time sign-in flow. ## Connect Coresignal MCP Choose the option to add a custom or remote server and use `https://mcp.coresignal.com/mcp/v2` to connect to Coresignal MCP. Several MCP-compatible clients integrations steps are listed below. ### Claude Code Run this in your terminal: {% code lineNumbers="true" expandable="true" %} ``` claude mcp add coresignal --transport http https://mcp.coresignal.com/mcp/v2 ``` {% endcode %} Then verify the connection: {% code lineNumbers="true" expandable="true" %} ``` claude mcp list # coresignal: https://mcp.coresignal.com/mcp/v2 (HTTP) - / Connected ``` {% endcode %} ### Codex Run this in your terminal: {% code lineNumbers="true" expandable="true" %} ``` codex mcp add coresignal --url https://mcp.coresignal.com/mcp/v2 ``` {% endcode %} Then verify the connection: {% code lineNumbers="true" expandable="true" %} ``` codex mcp list # coresignal: https://mcp.coresignal.com/mcp/v2 (HTTP) - / Connected ``` {% endcode %} ### AntigravityCLI Edit `~/.gemini/config/mcp_config.json` file {% code lineNumbers="true" expandable="true" %} ``` { "mcpServers": { "coresignal": { "url": "https://mcp.coresignal.com/mcp/v2" } } } ``` {% endcode %} ### OpenCode Run this in your terminal: {% code lineNumbers="true" expandable="true" %} ``` opencode mcp add coresignal --url https://mcp.coresignal.com/mcp/v2 ``` {% endcode %} Then verify the connection: {% code lineNumbers="true" expandable="true" %} ``` opencode mcp list # coresignal: https://mcp.coresignal.com/mcp/v2 (HTTP) - / Connected ``` {% endcode %} ### Cursor Open **Settings → Tools & MCPs → Add Custom MCP** and paste: {% code lineNumbers="true" expandable="true" %} ``` { "mcpServers": { "coresignal": { "url": "https://mcp.coresignal.com/mcp/v2" } } } ``` {% endcode %} ## Available tools and cost All requests use the same Coresignal credit balance as other activities in your account. Costs are fixed per action and are included in each response. | Tool | Action | Description | Credits | | --------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- | | `entity_search` | Natural-language search | Describe the data you want in natural language. The server builds a query, explains the search, and returns results with an exact-match count and a preview. | 20 credits per search | | `entity_fields` | Data field discovery | Semantic search across top-level and nested fields, for scoping a query or exploring what's available on an entity. | Free | | `entity_fetch` | Full profile pull | Retrieve a complete company, employee, or job record. | 1-20 credits per record. See [Pricing](https://docs.coresignal.com/pricing/) | | `email_enrich` | Email enrichment |

Get a publicly accessible, strictly business-related work email for an employee.
The system's public email lookups automatically exclude employees in the EEA and UK to comply with GDPR. Blocked lookups are not charged.

| 10 credits per email | ## Limitations Coresignal MCP has several limitations: * Business-related email enrichment cannot be provided for employees in the European Economic Area (EEA) and the United Kingdom (UK) due to privacy regulations. * Tool availability may vary by MCP client and rollout status. ## Sample queries and flows See illustrative sample flows that can help you craft your own requests effectively. {% hint style="info" %} All personal/company information mentioned within this context is entirely fictional and is solely intended for illustrative purposes. {% endhint %}
Lead generation and enrichment 1. Describe what you are looking for Client types: {% prompt description="Find marketing directors at US software companies with 200–1,000 employees." %} ```markdown Find marketing directors at US software companies with 200–1,000 employees. ``` {% endprompt %} Assistant replies: > *8,214 people match. Here are the first 10 so you can check the fit – each one shows the exact role that matched your criteria.* 2. Narrow it down Client types: {% prompt description="Only companies that raised funding in the last two years." %} ```markdown Only companies that raised funding in the last two years. ``` {% endprompt %} Assistant replies: > *Now 1,930 people. The preview shows each person's company and its latest funding round.* 3. Build the list – delivered as a file Client types: {% prompt description="Great – pull the top 50 with name, title, company, and profile, as a file." %} ```markdown Great – pull the top 50 with name, title, company, and profile, as a file. ``` {% endprompt %} Assistant replies: | Name | Title | Company | Location | | -------------- | ------------------ | ------------------- | ------------- | | Sarah Mitchell | VP Marketing | Brightpath Software | Austin, TX | | Daniel Okafor | Marketing Director | Cloudline Systems | Denver, CO | | Emma Ruiz | Head of Growth | Parkstone Labs | San Diego, CA | *… full 50 in the file below.* {% code title="" expandable="true" %} ``` FILE marketing-directors-top50.jsonl 50 complete records · private download link, ready for CRM import ``` {% endcode %}
Investment research or due diligence 1. Describe what you are looking for Client types: {% prompt description="Tell me everything about Voltaic Dynamics (voltaicdynamics.com)." %} ```markdown Tell me everything about Voltaic Dynamics (voltaicdynamics.com). ``` {% endprompt %} Assistant replies: > *Voltaic Dynamics · Industrial robotics · Munich, DE* | Founded | 2016 | | -------------- | ----------------------------- | | Headcount | 412 – +34% year over year | | Latest funding | Series C, $60M (Oct 2025) | | Key executives | 11 listed, with arrival dates | 2. Ask about the leadership team Client types: {% prompt description="Who joined or left the leadership team in the last year?" %} ```markdown Who joined or left the leadership team in the last year? ``` {% endprompt %} Assistant replies: > *2 arrivals (a CTO in Jan 2026, a VP Sales in Mar 2026), 1 departure (CFO, Nov 2025) — pulled from the same profile, no extra cost.* 3. Get details about the growth signals Client types: {% prompt description="How many roles are they hiring for right now, and in which teams?" %} ```markdown How many roles are they hiring for right now, and in which teams? ``` {% endprompt %} Assistant replies: > *23 open roles – 14 in engineering, 9 in sales. Hiring velocity as a due-diligence signal, in one question.* 4. Export a file Client types: {% prompt description="Export the complete profile as a file." %} ```markdown Export the complete profile as a file. ``` {% endprompt %} Assistant replies: {% code title="" expandable="true" %} ``` FILE voltaic-dynamics-full-profile.jsonl The entire company record, every field · private download link for the data room ``` {% endcode %}
Market or competitive analysis 1. Describe what you are looking for Client types: {% prompt description="How many companies in Germany sell HR software?" %} ```markdown How many companies in Germany sell HR software? ``` {% endprompt %} Assistant replies: > *1,204 companies match. Want a preview, a breakdown, or the full list?* 2. Ask for other countries Client types: {% prompt description="Same question for the UK, France, and the Nordics." %} ```markdown Same question for the UK, France, and the Nordics. ``` {% endprompt %} Assistant replies: | Market | HR software companies | | -------------- | --------------------- | | Germany | 1,204 | | United Kingdom | 986 | | France | 743 | | Nordics | 611 | *Illustrative counts.* 3. Build the list – delivered as a file Client types: {% prompt description="Export the full German list as a file for my spreadsheet." %} ```markdown Export the full German list as a file for my spreadsheet. ``` {% endprompt %} Assistant replies: 
FILE german-hr-software-companies.jsonl
1,000 records · download link, ready for a spreadsheet or CRM import
## Legacy Coresignal MCP **Legacy Coresignal MCP** is a server that connects Coresignal's latest Multi-source Company API, Multi-source Employee API, and Base Jobs API information directly within chat interface. ### Prerequisites To connect to the remote Legacy Coresignal MCP server using `mcp-remote` you need to have [Node.js](https://nodejs.org/en/download) installed. {% hint style="info" %} We recommend using Node.js v24 for optimal compatibility and performance with Legacy Coresignal MCP. Node.js v24 is the version we validate and support to ensure a smooth setup experience. {% endhint %} Credits for requests performed through the MCP server will also be deducted from the same credit balance. ### Integration with AI assistants Learn integration steps for a few AI assistant tools. {% hint style="warning" %} Enter your API Key as the `` value. Get your key from Coresignal's [self-service platform](https://dashboard.coresignal.com/sign-in). Do not forget to refresh the tool after the integration steps. {% endhint %} #### Claude Desktop To set up your Claude Desktop assistant, add this entry to your claude\_desktop\_config.json file: {% code title="Access" %} ```json { "mcpServers": { "coresignal_data_api": { "command": "npx", "args": [ "mcp-remote", "https://mcp.coresignal.com/mcp", "--header", "apikey:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "" } } } } ``` {% endcode %} #### Cursor Cursor has integrated support for MCP servers: 1. Go to: Cursor > Settings > Cursor Settings > MCP 2. Click on the `Add new global MCP server` button 3. Add the following configuration: {% code title="Access" %} ```json { "mcpServers": { "coresignal_data_api": { "command": "npx", "args": [ "mcp-remote", "https://mcp.coresignal.com/mcp", "--header", "apikey:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "" } } } } ``` {% endcode %} ### Available tools The Legacy Coresignal MCP server gives access to several API data entities: * **coresignal\_company\_multisource\_api** – data from Multi-source Company API * **coresignal\_employee\_multisource\_api** – data from Multi-source Employee API * **coresignal\_job\_api** – data from Base Job API --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.coresignal.com/integrations/coresignal-mcp.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.