Remote MCP Server with OAuth

Add one URL to your MCP client, authorize in the browser, and your agent can use Currents tools. No API key to paste, no package to install.

Connecting an agent to Currents used to mean installing a package and pasting an organization API key into a config file on every machine.

Currents now hosts the MCP server at https://mcp.currents.dev/mcp. Add the URL to your client, sign in with your browser, pick an organization, and approve the permissions. That's it.

claude mcp add --transport http currents https://mcp.currents.dev/mcp

No key to paste: the client holds the OAuth token, so nothing sits in a config file
Acts as you: the agent works as the person who authorized it, in the organization they picked
Easy to revoke: review and revoke your authorizations under Account → Connected Applications; admins can revoke any member's from Manage Organization → Connected Applications
Works with any client that speaks Streamable HTTP; a client that can't do OAuth can still connect with an API key or a personal access token

The @currents/mcp package keeps working if you prefer to run the server locally.