Runheed MCP Server

by runheed Your server? Claim it

answering

Runheed is answering right now. Last checked 6 min ago. It exposes 9 tools.

Production errors your coding agent can read: search, stack traces, context, trends, resolve.

Uptime history 7 hours of history

7 hours agonow

100.0%

Uptime 24h

23 of 23 checks

Tools

read from the server

394 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Runheed every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add runheed --transport http https://runheed.com/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://runheed.com/api/mcp

~/.codex/config.toml

[mcp_servers.runheed]
url = "https://runheed.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "runheed": {
      "url": "https://runheed.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "runheed": {
      "type": "http",
      "url": "https://runheed.com/api/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

runheed

runheed_get_error

Returns one error group in full: message, status, counts, first and last seen, environment, agent context, the top stack frames and the latest breadcrumbs.

runheed_get_error_context

Returns everything recorded around an error: every breadcrumb, platform, runtime, OS, environment, release, the affected user, the agent session and extra data.

runheed_get_project_health

Returns a 0 to 100 health score for a project (or the whole workspace), errors in the last 24 hours, the unresolved count, the error rate, recent issues and recommendations.

runheed_get_recent

Returns the error groups seen most recently, newest first, with status, type, message, event count, last-seen time and ID.

runheed_get_trends

Returns error statistics for the last 24 hours, 7 days or 30 days: total, new and resolved counts, the most frequent errors and the hourly error rate.

runheed_ignore_error

Marks an error group ignored, for known or expected errors, so new occurrences stop alerting. Returns a confirmation.

runheed_resolve_error

Marks an error group resolved, with an optional note such as the fixing commit. The group reopens on its own if the error happens again. Returns a confirmation.

runheed_search_errors

Searches the workspace's error groups by text (type or message), status and project. Returns each matching group with its status, type, message, event count, last-seen time and ID.

runheed_unignore_error

Moves an ignored error group back to unresolved, so new occurrences alert again. Returns a confirmation.

Endpoints

URL	Transport	State	Latency	Checked
https://runheed.com/api/mcp	streamable-http	answering	382 ms	6 min ago

Alternatives to Runheed

same job, measured the same way

Llama Logger

by llamalogger

Exception tracking for .NET. Let your AI coding agent search and triage errors and stack traces.

answering

Flare

by flareapp

Error tracking for Laravel and PHP apps. Let your agent fetch errors, stack traces and context.

answering

ForgeOps

by getforgeops

Production errors and incidents for your agent: stack traces, breadcrumbs, likely causes, triage.

answering

Condux error monitoring

by condux

Read your Condux issues, events and stack traces (deminified with source maps). Triage optional.

answering

Auralogs

by auralogs

Read-only access to Auralogs production logs: search logs, inspect errors, review AI analyses.

7 tools answering

LogBrew

by logbrew

Read LogBrew errors, slow traces, logs, and product analytics, and triage issues with consent.

answering

Jamp

by jdwilliums

Agent-run site monitoring: install JAMP, read errors, uptime, vitals and traffic, resolve fixes.

38 installs/wk answering

Talaria

by newtalaria

Errors, traces, replays and logs from Talaria for coding agents.

answering

Runheed — questions

Answers built from our own checks of this server.

What can Runheed do?

It exposes 9 tools, read directly from the server on our last check. Among them: runheed_get_error, runheed_get_error_context, runheed_get_project_health, runheed_get_recent, runheed_get_trends, runheed_ignore_error and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Runheed working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 23 of 23 checks got a reply (100.0%), average response time 394 ms. The bar chart above shows every period we have measured.

How do I connect Runheed?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Runheed need an API key?

No. Runheed completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Runheed?

It answers our handshake in 394 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.