# How to connect the Currents MCP server

To connect the official Currents MCP server, add https://mcp.currents.dev/mcp to your MCP client as a Streamable HTTP server, then sign in with OAuth when your client prompts you. If your client can't complete the OAuth sign-in, use an API key. Currents documents setup for Claude Code, Cursor, Claude, Codex, ChatGPT and VS Code.

- Endpoint: https://mcp.currents.dev/mcp
- Transport: Streamable HTTP
- Registry: dev.currents/mcp 1.0.0
- Publisher documentation reviewed: 2026-11-05 (not a tested connection)
- Guide page: https://apitracker.io/mcp-guides/currents-mcp

## Before you start

- A Currents account and membership in the organization you connect to. Each connection reaches one organization, chosen at sign-in.
- Your role caps the permissions you can approve; for example, a Guest can approve reading projects and results only. Tools outside your permissions are not listed.
- If the server answers 403 organization_not_enabled, the endpoint is not served to that organization; contact Currents support.
- Currents does not accept dynamic client registration. A client must identify itself with a Client ID Metadata Document or be one Currents ships a definition for; otherwise use an API key.

## Steps

1. **Open Currents's MCP connection instructions** <https://docs.currents.dev/ai/connect>
2. **Add the Currents MCP server to your client** Add https://mcp.currents.dev/mcp as a remote MCP server that uses the Streamable HTTP transport, and leave any client ID and secret empty. The server is stateless and answers POST only. Currents also publishes a Claude directory listing, a ChatGPT plugin directory listing, and a Cursor install link.
3. **Sign in to Currents, pick the organization and approve the permissions**
4. **If your client can't complete the OAuth sign-in, use an API key** Create an API key under Organization, API Keys and send it in the Authorization header as a bearer token. A key acts as the organization, not as a person, and has one access level: Read Only or Read & Write. Removing the server from the client does not revoke the key; an admin must revoke it. Keep the key in a secret store, not in shared configuration.
5. **List the server's tools**

## Questions

### What is the Currents MCP server URL?

The official Currents MCP server is at https://mcp.currents.dev/mcp and uses the Streamable HTTP transport.

### How do I authenticate with the Currents MCP server?

Sign in with OAuth when your client prompts you. If your client can't complete the OAuth sign-in, use an API key: Create an API key under Organization, API Keys and send it in the Authorization header as a bearer token. A key acts as the organization, not as a person, and has one access level: Read Only or Read & Write. Removing the server from the client does not revoke the key; an admin must revoke it. Keep the key in a secret store, not in shared configuration.

### Which AI clients can use the Currents MCP server?

Currents's documentation covers Claude Code, Cursor, Claude, Codex, ChatGPT and VS Code. Other clients that support remote Streamable HTTP MCP servers may also work.

### What do I need before connecting Currents MCP?

A Currents account and membership in the organization you connect to. Each connection reaches one organization, chosen at sign-in. Your role caps the permissions you can approve; for example, a Guest can approve reading projects and results only. Tools outside your permissions are not listed. If the server answers 403 organization_not_enabled, the endpoint is not served to that organization; contact Currents support. Currents does not accept dynamic client registration. A client must identify itself with a Client ID Metadata Document or be one Currents ships a definition for; otherwise use an API key.

### Has this Currents MCP guide been tested?

Currents's documentation was reviewed on 2026-11-05. It is not a tested connection; your account and permissions decide which tools work.

## Sources

- https://docs.currents.dev/ai/connect (checked 2026-11-05)
- https://docs.currents.dev/ai/connect/remote (checked 2026-11-05)
- https://docs.currents.dev/authentication/oauth (checked 2026-11-05)
- https://registry.modelcontextprotocol.io/v0.1/servers/dev.currents%2Fmcp/versions/1.0.0 (checked 2026-11-05)
- https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization (checked 2026-11-05)

Guide JSON: https://github.com/apideck-libraries/mcp-connect/blob/626f6a146170ded34891b30dca3af26f09e07466/proposals/connection-guide/0.1/reviewed/guides/currents-mcp.json