Local Evidence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| root | Yes | Absolute path to the evidence root directory | |
| policy | Yes | Absolute path to the local policy.json file |
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 |
|---|---|
| evidence_statusA | Show the configured evidence boundary, retrieval mode, and write policy. |
| evidence_searchB | Search allowlisted local notes with optional local embeddings and deterministic lexical fallback. |
| evidence_readA | Read one allowlisted UTF-8 note with potential credentials and raw challenge flags redacted. |
| evidence_create_noteB | Create a new evidence note in one configured directory; never overwrite. |
| evidence_append_lessonC | Append one evidence-backed lesson to the configured ledger. |
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 5 tools
Each tool targets a clearly distinct operation: status (introspection), search (query), read (fetch single note), create_note (write), and append_lesson (ledger write). There is no meaningful overlap between search/read or create/append, and the descriptions make the boundaries explicit.
All tools share the evidence_ prefix followed by a clear snake_case verb or noun (status, search, read, create_note, append_lesson). The pattern is predictable and readable throughout.
Five tools is well-scoped for a local evidence/notes server, covering introspection, retrieval, and writing without redundancy. Each tool earns its place.
The surface covers the core lifecycle: status, search, read, create, and append. Update/delete are absent, but the 'never overwrite' policy and append-only ledger suggest this is intentional immutability rather than a gap.