Citepath
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| searchA | Start here: full-text search over the documentation indexed on this machine. Returns ranked passages, each with an id, title, heading path, citation_url, and text (long passages are shortened; read them in full with get_passage). Works with natural-language questions and code identifiers (getUserName, --dry-run, a.b.c). Results come from the current docs version; other_versions lists older versions that also matched, each with a path_prefix to pass back as path_prefix to search that version. Use list_sources to see which sources exist. Read-only. |
| get_passageA | Reads one passage in full by its ID, after search has found it. Use it when a search result was shortened, or when you need the text around a passage: neighbors adds up to 3 passages before and after it from the same page, in document order. Returns { passage, before, after }, each passage with its citation_url. To find passages, use search instead. Read-only; fails if the ID is unknown or its source was removed. |
| list_sourcesA | Lists the configured documentation sources: id, name, type, document and passage counts, and the last sync status. Use the ids to narrow search with source_ids. Sources are added and synced only from the citepath CLI, not through MCP. Read-only. |
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 3 tools
Each tool targets a distinct action: search finds passages, get_passage retrieves a specific passage by ID, and list_sources enumerates available sources. The descriptions explicitly clarify the intended workflow (e.g., 'Start here' for search, 'after search has found it' for get_passage), leaving no overlap.
Two tools follow a clear verb_noun pattern (get_passage, list_sources) in snake_case, but 'search' is a bare verb without a noun. This minor deviation is readable and common, but not fully consistent with the established pattern.
The server's narrow purpose (documentation search and passage retrieval) is served by exactly three well-scoped tools: finding content, drilling into specific passages, and listing sources. Each tool is necessary, and the count sits at the low end of the recommended 3-15 range without feeling thin.
The read-only surface covers the essential workflow: discover sources, search across them, and retrieve full passages with neighborhood context. Source management is intentionally delegated to the CLI, so no obvious gaps exist for the MCP role.