pollux-mcp
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_instructionsA | Load the project's mandatory AI workflow rules (AI_INSTRUCTIONS.md). Read-only; call at session start. |
| get_summaryA | Read the distilled project memory (summary.md). Small memories return the full file; when the summary exceeds the MCP
size budget (where client-side truncation would silently hide older
entries), a bounded digest is returned instead with pointers to
|
| get_project_mapA | Read the structural layout (PROJECT_MAP.md). Returns 'No project map found.' if not initialized. Read-only. |
| get_planA | Read plan.md — the team's intent (ideas, active plans, next steps). Returns 'No plan found.' if not initialized. Read-only. |
| precheck_fileA | Check a file's memory before modifying it: open issues, failed and partial attempts, stale decisions, churn. Read-only. |
| get_issueA | Read one issue's full history (token-efficient vs the whole summary). Read-only. |
| search_eventsA | Search the event log, most relevant first (open issues, unresolved failures, recency, and file-path hits rank higher). Empty result returns a friendly message, not an error. Read-only. |
| get_scoreA | Failure-prevention score with the formula disclosed. Read-only; computed from events.jsonl on each call. |
| get_contextA | Token-budgeted context block biased toward failures and decisions. Read-only. |
| get_global_gotchasA | Read cross-project gotchas from the shared global store. Read-only. Auto-promotion into this store stays OFF by default in pollux (conservative governance); entries come from explicit curation. |
| log_issueA | Open a new issue and mark it active. Call BEFORE writing fix code. |
| record_attemptA | Record a fix attempt IMMEDIATELY after it fails, partially works, or works. Each distinct approach is its own call — never batch them. |
| record_fixA | Record the confirmed fix and close the issue. Only call with evidence (test passed, error gone, or user confirmed). |
| add_decisionB | Record an architectural/product decision with its rationale. |
| add_noteB | Record a gotcha, setup detail, or durable context. |
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 15 tools
Most tools have clearly distinct purposes, especially the write operations for issue lifecycle, attempts, fixes, decisions, and notes. However, get_summary, get_context, and search_events all surface overlapping project-memory information, and record_attempt's 'works' case creates some ambiguity with record_fix.
Tool names consistently follow a verb_noun pattern in lowercase snake_case: get_* for reads, and log_/record_/add_ for writes. The pattern is easy to predict and there are no mixed naming conventions or vague generic verbs.
At 15 tools, the server sits at the upper edge of a reasonable scope. Each tool corresponds to a meaningful memory or issue action, but the number of read-only context retrieval tools is slightly high and some could potentially be consolidated.
The core failure-prevention loop is well covered: precheck, log issue, record attempt, record fix, plus decision and note persistence. However, there is no write/update path for project map or plan files, and global gotchas are read-only, leaving minor lifecycle gaps.