How to connect the Currents MCP server

Before you start

• A Currents account and membership in the organization you connect to. Each connection reaches one organization, chosen at sign-in. docs.currents.dev/ai
• 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. docs.currents.dev/aidocs.currents.dev/ai
• If the server answers 403 organization_not_enabled, the endpoint is not served to that organization; contact Currents support. docs.currents.dev/ai
• 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. docs.currents.dev/aidocs.currents.dev/authentication

Authentication

Your client → Currents MCP

OAuth sign-in, handled by your MCP client. docs.currents.dev/aidocs.currents.dev/authenticationmodelcontextprotocol.io/specification

Currents MCP → Currents API

The server acts on your account with the access you approve. docs.currents.dev/aidocs.currents.dev/authentication

Steps

1. Open Currents's MCP connection instructions

   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.

   docs.currents.dev/aidocs.currents.dev/airegistry.modelcontextprotocol.io/v0.1
3. Sign in to Currents, pick the organization and approve the permissions
   docs.currents.dev/ai
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.

   docs.currents.dev/ai
5. List the server's tools

   Your client should list the server's tools. That confirms the connection, not every API permission.

   docs.currents.dev/ai

What we observed

• 5 Nov 2026: HTTP 401 with WWW-Authenticate resource_metadata https://mcp.currents.dev/.well-known/oauth-protected-resource/mcp, which names the authorization server https://id.currents.dev.