Review MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRACE_ID | No | Trace ID used to tune server logging. | |
| MCP_LOG_LEVEL | No | Log level for stderr pino JSON logs. One of: debug, info, warn, error. | |
| MCP_LOG_FORMAT | No | Set to "human" to make server logs human-readable. | |
| REVIEW_MCP_DB_PATH | No | Path to the SQLite database used by the Review MCP server. Parent directories are created automatically. | ./review-mcp.db |
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": false
} |
| prompts | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Save a durable review about geometry: a semantic feature (give it a name, e.g. 'mounting holes') or a plain note (no name). Re-remembering a named feature REPLACES it (use this to correct the AI). Re-remembering the same entities without a name APPENDS facts. The more you save, the more the system understands the part across sessions. |
| recallA | Retrieve saved reviews for a STEP file, optionally filtered by an entity, free-text search, or tags. Pass the current ArtifactRef from Geometry inspect; its revision is used to mark each returned record stale or current. Each record returns one artifact reference, its entity IDs and the ID scheme; use these together when handing an annotation to another tool. An entity filter matches only reviews written against the supplied revision, because a face ID denotes different geometry in a different revision; text and tag filters are not scoped that way. Use early in a conversation to restore persistent context about a part. Uses the supplied artifact revision to mark saved records stale; it does not open the artifact or require shared filesystem access. |
| forgetB | Delete a saved record. Pass the feature name to remove a named feature, an entity id to remove the anonymous notes attached to that entity, or a subject to remove a decision. Idempotent. Use only when the user explicitly asks to remove it. |
| remember_decisionA | Save the disposition reached about an artifact revision, with the basis it rests on: a list of requirement-checks, each saying where its requirement came from and what happened when it was checked. Re-remembering the same subject on the same artifact revision REPLACES that decision, which is how a decision is revised as the engineer answers questions or disagrees with a line. A different subject starts a separate decision, because one part can carry several at once. Record each engineer verdict when they have given one: a requirement the engineer accepted is a different thing from one that was proposed. Store each requirement as stated and each piece of evidence as it was reported. This server never opens or measures the artifact, so recall returns what was concluded, not a measurement — Geometry remains the authority for numbers. |
| recall_decisionsA | Retrieve decisions saved for an artifact, newest first, each marked stale when it was made against a different revision than the one supplied. Pass the current ArtifactRef from Geometry inspect. Filter by subject text, status, or an entity that appears in the basis. An entity filter matches only decisions made against the supplied revision, because a face ID is scoped to the revision that produced it: a decision about face:3 in an older revision is not a decision about face:3 now. Use this when a revision reappears, to recover what was already concluded instead of reaching it again. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_part | Orient to a STEP part/assembly: structure, size, key features (largest faces, holes, thin regions) and a readable engineering summary. Optionally persist observations. |
| resume_part_context | Restore persistent design intent, decisions and unresolved findings for a part from the knowledge base, check their currency against the current file, then continue the requested task. |
| check_thickness | Locate thin or uneven regions and compare observed wall thickness against process-specific material guidance or an explicit requirement. |
| check_moldability | Screen injection-molding feasibility across wall thickness, draft, release strategy and potential molding defects, then give a scoped verdict. |
| draft_audit | Review draft against a mold pull direction and distinguish insufficient draft from actual release obstructions. |
| measure_clearance | Resolve named feature sets, measure nominal gaps, and assess clearance or interference within the available evidence. |
| compare_iterations | Compare STEP revisions, prioritize changes by functional impact, and preserve revision-specific engineering context. |
| design_review | Conduct an outside-in engineering review combining geometry, persistent intent, manufacturing guidance and actionable findings. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The set is organized as two parallel pairs: recall/remember operate on reviews (features and notes), while recall_decisions/remember_decision operate on decisions with requirement-checks as a basis. Descriptions make the boundary explicit, though the near-identical verb stems mean an agent skimming names could still pick recall when it wants recall_decisions. forget is the only tool spanning both domains, but its description clarifies how to target features, entity notes, or decision subjects.
Names are all lowercase snake_case with verb-first construction, and the pattern is readable: base verbs (recall, remember, forget) for reviews, and the same verbs plus a _decision(s) suffix for decisions. Minor deviation: singular remember_decision paired with plural recall_decisions breaks the symmetry, and forget has no _decision counterpart despite handling decisions.
Five tools is tightly scoped to a persistent-memory server: two write paths, two read paths, and one delete. Each tool earns its place and there is no redundancy. Nothing feels missing or bloated for the stated purpose.
Full lifecycle is covered for both domains — create (remember, remember_decision), read (recall, recall_decisions), delete (forget) — with 'update' handled through documented replace-on-rewrite semantics, which is a valid design. Minor gaps: there is no way to enumerate or export all saved reviews/decisions without supplying an ArtifactRef, and no cross-artifact or cross-revision listing operation.