Local MCP Server

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

The @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, which needs nothing installed and signs each person in with their own role.

Set it up

Create an API key, then add this to your client's MCP configuration, for example mcp.json in Cursor or claude_desktop_config.json in Claude Desktop:

{
  "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 lists them; the repository README 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.