mcp-sphinx-docs
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_sphinx_fileA | Convert a single Sphinx RST file to LLM-optimized Markdown |
| convert_sphinx_directoryB | Convert an entire Sphinx documentation directory to LLM-optimized Markdown |
| analyze_sphinx_structureB | Analyze the structure of a Sphinx documentation project |
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 scope: single file conversion, directory conversion, and structural analysis. There is no overlap or ambiguity in their purposes.
All tools follow a consistent verb_sphinx_noun pattern (convert/analyze + sphinx + file/directory/structure), making the naming predictable and clear.
Three tools is a well-scoped set for a Sphinx documentation conversion server, covering the essential operations without unnecessary bloat.
The tool set covers the full conversion workflow (single file and whole directory) plus structural analysis, leaving no obvious dead ends for the stated purpose.