Can AI agents automate Currents?

Currents is automatable today through its hosted MCP server. This record is the Currents Playwright dashboard and test orchestrator at currents.dev, not the Playwright runner. The docs index describes Currents as a cloud platform for CI test results. The REST API is https://api.currents.dev. The authentication overview names three credentials: an organization API key with one Read Only or Read & Write level, a personal access token with named permissions and an expiry, and an OAuth grant that acts as the authorizing person inside one organization. The API getting-started page shows requests to https://api.currents.dev/v1/projects with Authorization Bearer over HTTPS. Currents hosts an MCP server at https://mcp.currents.dev/mcp and also publishes the local package @currents/mcp. The hosted server accepts a sign-in or an API key. The opened tool list covers projects, runs, spec results, failure context, evidence, quarantine actions, webhooks, and Jira issue links. Each tool requires a named permission. The hosted server lists only the tools that permission allows. currents-delete-run and currents-delete-webhook are permanent, and Currents does not ask for confirmation. A REST OAuth token is refused by the MCP endpoint, and an MCP token is refused by the REST API. Webhook tools store a URL that Currents later calls with run events. https://docs.currents.dev/llms.txt is a first-party docs index. Connector catalogs and a separate SDK page were not opened. Computer-use viability is unassessed. MCP scores 8. API scores 7. MCP is the best path because the hosted server is the documented agent interface, with permission-filtered tools, while the opened API pages establish authentication and projects without a full resource catalog.

Best path today: mcp · Overall automatability: 8/10