codebugs MCP server
Commit 30. Okt. 2026Verfolgt Code-Defekte, Anforderungen und Releases über ein deduplizierendes, SQLite-basiertes System für KI-Assistenten.
Auch bekannt als faxik/codebugs
- Stars
- 1
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- —
- Letzter Commit
- 30. Okt. 2026
- Lizenz
- MIT
Was ist codebugs MCP?
codebugs ist ein MCP server. Verfolgt Code-Defekte, Anforderungen und Releases über ein deduplizierendes, SQLite-basiertes System für KI-Assistenten.
Zusammenfassung generiert aus dem README des Projekts
Über codebugs MCP server
Das Management von Code-Defekten, Anforderungen und Releases wird für KI-Assistenten durch dieses SQLite-basierte System deutlich organisierter. Im Gegensatz zu Standard-Trackern, die für jeden Report einen neuen Eintrag erstellen, behandelt dieses Tool wiederholte Sichtungen desselben Problems als Beobachtungen eines einzelnen Defekts. Dies verhindert redundantes Rauschen, indem entweder die Anzahl der Vorkommen erhöht oder die Schwere des Fehlers hochgestuft wird, wenn ein neuer Report auf ein kritischeres Problem hinweist. Zudem werden Regressionen verfolgt, indem bestehende Cards wieder geöffnet werden, anstatt neue zu erstellen – so bleibt die gesamte Historie eines Bugs in einer einzigen Zeile erhalten.
Entwickler können das Tool über ein CLI oder als MCP server für Clients wie Claude Code nutzen. Das System enthält spezialisierte Features wie anchor_resolve, um Code zu verfolgen, der durch Edits verschoben wurde, und claims_claim, um zu verhindern, dass mehrere Agenten gleichzeitig an derselben Aufgabe arbeiten. Es ist für den lokalen Einsatz konzipiert und erfordert eine projektspezifische Initialisierung mit dem init command, um eine findings.db Datei zu erstellen. Nutzer können den Server zudem auf spezifische Module, wie etwa findings, beschränken, um das verfügbare Toolset zu limitieren.
Was du damit machen kannst
- 1Verhindern von doppelten Bug-ReportsEin KI-Agent kann einen Bug mehrfach melden, ohne die Datenbank zu überladen, da das System nachfolgende Reports als Beobachtungen desselben Defekts behandelt.
- 2Verfolgen von Code-Bewegungen nach EditsEin Entwickler kann einen Bug auch dann noch lokalisieren, wenn der umgebende Code refactored oder in andere Zeilennummern verschoben wurde.
- 3Koordinierung mehrerer KI-AgentenDu kannst verhindern, dass zwei verschiedene KI-Assistenten versuchen, denselben Defekt zur gleichen Zeit zu fixen.
- 4Identifizieren von Software-RegressionenWenn ein zuvor behobener Bug erneut auftritt, erfasst das System dies als Regression auf der ursprünglichen Defekt-Card.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
Konfiguration
CODEBUGS_ROOT
| Name | Beschreibung | Typ |
|---|---|---|
| CODEBUGS_ROOT | — |
Automatisierte Checks
Geluften am 15. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarfaxik/codebugs is public and reachablegithub.com/faxik/codebugs ↗Bestanden
- Paket nennt dieses Repository als QuelleNicht geprüft
- Build-Provenienz (Sigstore-Attestierung)Nicht geprüft
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-10-30github.com/faxik/codebugs ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehencodebugs
A code-finding, requirements, and release tracker for AI assistants — one where a finding has an identity. SQLite-backed, exposed via an MCP server and a CLI.
Most trackers treat every report as a new row, so the second agent to notice the same bug files it again, and the queue fills with copies of one defect. codebugs treats a finding as a defect, and each report of it as one observation of that defect:
$ codebugs add -s high -c n_plus_one -f src/api.py -d "Query in loop at line 42" --new-category
Added: CB-1
$ codebugs add -s high -c n_plus_one -f src/api.py -d "Query in loop at line 42"
Bumped: CB-1 (occurrence 2)
$ codebugs update CB-1 --status fixed
Updated: CB-1 (status=fixed, severity=high)
$ codebugs add -s high -c n_plus_one -f src/api.py -d "Query in loop at line 42"
Reopened as regression: CB-1 (occurrence 3)
One card, three observations, and a regression recorded on the row it belongs to. Filing an observation again is normal and useful, not noise.
What makes this different
Deduplication is the point, not a side effect — and the rest of the design falls out of that one decision.
- Filing the same finding twice does not create two cards. The second report bumps the first: its occurrence count goes up, and its severity rises if this sighting was worse than the last. Severity only ever escalates under observation, so a card filed
lowand re-seencriticalstops hiding from a--severity criticalquery. Lowering it back is a deliberateupdate, never an accident of the last report. - A card that was fixed and comes back is a regression, not a duplicate. Re-filing reopens the same card and records the regression on it, so one defect's whole history stays on one row.
- A decision stays decided. Re-filing something already dismissed as
wont_fixornot_a_bugdoes not quietly reopen the argument. It files a new card pointing back at the dismissal, so the recurrence is visible and the original ruling survives. - The place in the code outlives the edit. When a report names a line range, the location is anchored at filing time from git. After the file is edited around it,
anchor_resolvereports where that code went —moved, with the new line numbers — instead of pointing at whatever now occupies the old line. - Parallel agents don't collide.
claims_claimgives one agent a card and refuses the second, naming who holds it and from which repo, so two agents cannot silently fix the same thing. Closing a card releases the claim in the same transaction. - Findings can be related and grouped. Cards link to each other, and a similarity report proposes families of near-duplicate findings as a dry run you inspect before merging anything.
- It tells you when it could not look. A tracker it cannot read, a file it cannot stat, an anchor whose card never named a code span — each of these comes back as undetermined, with the reason, rather than as a confident wrong answer.
codebugs wherewill tell you which tracker a command is actually bound to and which channel decided that, because a binding you cannot see is a binding you cannot debug.
Underneath that, it is durable memory across sessions: findings survive the conversation that produced them, requirements are checked against the code that claims to implement them, blocked work resurfaces when its dependency resolves, and a release knows what is still stranded on a branch.
codebugs is one SQLite database (.codebugs/findings.db). Modules are self-registering, and the running server reports its own tool catalogue — the module table below is the set of them.
Install
codebugs is not published to PyPI. There is nothing under that name in the public index, so
pipx install codebugs and pip install codebugs cannot resolve — they fail before they start.
Install it from a clone instead, by path:
git clone https://github.com/faxik/codebugs.git
pipx install ./codebugs # global install, recommended
pip install ./codebugs works too, into whatever environment is active.
Two consequences of installing by path, both worth knowing before the first surprise:
- The installed copy is a snapshot, not a link. Editing the clone afterwards does not change
what
codebugsruns. Re-runpipx install --force ./codebugsto pick the changes up, or pass--editableat install time if you want the clone itself to be what runs. - The installer resolves dependencies on its own and does not read this repository's
uv.lock. So the versions you end up running are whatever your installer resolved — for a freshpipxinstall, typically the newest release each declared range admits; forpipinto an environment that already has a satisfying version, whatever was already there — and neither is necessarily the combination the test suite ran against. That gap is real and has bitten once already, which is why thenewest-sdkjob in.github/workflows/ci.ymlruns the whole suite against the newest versions the ranges admit. Note what that buys and what it does not: a break on the versions you would install becomes VISIBLE there instead of passing silently on the locked ones — it is not a promise that the newest combination currently works.
Setup
Create the tracker
Run this once per project, in the project root:
codebugs init
This creates .codebugs/findings.db. init is the only command that creates the .codebugs/ directory — every other command discovers an existing one by walking up from the current directory (unless you point it somewhere explicitly, see below), and refuses with an actionable error if there is none. That refusal is deliberate: silently creating an empty database is how findings go missing.
There is one deliberate exception, and it is worth stating precisely because it looks like the rule being broken. The upward walk treats an existing .codebugs/ directory as the opt-in, so if that directory is there but holds no findings.db, the next command creates the database inside it rather than refusing. The common way to end up in that state is an interrupted init — the directory is created before the database — and self-healing on the next command is more useful there than demanding a second init.
A tracker you name explicitly is held to the stricter rule. --repo, --tracker-root and $CODEBUGS_ROOT must resolve to a directory that actually contains findings.db; a .codebugs/ without one is refused, and the message names which channel pointed there. The difference is about evidence: standing inside a directory says something about where you are, while a named path is an assertion that can be mistyped, or exported into a shell days ago and inherited by an unrelated process. That is exactly where a silent empty tracker does the most damage.
Two consequences worth knowing:
-
Run
initat the project root, not in a subdirectory. Discovery binds to the nearest.codebugs/, so a nested tracker hides the project's real one from everything beneath it.initrefuses to do this unless you pass--force. -
Git worktrees share the main repo's tracker. A worktree's
.gitis a file pointing at the main repo, which discovery follows — so findings filed from a worktree land in the project's database, not in a throwaway that dies with the worktree.initrefuses to run inside a worktree for the same reason; run it in the main checkout.Two layouts are the exception: if the main repo is bare or was created with
--separate-git-dir, git records no path back to a main checkout — its owngit worktree listreports the git directory instead. Discovery usually refuses those with an explicit error rather than guessing. There is one case it cannot detect: a--separate-git-dirrepo whose git directory is itself named.gitlooks exactly like a normal checkout, so discovery binds to the directory holding the git dir instead of the real checkout, silently. Nothing local can distinguish the two — git reports that directory as a valid work tree as well — so the remedy is to state the root explicitly (below). Runinitin the main checkout before creating worktrees.
Pointing codebugs at a specific tracker
Discovery is a heuristic, so it has an override:
codebugs --tracker-root /path/to/project query # this invocation only
export CODEBUGS_ROOT=/path/to/project # this shell and anything it spawns
Resolution order, most specific first: a command's own explicit path argument (--repo, where a command has one) → --tracker-root → CODEBUGS_ROOT → walking up from the current directory. A per-command argument outranks a declaration because it names one operation's target, while a declaration is process-wide.
codebugs where # show the current binding and which channel decided it
where is a diagnostic, not a precedence level: it prints the resolved root, the database path, and the channel — the fastest way to check that a command is about to read the tracker you think it is.
One thing is true of every declared root, for every command except init: a root that contains no .codebugs/ is a hard error, never a new tracker. The value may be a stale export inherited from another shell, and silently creating an empty database there is how findings go missing.
init is the exception, and it treats the two channels differently, because they carry different evidence. --tracker-root DIR init creates the tracker in DIR — the flag is typed on the command line being run, so it is an assertion about this invocation, exactly like a path argument. CODEBUGS_ROOT is ignored by init, which creates where you are standing, and warns that later commands will read somewhere else: an environment variable exported days ago and inherited by an unrelated process must never conjure a tracker in a directory you are not in. Whenever the tracker init created is not the one the next command would read, it says so on stderr, since otherwise it would report success for a dead end.
CODEBUGS_ROOT is inherited by every subprocess, so export it only when you mean "this shell works on that project". For one-off use across projects, prefer --tracker-root.
Claude Code (MCP)
Add to ~/.claude.json (global) or .mcp.json (per-project):
{
"mcpServers": {
"codebugs": {
"command": "codebugs-mcp"
}
}
}
The database lives at .codebugs/findings.db, discovered by walking up from the server's working directory — each project gets its own. Run codebugs init in the project first (see above), or every tool call will fail with "no .codebugs/ found".
The server connects lazily, per tool call, so it starts successfully even when no tracker is reachable. At startup it writes a diagnostic to stderr — which MCP clients log — if discovery failed, or if a root was declared rather than discovered; on the ordinary path it says nothing. It never refuses to start: a project directory that appears later must still work.
To pin one server to one tracker instead of deriving it from the working directory:
{
"mcpServers": {
"codebugs": {
"command": "codebugs-mcp",
"args": ["--tracker-root", "/path/to/project"]
}
}
}
Only do this when you want that server bound to a single project — the default cwd-derived behavior is what lets one registration serve many. Add .codebugs/ to your .gitignore.
Running Modules Independently
Use --mode to load only the tools you need:
{
"mcpServers": {
"codebugs": {
"command": "codebugs-mcp",
"args": ["--mode", "findings"]
}
}
}
Any module name from the module table below is a valid mode, and all — the default — loads everything. The CLI takes the same flag: codebugs --mode findings summary.
One asymmetry is worth knowing before you rely on it: usage is a CLI-only mode. It registers a command but no MCP tools, so codebugs --mode usage usage works, while codebugs-mcp --mode usage does not start at all — the server does not accept that value, and refuses it with argument --mode: invalid choice: 'usage' and exit code 2. It is not a server that runs with an empty catalogue; there is no server. The two lists of accepted modes are compared with each other, and with the module table below, by the test suite — so a mode that appears on one surface and not the other turns a test red rather than surprising you here.
Other MCP Clients
Any MCP-compatible client can connect to codebugs-mcp via stdio transport.
The modules
Every name in this table is a valid --mode value.
| Module | Domain | Headline tools |
|---|---|---|
| findings | Bugs, tech-debt, review findings | summary, add, query, categories |
| reqs | Functional requirements (FR-N) | reqs_summary, reqs_add, reqs_verify, reqs_search_similar |
| blockers | "X is blocked by Y" dependency graph | blockers_add, blockers_check |
| sweep | Batch iteration with state machines | codesweep_create, codesweep_next, codesweep_mark |
| bench | Performance benchmark snapshots | codebench_import, codebench_query |
| merge | Parallel-agent merge serialization | codemerge_start, codemerge_claim |
| milestones | Releases, streams, capacity-aware pull | pull_next, milestone_status, milestone_close |
| provenance | Staleness vs git history, commit trailers | staleness_check |
| claims | Which agent holds a finding or requirement | claims_claim, claims_release, claims_who_holds |
| loc | Where in the code a finding is, across edits | anchor_resolve, anchor_recapture |
| similarity | Near-duplicate findings, as a dry run | similarity_check, similarity_report |
| relations | Typed, retractable links between findings | relations_relate, relations_query |
| grouping | Reads the axes the tracker stores but never exposed | grouping_citations, grouping_tags, grouping_filing |
| usage | Tool-call counters (CLI only — no MCP tools) | — |
Modules are self-registering — adding a new one is local to its own file. See docs/superpowers/specs/ for the architecture history.
Not every MCP tool has a CLI verb. The milestones module is where the gap is widest: milestone_create, milestone_update, milestone_add_item, milestone_move_item, milestone_set_status, milestone_defer, milestone_close, triage_dismiss, triage_promote, pull_next and release_item are reachable through MCP only. From a terminal you can inspect a release, but you cannot create one or pull work from it.
Quick tour
Findings — log it, never re-discover it
MCP tools:
| Tool | Purpose |
|---|---|
summary |
Dashboard overview — start here for orientation |
add |
File an observation. Creates, bumps, reopens or refiles — read dedup_action to see which |
batch_add |
File several observations at once |
update |
Change status, severity, notes, tags or metadata (append_note adds, notes replaces) |
query |
Search/filter with pagination and group-by |
get |
Fetch one finding by id, with its full body and occurrence history |
recent |
Findings touched at or after a date — the one call for "what closed since" |
stats |
Cross-tabulated counts (severity x category/file/status) |
categories |
List existing categories — call before add for consistency |
categories_normalize |
Fold twin category spellings together. Dry run by default |
staleness_check lives in the provenance module rather than here, and anchor_resolve in loc; both are listed in the module table. The tools behind the opening section — anchors, similarity, relations and grouping — have their own entry under Identity, location and grouping below.
CLI:
codebugs add -s high -c n_plus_one -f src/api.py -d "Query in loop at line 42" --new-category
codebugs summary
codebugs query --status open --severity critical
codebugs update CB-1 --status fixed --append-note "Fixed in PR #42"
codebugs categories
--new-category is needed the first time a category is used, and only then. A category the tracker has never seen is refused, naming the closest existing spellings, because the common way a category set fragments is a typo — n-plus-one beside n_plus_one — and a fragmented category set is what makes categories stop revealing patterns. Once n_plus_one exists, later findings use it without the flag. Spelling is normalized on the way in, so hyphens, spaces and case do not mint twins.
--append-note adds to a finding's notes; --notes replaces them wholesale. Prefer --append-note when recording investigation history — --notes will discard whatever was there, which is usually not what you want on a finding others have been working.
When a new finding is added, the milestones auto-router automatically attaches it to stream/triage (or stream/security when severity=critical and category starts with security:). The finding and its triage entry land in the same transaction.
Requirements — verify what shipped, surface contradictions
MCP tools:
| Tool | Purpose |
|---|---|
reqs_summary |
Requirements dashboard — start here |
reqs_add |
Add a requirement (FR-001, priority, status, test coverage) |
reqs_update |
Change status, description, priority, test coverage |
reqs_query |
Search/filter by status, priority, section, free text |
reqs_get |
Fetch a single requirement by ID with full body |
reqs_stats |
Cross-tabulated counts (status x priority) |
reqs_verify |
Automated checks: ghost test files, duplicate IDs, status contradictions |
reqs_import |
Import from REQUIREMENTS.md (parses markdown tables) |
reqs_embed / reqs_batch_embed |
Store embedding vectors |
reqs_search_similar |
Semantic search across requirements |
reqs_embedding_stats |
Report on embedding coverage |
CLI:
codebugs reqs-import REQUIREMENTS.md
codebugs reqs-summary
codebugs reqs-verify
codebugs reqs-query --status Implemented --priority Must
codebugs reqs-update FR-090 --status Superseded --notes "Replaced by vault architecture"
codebugs reqs-export REQUIREMENTS.md
Blockers — "X is blocked by Y", with auto-unblock
MCP tools:
| Tool | Purpose |
|---|---|
blockers_add |
Defer an item until another item resolves, a date passes, or a manual signal |
blockers_query |
List blockers filtered by item, dependency, trigger type |
blockers_check |
Find currently-actionable items (all blockers satisfied) |
blockers_resolve |
Cancel or manually resolve a blocker |
Triggers come in three flavors: entity_resolved (waits for another finding/requirement to reach a terminal state), date (unblocks on a specific datetime), and manual (operator signal). When you mark a finding fixed, every blocker that was waiting on it auto-unblocks and surfaces in the next blockers_check.
Milestones — release containers + standing streams + capacity-aware pull
MCP tools:
| Tool | Purpose |
|---|---|
milestone_status |
Rollup for one milestone (counts by status/size, branch-only, blocked, days to target) |
milestone_list |
List milestones, filter by kind / state |
milestone_create |
Create a release or stream |
milestone_update |
Mutate description, target_date, state |
milestone_add_item |
Attach a bug / requirement / external ref to a milestone |
milestone_move_item |
Move an item between milestones |
milestone_set_status |
Open / in_progress / done / dismissed / deferred |
milestone_defer |
Move to stream/maintenance with status='deferred' |
milestone_close |
Refuses if open / branch-only / blocked items remain (force overrides, except for streams) |
milestone_audit_query |
Full state-transition history |
triage_inbox |
Items waiting to be triaged |
triage_dismiss |
Reject a triage item; propagates to underlying entity |
triage_promote |
Move a triage item to a target milestone |
pull_next |
Atomically claim the next eligible item for the calling agent |
release_item |
Free agent capacity (status='done' or 'abandoned') |
wip_status |
Snapshot of agent_capacity per agent |
mark_branch_only |
Flag an item as living on a feature branch only |
mark_integrated |
Mark merged-to-main with commit SHA; clears branch_only |
Four seed milestones are created automatically:
stream/triage— inbox for unsorted findings (default destination)stream/maintenance— deferred / boy-scout workstream/security— urgent fixes (preempts release work)release/1.1— first post-1.0 release
pull_next priority order: stream/security > release/* (earliest target_date first) > stream/triage > stream/maintenance. Within a milestone: priority ASC, then created_at ASC.
Eligibility: item is open, no active blockers (skipped for item_kind='external'), acceptance required for size='large', and a large bug in a release milestone must declare linked_frs whose ids resolve to rows in requirements. Concurrent calls from multiple agents are atomic — claims are serialized via BEGIN IMMEDIATE.
CLI:
codebugs milestone-list
codebugs milestone-status release/1.1
codebugs triage-inbox
codebugs wip-status
codebugs milestone-audit --milestone release/1.1
A typical autonomous-agent loop:
# 1. Agent claims the next eligible item.
item = pull_next(agent_id="agent-A", capacity={"large": 1, "small": 2, "triage": 5})
# 2. (Optional) flag a feature branch.
mark_branch_only(item_ref=item["item_ref"], branch_name="feat/CB-1234")
# 3. After integration, mark it done with the commit SHA.
mark_integrated(item_ref=item["item_ref"], commit="abc123…")
# 4. Free the agent's capacity slot.
release_item(item_ref=item["item_ref"], status="done")
Closing a release runs the close-gate: unfinished, branch-only, and blocker-gated items refuse to let the milestone ship. force=True (with a logged reason) overrides — but stream/* milestones cannot be closed, even with force.
Sweeps — batch iteration with recurrence-aware lifecycles
MCP tools:
| Tool | Purpose |
|---|---|
codesweep_create |
Create a new sweep (optional lifecycle=[...], terminal_states=[...], transitions={...} for state machines) |
codesweep_add |
Add items. Atomic upsert: existing items bump recurrence_count, refresh last_seen, un-archive |
codesweep_next |
Next batch of unprocessed (non-terminal, non-archived) items |
codesweep_mark |
Transition state (legacy processed=True still works) |
codesweep_status |
Progress overview |
codesweep_archive / codesweep_archive_items |
Soft-delete |
codesweep_list_items / codesweep_list |
Inspection |
codebugs sweep-create --name lint-pass --batch-size 5
codebugs sweep-add lint-pass src/*.py --tags critical
codebugs sweep-next lint-pass
codebugs sweep-mark lint-pass src/api.py
codebugs sweep-status lint-pass
With a custom lifecycle (e.g. for retro findings):
codebugs sweep-create --name retro-findings \
--lifecycle DETECTED,CONFIRMED,ESCALATED,RESOLVED,DROPPED \
--terminal-states RESOLVED,DROPPED
codebugs sweep-add retro-findings finding-2026-04-todo-bypassed --tags silent_abandonment
codebugs sweep-mark retro-findings finding-2026-04-todo-bypassed --state CONFIRMED
codebugs sweep-archive-items retro-findings --state RESOLVED --older-than 30d
codebugs MCP Fragen
Wie geht codebugs mit doppelten Bug-Reports um?
Mehrere Meldungen desselben Problems werden als Beobachtungen eines einzigen Defekts behandelt. Dabei wird die Anzahl der Vorkommen erhöht und die Schwere des Fehlers hochgestuft, anstatt neue Einträge zu erstellen.
Wie geht der Tracker mit Code-Änderungen und verschobenen Zeilennummern um?
Er nutzt git-basierte Anker, um den Code auch nach Edits zu verfolgen; das anchor_resolve Tool kann melden, wenn ein Codeblock auf neue Zeilennummern verschoben wurde.
Können mehrere KI-Agenten gleichzeitig an denselben Bugs arbeiten?
Ja, das System verhindert Kollisionen durch einen Claim-Mechanismus, der sicherstellt, dass immer nur ein Agent eine bestimmte Card hält.