Marten Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARTEN_MCP_CACHE_DIR | No | Directory for caching documentation | |
| MARTEN_MCP_SQLITE_PATH | No | Path to SQLite database | |
| MARTEN_MCP_STORAGE_MODE | No | Storage mode (e.g., auto) |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Start here: global docs search. Once a relevant page is found, prefer local navigation over another global search. |
| search_within_pageA | Narrow within a known page after global search. Prefer this over another global search. |
| list_headingsC | Inspect sections within a known page before reading a chunk. |
| read_sectionA | Read one chunk with pagination. Prefer neighbors.before/after for the next local read before running another global search. |
| read_contextA | Expand nearby refs around one chunk when immediate neighbor refs are not enough. |
| list_pagesC | Discovery only when search does not identify a relevant page. |
| get_statusB | Get cache and index status. |
| refresh_docsC | Refresh source docs and rebuild the index. |
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 8 tools
Each tool has a distinct purpose that is clearly described. Tools like search_docs, search_within_page, and read_section guide the agent through a clear search-to-read workflow without ambiguity.
All tool names follow a consistent verb_noun pattern: list_headings, search_docs, search_within_page, read_section, read_context, list_pages, get_status, refresh_docs. The naming is predictable and uniform.
With 8 tools, the count is well-scoped for a documentation server. Each tool supports a specific step in the exploration process, from search to reading to cache management.
The tool surface covers the full workflow: global search, local search, reading with pagination, context expansion, page listing, and cache status/refresh. A minor gap is the lack of a tool to directly fetch a page by ID or URL, but the workflow is otherwise complete.