> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/ai/connect/local.md).

# Local MCP Server

Run the Currents MCP server on your own machine with the @currents/mcp package and an API key

The [`@currents/mcp`](https://github.com/currents-dev/currents-mcp) package runs the Currents MCP server on your machine, over `stdio`, with an API key. Use it only when your client cannot connect to the [hosted Currents MCP server](/ai/connect/remote.md), which needs nothing installed and signs each person in with their own role.

## Set it up

Create an [API key](/dashboard/administration/api-keys.md), then add this to your client's MCP configuration, for example `mcp.json` in Cursor or `claude_desktop_config.json` in Claude Desktop:

```json
{
  "mcpServers": {
    "currents": {
      "command": "npx",
      "args": ["-y", "@currents/mcp"],
      "env": {
        "CURRENTS_API_KEY": "your-api-key"
      }
    }
  }
}
```

The client downloads and starts the package. Then ask, for example: "Tests are failing in CI. Get the details for the last run on main and fix the failures."

## Permissions

The server can do only what the key allows. With a **Read Only** key, every write is refused with `403`. Use a Read Only key unless the agent needs to write.

The server lists every tool, whatever the key allows. [MCP tools and permissions](/ai/reference/mcp-server.md) lists them; the [repository README](https://github.com/currents-dev/currents-mcp) lists the tools in each version. With a **Read & Write** key, `currents-delete-run` and `currents-delete-webhook` delete without confirmation and cannot be undone.


---

# 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.currents.dev/ai/connect/local.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.