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

# Connect Coresignal MCP to OpenCode

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

### What is OpenCode?

OpenCode is an open-source coding agent available in the terminal, as a desktop app, and in IDEs. Because it is not tied to a single AI provider, you can choose the model it uses. OpenCode reads and edits code, runs commands, and accesses external tools and data through MCP servers.

Developers, data engineers, and technical GTM teams can add Coresignal MCP to OpenCode to search, enrich, and export Coresignal data without leaving their development environment.

### How to connect Coresignal to OpenCode?

{% 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 %}
Add Coresignal to your `opencode.json` file under `mcp`. Use the project's `opencode.json` to enable it for one project, or `~/.config/opencode/opencode.json` to enable it everywhere

{% hint style="info" %}
Keep `"type": "remote"` and the `/v2` endpoint, and make sure the file is valid JSON. Mistakes here are the most common cause of setup issues.
{% endhint %}
{% endstep %}

{% step %}
Sign in to Coresignal:

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

```
opencode mcp auth coresignal
```

{% endcode %}
{% endstep %}

{% step %}
Open OpenCode mcp and add Coresignal:

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

```
opencode mcp add coresignal --url https://mcp.coresignal.com/mcp/v2
```

{% endcode %}
{% endstep %}

{% step %}
Verify the connection:

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

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

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

Your browser opens the Coresignal dashboard. Sign in and approve access. OpenCode stores the credentials, so you only need to do this once.

### FAQ

<details>

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

Common issues when setting up Coresignal MCP in OpenCode are:

* skipping `opencode mcp auth coresignal`
* a missing `"type": "remote"` in the entry
* invalid JSON
* still using the old endpoint without `/v2`

Run `opencode mcp debug coresignal` to test the connection and sign-in.

</details>

<details>

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

To remove the server, delete the `coresignal` entry from `opencode.json`. To sign out but keep the server, run `opencode mcp logout coresignal`.

</details>

<details>

<summary>How do I add a remote MCP server to OpenCode?</summary>

Run `opencode mcp add coresignal --url https://mcp.coresignal.com/mcp/v2`, then verify with `opencode mcp list`. When your browser opens the Coresignal dashboard, sign in and approve access. OpenCode stores the credentials, so you only sign in once.

</details>

<details>

<summary>Which AI models can I use with Coresignal MCP in OpenCode?</summary>

OpenCode is not tied to a single AI provider, so you can choose which model it uses. Coresignal MCP connects through OpenCode’s MCP setup, so it is available whichever model you pick.

</details>

<details>

<summary>How many credits does Coresignal MCP use in OpenCode?</summary>

That depends on the task. While field discovery and reading delivered files are free, a full profile pull can cost 1–20 credits per record. See our [pricing](https://docs.coresignal.com/pricing/).

</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/opencode.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.
