Where it fits
QA and engineering teams using Currents who want test diagnostics and run control from an AI client.
- Diagnose a flaky test from recent runs.
- Cancel or delete a run that is no longer needed.
- Create a Jira issue from a failure.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Currents
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Dispatches one agent per independent problem domain so unrelated failures can be investigated concurrently, then reviews and integrates the results. Use it when failures are separate, need no shared context, and can run without interfering.
For carrying out an implementation plan inside the current session, with the agent acting as the implementer itself. That happens when the human partner picked inline execution or when no subagent tool is available.
Helps decide how to integrate finished work after implementation and passing tests. Presents structured choices for merging locally, pushing and creating a pull request, or keeping the branch.
No skills found
Try a different search term or clear the filters.
Local stdio via npx
Set CURRENTS_API_KEY for the Currents project. Desktop and editor clients add this as a stdio server; the hosted endpoint https://mcp.currents.dev/mcp is an alternative remote transport for clients that support remote connectors.
- Create a Currents API key
Generate the key in Currents and keep it out of source control.
- Add the stdio server
Point your client at npx -y @currents/mcp with CURRENTS_API_KEY in the environment.
- Reload and check the tool list
Read-only tools list projects and runs; write tools such as currents-delete-run, currents-cancel-run and currents-create-webhook appear in the same list, so grant the key only where those actions are acceptable.
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name currents. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
currentsappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Diagnose a flaky test from recent runs. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
- The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Currents repositoryhttps://github.com/currents-dev/currents-mcp