> 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/claude-code.md).

# Connect Coresignal MCP to Claude Code

Connect Claude Code to Coresignal MCP to search, enrich, and export data from your development environment.

### What is Claude Code?

Claude Code is Anthropic's agentic coding tool. It runs in the terminal, in IDEs such as VS Code and JetBrains, and in the Claude desktop app. It can read and edit code, run commands, and use external tools and data through MCP servers. It’s suitable for developers, data engineers, and technical GTM teams who want to search, enrich, and export Coresignal data without leaving their development environment, and use the results directly in scripts, pipelines, and applications they are building.

{% hint style="info" %}
Use `https://mcp.coresignal.com/mcp/v2` to connect to Coresignal MCP.
{% endhint %}

### Available tools and credits

Coresignal MCP gives Claude Code five tools: natural-language search, data field discovery, full profile pulls, contact enrichment, and paginated reading of delivered files. Field discovery and reading delivered files are free; other actions use your Coresignal credit balance, and each response shows the exact credits spent. Large results are delivered as a file with a download link instead of inline.

Before you start bundling Coresignal’s MCP with Claude Code, ensure that you have:

* Coresignal account with available credits
* Claude Code installed. See the [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp) for general MCP options

### How to connect Coresignal to Claude Code?

{% stepper %}
{% step %}
Make sure you have a Coresignal account with available credits. If you don't have one yet, sign up in the [Coresignal dashboard](https://dashboard.coresignal.com/sign-up).
{% endstep %}

{% step %}
Run this in your terminal to add the server:

{% code lineNumbers="true" expandable="true" %}

```
claude mcp add coresignal --transport http https://mcp.coresignal.com/mcp/v2
```

{% endcode %}
{% endstep %}

{% step %}
Check the connection:

{% code lineNumbers="true" expandable="true" %}

```
claude mcp list
# coresignal: https://mcp.coresignal.com/mcp/v2 (HTTP) - / Connected
```

{% endcode %}
{% endstep %}
{% endstepper %}

### Verify connection

Once the server is connected, it is worth a quick check:

* `claude mcp list` shows coresignal as Connected
* A free field discovery prompt returns results, for example: "Which fields are available for employee records?"
* A search response shows the credits used for the request

### FAQ

<details>

<summary>Do I need an API key to connect Claude Code to Coresignal?</summary>

No. Coresignal MCP uses OAuth 2.1 sign-in through the Coresignal dashboard. The server fetches your team’s API key live for each request, so no key is stored. You just sign in through `/mcp` in an interactive Claude Code session.

</details>

<details>

<summary>How does Claude Code handle large Coresignal MCP results?</summary>

To avoid overwhelming the conversation, a file is created when you request the complete available record data. The response includes a link to the file with a large volume of records, while the remaining data stays available for further processing.

</details>

<details>

<summary>What can I ask Claude Code to do with Coresignal data?</summary>

You can ask Claude Code to search companies, employees, and jobs in natural language, discover fields, pull full profiles, enrich business emails, and read delivered files.&#x20;

</details>

<details>

<summary>What are the most common Coresignal MCP setup issues in Claude Code?</summary>

Common Coresignal MCP setup issues in Claude Code include:

* adding the server without `--scope user`, so it is missing in other projects
* skipping the `/mcp` sign-in, or attempting it in a non-interactive `claude -p` run
* the browser not opening (open the URL manually)
* an outdated endpoint without `/v2`
* no available Coresignal credits

</details>

<details>

<summary>How do I remove Coresignal MCP from Claude Code or sign out?</summary>

Run `claude mcp remove coresignal` to remove the server and its stored token. If you added it with a scope, include it, e.g. `--scope user`. To sign out but keep the server, type `/mcp`, select coresignal, and choose **Clear authentication**.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/integrations/coresignal-mcp/claude-code.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
