loopgrid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOOPGRID_BASE_URL | No | Base URL of the LoopGrid service. Defaults to http://127.0.0.1:8000. | http://127.0.0.1:8000 |
| LOOPGRID_WORKSPACE | No | LoopGrid workspace name. Defaults to 'default'. | default |
| LOOPGRID_SERVICE_KEY | No | Scoped service key for authenticated LoopGrid deployments. Not required when authentication is disabled. | |
| LOOPGRID_EVIDENCE_DIR | No | Directory where evidence ZIP files are downloaded. Defaults to ./loopgrid-evidence. | ./loopgrid-evidence |
| LOOPGRID_MCP_REVIEWER_ID | No | Reviewer identity used by the review tool. Required when LOOPGRID_MCP_ENABLE_REVIEW_TOOL is set to 'true'. | |
| LOOPGRID_MCP_ENABLE_REVIEW_TOOL | No | Set to 'true' to enable the loopgrid.record_review tool (disabled by default). | false |
| LOOPGRID_MCP_ALLOW_PAYLOAD_EXPORT | No | Set to 'true' to allow raw FULL-mode disclosure payloads in evidence export. Defaults to false. | false |
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 |
|---|---|
| loopgrid.record_decisionA | Capture a consequential AI/agent decision in LoopGrid. Optionally record model output and evaluate an existing LoopGrid policy. This records evidence only and does not execute the proposed action. |
| loopgrid.record_reviewA | Record a human approve/reject review in LoopGrid. Disabled by default. The operator must explicitly enable it and configure reviewer identity; the MCP host should require human confirmation. |
| loopgrid.record_actionC | Record evidence that an external tool/action executed. This does NOT call Stripe, Salesforce, ServiceNow, or any other business system; it only records execution evidence supplied by the integration. |
| loopgrid.record_outcomeA | Record an observed downstream outcome for a decision after execution evidence exists. The integration is responsible for obtaining the outcome from the real downstream system. |
| loopgrid.get_evidenceA | Download a portable LoopGrid evidence ZIP for a decision to the configured local evidence directory. Raw disclosure payloads are excluded by default. |
| loopgrid.verify_evidenceB | Ask the connected LoopGrid service to verify the decision's signed workspace chain. For independent offline verification of an exported ZIP, use the standalone LoopGrid verifier. |
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 6 tools
Each tool targets a distinct stage in the evidence lifecycle: decision, review, action, outcome, retrieval, and verification. The descriptions clearly separate recording evidence from executing actions, so there is no real ambiguity between tools.
All tool names follow a consistent snake_case verb_noun pattern with a uniform loopgrid. prefix. The record_* tools form a clear family, while get_evidence and verify_evidence follow the same predictable convention.
Six tools is well-scoped for a focused governance/evidence server. Each tool earns its place and covers a necessary function without redundancy or bloat.
The tool set covers the full evidentiary workflow: capture decisions, record reviews, log actions, record outcomes, retrieve portable evidence, and verify integrity. There are no obvious dead ends for the stated purpose.