code-failures-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRAIN_PATH | Yes | Path to the directory containing code_failures knowledge base |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_past_bugsA | Search your code_failures knowledge base for bugs you've already solved. Query with error messages, symptoms, library names, or keywords. Currently indexing 8 documents. USE THIS TOOL BEFORE debugging any integration issue — your past self may have already spent hours finding the fix. |
| search_referencesA | Search your code_failures knowledge base for canonical working patterns, version guides, and integration references. USE THIS for questions like 'what's the correct CopilotKit + AG-UI setup?' or 'which versions are compatible?' |
| file_bugA | Save a newly discovered bug to the knowledge base. Call this AFTER solving a hard bug to capture the knowledge for future sessions. The file is written to code_failures/bugs/ and auto-indexed. IMPORTANT: Show the user the generated content and get confirmation before calling. |
| file_referenceA | Save a reference document (canonical pattern, version guide, architecture notes) to the knowledge base. Use this for working integration patterns, version compatibility matrices, and architectural decisions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: search_past_bugs targets bug records, search_references targets reference documents, and the two file tools similarly split between bugs and references. The descriptions explicitly define the boundary, so an agent should not confuse them.
All tools follow a verb_noun snake_case pattern with 'search' and 'file' as verbs. Minor inconsistency exists between 'past_bugs' (with modifier) and 'bug'/'reference' without modifiers, but the pattern is predictable.
Four tools is well-scoped for a knowledge base MCP: two search operations and two save operations covering the two content types. Each tool earns its place without redundancy or bloat.
The tool surface covers the core lifecycle: saving and searching both bugs and references. Missing update/delete operations are minor gaps that agents can work around by filing new entries, and the domain is simple enough that this does not cause failures.