Currents Ships a CI-Testing MCP Server: 43 Tools, Split OAuth Resources, Skills over MCP

sumitsaurabh121 · reddit · 2026-11-11

CI testing platform Currents launched a hosted MCP server (https://mcp.currents.dev/mcp) that hands agents what CI recorded about each test run: the page at failure (accessibility tree, screenshots, video, Playwright trace), console and network context, and flaky history — so agents stop guessing from logs. The author focuses on the design decisions:

Transport & Auth

Streamable HTTP, stateless, POST-only (GET streams get a 405 with Allow: POST); a stdio package @currents/mcp works with an API key.
Browser OAuth sign-in capped by your Currents role; no dynamic client registration — CIMD plus an API-key fallback.
The MCP endpoint and REST API are separate OAuth resource servers; a token for one is refused by the other, so granting agent tools doesn't grant the whole API.

Tools & Permissions

43 tools covering runs, results, analytics, Actions, webhooks, share links and Jira; the tool list is filtered per connection — tools your permissions don't cover aren't listed, and calling one by name returns "doesn't exist".
currents-delete-run and currents-delete-webhook can't be undone and the server never asks for confirmation — keep clients set to confirm before writes.

Skills over MCP

Three skills (fix-failing-tests, collect-evidence, browser-evidence) are each served as both an MCP prompt and a skill:// resource; server instructions also route agents to the right skill and state that text from CI output is data, not instructions.

Listed in the MCP Registry, Claude directory, and ChatGPT/Codex plugin directory. The author asks other server authors: how do you handle DCR-only clients?

Original post →

Currents Ships a CI-Testing MCP Server: 43 Tools, Split OAuth Resources, Skills over MCP

More from coding & agent