
Owl24 Mcp
io.github.Madnands5v0.2.2Updated Oct 3, 2026
Hand a production error to the coding agent you already use — it claims it and writes the fix.
Overview
Lets a coding agent list, claim, and inspect production error groups from owl24, then mark them resolved after a fix.
- What it does
- Connects an MCP-speaking coding agent to an owl24 project's error data. Tools include list_errors for deduplicated error groups, queue_error and list_queue for the agent-access queue, claim_error to take ownership of an item, get_trace for spans, logs and stack traces, get_rca_report to read an existing cached AI root-cause report, resolve_error and release_error to close or give up an item, plus count_open_items and extend_claim. It cannot run a new AI root-cause analysis; that stays a separate paid action in the owl24 dashboard.
- When to use it
- Useful when you work interactively with a coding agent inside your editor and want it to pull a production error, read the trace, and draft the fix. Not needed if you already have an AGENTS.md-driven CI loop, since this reaches the same endpoints.
- Requirements
- Runs locally over stdio, typically launched with npx, so Node.js is needed. Requires the OWL24_API_KEY environment variable, taken from a project page on the owl24 dashboard, and Agent Access must be enabled for that project or every tool returns 403. OWL24_API_BASE optionally overrides the API base URL for self-hosted or local testing. Desktop clients only.
Installation
In SourceWeft
- Open Owl24 Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
owl24-mcp
MCP server for owl24 — hand a production error to the coding agent you already use (Claude Code, Cursor, or any MCP-speaking client). It claims the item, reads the trace and stack trace, and writes the fix — instead of you reading a stack trace for a file you've never opened.
This doesn't replace the REST-plus-AGENTS.md workflow — it's a thinner way to reach the exact same endpoints. If you already have an AGENTS.md-driven CI loop working, you don't need this. This is for working with your agent interactively, from inside your editor.
What it can do
What it deliberately can't do: run a new AI Root-Cause Analysis. That's a separate, paid, human action from the owl24 dashboard — this server never spends AI-RCA credit on its own initiative. get_rca_report only reads a report that already exists; if one doesn't, investigate from get_trace's data instead, the same way AGENTS.md already tells an agent to.
Billing: listing and queuing are always free. A small charge (current rate on Pricing) applies once, the moment claim_error succeeds on an item that's never been claimed before — not when it's later resolved, and with no monthly cap. If you release_error instead of fixing it, or the claim simply expires, that charge isn't refunded, but re-claiming the same item later is never billed again. resolve_error itself never adds a charge — use it once you actually have a fix, and use release_error (also free to call) when you don't, so the record stays accurate for whoever claims it next.
We don't build, run, or host your agent. This server runs locally, on your machine, using your own project API key — same trust model as the REST workflow it wraps.
Install
You don't need to install this yourself — most MCP clients run it via npx on demand.
Claude Code
Cursor
Add to your MCP settings (Cursor Settings → MCP):
Any other MCP client: the same command/args/env shape works — npx -y owl24-mcp over stdio, with OWL24_API_KEY in the environment.
Get your API key from a project's page on the owl24 dashboard. Agent Access needs to be turned on for that project first, via your account's own API — every tool here 403s until it is.
Environment variables
Example
Once connected, in Claude Code or Cursor:
What's breaking in checkout-service?
The model calls list_errors({ serviceName: "checkout-service" }), reads the results, and can go straight into get_trace for the top offender, write the fix itself, and — once you've opened the PR — resolve_error with a note. A human always reviews the PR; nothing here merges anything.
License
MIT
Source: README.md at commit 4bf2407
Tools
0Version history
1- v0.2.2LatestOct 3, 2026


