evidence-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVIDENCE_MCP_TRANSPORT | No | Transport mode: stdio, sse | stdio |
| EVIDENCE_MCP_EVIDENCE_DEV_URL | No | Evidence dev server URL | http://localhost:3000 |
| EVIDENCE_MCP_EVIDENCE_PROJECT_PATH | Yes | Path to Evidence project |
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_metadataA | Returns database schema from Evidence's DuckDB connection. Returns a JSON object with tables and their columns, including data types. Use this to understand what data is available for queries. Returns: Dictionary with 'tables' array, each containing 'name' and 'columns' |
| read_docsB | Retrieves Evidence documentation using hierarchical lookup. Categories:
Returns: Dictionary with 'title', 'content', and 'related_docs' for further exploration |
| edit_pageC | Proposes changes to the current Evidence markdown page. Validates the proposed content for common Evidence syntax issues and returns the content with any warnings detected. Returns: Dictionary with 'success', 'description', 'content', and 'warnings' list |
| debug_codeC | Analyzes validation errors and suggests fixes. Examines the provided errors and page content to identify issues and generate actionable fix suggestions. Returns: Dictionary with 'analysis', 'suggestions' list, and optionally 'fixed_content' |
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 4 tools
Tools are mostly distinct: debug_code analyzes errors, edit_page modifies content, get_metadata queries schema, read_docs fetches documentation. Minor overlap between debug_code and edit_page as both involve page content, but their purposes are clear.
All tool names follow a consistent verb_noun pattern in lowercase with underscores: debug_code, edit_page, get_metadata, read_docs. No deviation.
Four tools is well-scoped for an Evidence MCP server, covering core needs like debugging, editing, schema discovery, and documentation. Not too few or too many.
Significant gaps: missing tools for creating, listing, or deleting pages, and no tool to run queries or fetch actual data from the database. The surface covers only partial workflows, likely causing agent failures in common tasks.