maester-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAESTER_MCP_AUTH_PROFILE | No | The authentication profile to use. Set to 'none' to disable auth, or 'synthetic' to use synthetic local demo tokens. |
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 | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Return the local caller and authorisation context. |
| list_runsA | List recent Maester runs from the sanitised DuckDB dataset. |
| get_run_summaryA | Return run summary counts only. No raw evidence, source path, source hash, result_detail or error_record. |
| get_failed_testsA | Return failed/error test summaries only. Not raw evidence; does not return result_detail or error_record. |
| get_test_historyA | Show summary history for a test/control. Not raw evidence; does not return result_detail or error_record. |
| compare_runsA | Compare summary result changes between two runs. Not raw evidence; no result_detail or error_record. |
| get_result_detailA | Auditor-only raw evidence. Use only when result_detail, error_record or script_block_file is requested. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema_resource | Describe the published Maester analytics schema and MCP contract. |
| controls_resource | Return the Maester test/control catalogue. |
| latest_run_resource | Return a Markdown summary of the latest run. |
| security_model_resource | Return the reference permission model and trust boundaries. |
TDQS
Scored across 7 tools
Each tool targets a distinct aspect of the Maester run data: identity, run listing, run summaries, failed tests, test history, run comparison, and raw detail. No overlap in purpose or ambiguity in selecting the appropriate tool.
All tools use snake_case with a consistent verb_noun pattern (e.g., list_runs, get_run_summary, compare_runs), with whoami as a minor but acceptable deviation. The naming is predictable and easy to infer.
With 7 tools, the server is well-scoped for a read-only analysis tool covering identity, runs, summaries, failures, history, comparison, and details. Each tool earns its place without excess.
The server lacks a tool to enumerate all tests or retrieve complete test results beyond failures, leaving a significant gap in understanding overall test outcomes. Compare_runs provides summary changes but not per-test detail, so agents cannot fully assess test coverage.