> 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/claude.md). # Claude Desktop and Claude.ai Connect Currents to Claude Desktop and Claude.ai from the Claude connectors directory, for yourself or for your whole Claude organization Currents is listed in the Claude connectors directory at [claude.ai/directory/currents](https://claude.ai/directory/currents). A connector belongs to your Claude account rather than to one device, so connecting once makes Currents available in Claude Desktop, Claude.ai, the Claude mobile app, Cowork and [Claude Code](https://docs.currents.dev/ai/connect/pages/fQ7ybzGCSS1uPAoEqVbM#use-the-connector-from-claude.ai). ## Connect from the Claude directory {% tabs %} {% tab title="Free, Pro and Max" %} 1. Open [claude.ai/directory/currents](https://claude.ai/directory/currents). Or, in Claude Desktop or Claude.ai, open **Customize → Connectors**, select **Discover** and search for **Currents**. 2. Click **Connect to Claude**, then [sign in](#sign-in). The directory listing works on every plan, including Free, and there is no URL to enter. {% endtab %} {% tab title="Team and Enterprise" %} An Owner adds Currents for the organization first: 1. Open [claude.ai/directory/currents](https://claude.ai/directory/currents). 2. Click **Connect for your team**. Currents is now available to everyone in the organization. 3. Click **Connect to Claude** to connect your own Currents account. Owners can also add Currents from **Organization settings → Connectors → Browse connectors**. Each member then connects with their own Currents account: 1. Open **Customize → Connectors** and find **Currents**. 2. Click **Connect to Claude**, then [sign in](#sign-in). On a Team plan, a member without permission to enable connectors sees **Request** instead of a connect button. **Request** sends the request to the organization's Owners, who approve it under **Organization settings → Connectors**. Adding the connector gives nobody access to Currents data. Each member signs in to Currents themselves, and their connection carries their own Currents role. {% endtab %} {% endtabs %} ## Sign in **Connect to Claude** opens a Currents sign-in page. Sign in, choose the organization Claude will work in, and approve the permissions Claude asks for. The browser then returns you to Claude, and the connector shows as connected. See [Sign in once](/ai/connect.md#sign-in-once) for what each screen shows. ## Use it in a chat Click **+** at the bottom left of the message box, open **Connectors**, and make sure **Currents** is turned on for the conversation. Then ask about your projects: > Which tests in `` were flakiest on main this week, and why? The **Search and tools** menu lets you turn off individual Currents tools before Claude calls them. Turn off the ones a conversation does not need, especially `currents-delete-run`, which permanently deletes a run. Currents does not ask for confirmation. ## Disconnect Disconnecting in **Customize → Connectors** removes Currents from Claude. To revoke Claude's access from the Currents side, see [Revoke a connection](/ai/connect.md#revoke-a-connection). ## Other ways to connect ### Add Currents by URL Use a custom connector only when the directory listing is not available to you. **Free, Pro and Max:** 1. In Claude Desktop or claude.ai, open **Customize → Connectors**. 2. Click **+**, then **Add custom connector**. 3. Name it `Currents` and enter the URL `https://mcp.currents.dev/mcp`. 4. Leave **Advanced settings** empty. Claude identifies itself to Currents on its own, so there is no client ID or secret to enter. 5. Click **Add**, then **Connect**. On the Free plan, Claude allows one custom connector. **Team and Enterprise:** an Owner opens **Organization settings → Connectors**, clicks **Add**, hovers over **Custom** and chooses **Web**, enters `https://mcp.currents.dev/mcp` with **Advanced settings** empty, and clicks **Add**. Members then connect as described in the **Team and Enterprise** tab above. ### If you added Currents by URL before A custom connector you added earlier keeps working. It shows under **Custom** in **Customize → Connectors**, and the directory listing shows Currents as not connected. Connecting from the directory without removing it gives you two Currents connections. To move to the directory listing: 1. In **Customize → Connectors**, open the Currents connector under **Custom**. 2. Open the three-dot menu and select **Remove**. On Team and Enterprise plans, an Owner removes it under **Organization settings → Connectors**. 3. Connect from [claude.ai/directory/currents](https://claude.ai/directory/currents) and sign in again. ### Run the server on your computer Claude Desktop can also run the Currents MCP server on your computer, with an API key instead of your own sign-in. This works in Claude Desktop only, not on Claude.ai. Open **Settings → Developer → Edit Config** and add the configuration from [Local MCP Server](/ai/connect/local.md) to `claude_desktop_config.json`, then restart Claude Desktop. A local setup creates no entry under **Connected Applications**: the key keeps working until an Admin revokes it under **Organization → API Keys**. The connector from the directory needs nothing installed, and its access follows your own Currents role. ## Troubleshooting | What you see | What to do | | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | Claude does not use Currents | Check that **Currents** is turned on under **+ → Connectors** for this conversation. | | The wrong organization's data | Disconnect, connect again, and choose the other organization. | | Two Currents connectors in the list | One is a custom connector added by URL. Remove the one under **Custom**. See [If you added Currents by URL before](#if-you-added-currents-by-url-before). | For other errors, see [Troubleshooting](/ai/connect.md#troubleshooting). --- # 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/claude.md?ask=&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.