MCP.Market

Owl24 MCP server

by Madnands5·io.github.Madnands5/owl24-mcp·v0.2.2
No reviews yet

Hand a production error to the coding agent you already use — it claims it and writes the fix.

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars73 downloads/wk

Reviews

Write one

Nobody has reviewed Owl24 yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Owl24 tools (10)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • claim_error

    Claims one queue item by its numeric id (from list_queue), so no other agent works it at the same time. IMPORTANT: this is what triggers billing (see the owl24 Pricing page) - the first time an item is ever claimed, it's billed once, immediately, with no monthly cap; resolving or releasing it afterward never bills it again. Returns a 409-shaped error if something else already holds the claim withi

  • count_open_items

    Returns just the count of open (unresolved) queue items, without the cost of fetching the full list - call this on every poll and only call list_queue when the count is greater than 0. Matches GET /api/v1/agent-access/count.

  • extend_claim

    Pushes a claim's expiry another claim-TTL window out. Use this if you're still actively working an item and getting close to claim_expires_at (from claim_error's or list_queue's response) - the alternative is racing the clock and risking another agent claiming it out from under you. Free, and does not affect billing either way.

  • get_rca_report

    Checks whether a human already ran (and paid for) AI Root-Cause Analysis on this trace, and returns it if so. Read-only - this tool NEVER runs a new analysis or spends AI-RCA credit. Returns {found: false} for the normal case where no report exists yet; that is not an error, and is not a reason to wait for one - investigate from get_trace's data instead. Running a new analysis is a deliberate, pai

  • get_trace

    Fetches the spans, logs, and stack trace for one trace_id (from list_errors' sample_trace_id or list_queue's trace_id). This is the primary evidence to investigate from - most queued items have no AI report attached (queuing never runs one), so read this before assuming one exists.

  • list_errors

    Lists deduplicated error groups for this project - one row per distinct bug, with occurrence count, first/last seen, which service it's in, whether it's already queued/claimed/resolved (queue_state), and whether a cached AI root-cause report already exists for it (has_report). Use this to answer "what's breaking in <service>" - filter with serviceName. Each group's `fingerprint` is what you pass t

  • list_queue

    Lists items already in the agent-access queue, each with its numeric id (what claim_error/resolve_error need), fingerprint, trace_id, service_name, and claim state. Defaults to open (unclaimed, unresolved) items only - the actual work queue. Pass status: "all" or "resolved" to see history instead.

  • queue_error

    Adds one or more error groups (by fingerprint, from list_errors) to the agent-access queue. Free, and never calls an AI provider - this only marks errors as ready for an agent to claim and investigate. Safe to call again on an already-queued-and-open fingerprint (a no-op, reported back as "skipped").

  • release_error

    Releases a claimed item back to open WITHOUT resolving it - use this when you can't actually find or confirm the cause, instead of marking it resolved with a "couldn't fix" note. This never adds a new charge on top of the claim - if that claim was billable, releasing it doesn't refund the charge either, but re-claiming the same item later (by you or anyone else) is never billed again. `reason` is

  • resolve_error

    Resolves a queue item once you have opened a pull request for it. Always include the PR link and the fingerprint you believe you fixed in resolutionNote (e.g. "Opened myorg/myrepo#123 - fixes fingerprint <fingerprint>") - that is what lets a later check confirm the error actually stopped recurring. Resolving is a permanent record, not a delete, and does not require you to be the one who claimed it

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Owl24 compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 68% of 4,460 AI and agents servers
Tools
10
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
73
more than 55% of 1,538 AI and agents servers with a package

What its tools let an agent do: 10 read

Install Owl24 in Claude Code, Cursor or VS Code

Runs npx -y owl24-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add owl24-mcp -- npx -y owl24-mcp
Add to Cursor

What the publisher says

From the Owl24 repository's README, as published. We do not edit it. Read it on GitHub

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. getrcareport 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 claimerror succeeds on an item that's never been claimed before — not when it's later resolved, and with no monthly cap. If you releaseerror 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. resolveerror itself never adds a charge — use it once you actually have a fix, and use releaseerror (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

claude mcp add owl24 -e OWL24_API_KEY=your_api_key -- npx -y owl24-mcp

Cursor

Add to your MCP settings (Cursor Settings → MCP):

{
  "mcpServers": {
    "owl24": {
      "command": "npx",
      "args": ["-y", "owl24-mcp"],
      "env": {
        "OWL24_API_KEY": "your_api_key"
      }
    }
  }
}

Any other MCP client: the same command/args/env shape works — npx -y owl24-mcp over stdio, with OWL24APIKEY 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:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Owl24: common questions

Is Owl24 MCP server safe?
Mostly: it is graded B (83/100). Read the Owl24 safety report
How do I install Owl24?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Owl24 need an API key?
Yes. The registry entry asks for OWL24_API_KEY.
Is Owl24 maintained?
The last commit was 32 days ago (2026-10-03). The latest release is v0.2.2.
What can I use instead of Owl24?
Servers from other publishers that do the same job: Serena MCP: the IDE for your agent MCP server, Figma Context MCP server and SuperCompress MCP server.
How does Owl24 compare with other AI and agents MCP servers?
safety score 83/100 (higher than 68% of 4,460 AI and agents servers); tools 10 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Owl24

Same job from other publishers: the closest match first, then the best rated.

  • Serena MCP: the IDE for your agent
    A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
    C
  • Figma Context
    Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
    B
  • SuperCompress
    Compress coding-agent context ~64%. Hosted Neural Keep MCP for Cursor/Claude/Codex.
    B
  • Orcareplay
    Read, replay and fork recorded coding-agent runs.
    A
  • three.ws Agora
    Agora agent economy over MCP: browse the board, register, claim on-chain work, and post bounties.
    B