ProjectBrain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| projectbrain_import_projectC | Import CodeGraph facts from a local repository into the local ProjectBrain store. Runs only on local files and does not upload source code. |
| projectbrain_list_projectsA | List projects imported into the local ProjectBrain store. |
| projectbrain_inspect_policyC | Inspect the local output policy loaded for an imported project. |
| projectbrain_add_experience_claimB | Add a local human experience claim to an imported project. Writes only to local ProjectBrain storage and does not read source bodies. |
| projectbrain_list_experience_claimsB | List local experience claims for an imported project. Archived claims are hidden by default. |
| projectbrain_review_experience_claimC | Update local review metadata for an experience claim. |
| projectbrain_archive_experience_claimC | Archive a local experience claim while keeping it in ProjectBrain storage. |
| projectbrain_context_packC | Build a task-scoped Context Pack from local ProjectBrain facts. |
| projectbrain_impact_analysisC | Analyze likely local project impact for changed files or symbols. |
| projectbrain_review_git_diffA | Analyze impact for local Git changes in an imported project. Reads changed file names from local git only; does not read or upload source bodies. |
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 10 tools
Each tool has a clearly distinct purpose, from importing projects and managing experience claims to analyzing impacts and building context packs. The two analysis tools differ by scope: impact_analysis for changed files/symbols and review_git_diff for git changes.
All tools use the 'projectbrain_' prefix followed by a consistent verb_noun pattern (e.g., add_experience_claim, list_projects, inspect_policy). The naming is predictable and clear across the entire set.
With 10 tools, the server is well-scoped for managing local project knowledge. Each tool serves a specific purpose without unnecessary redundancy, covering import, CRUD for claims, analysis, and context building.
The tool surface covers core workflows but has minor gaps: there is no tool to update claim content (only review metadata) and no unarchive functionality. Retrieving a single claim by ID is also missing, though listing works.