DevDocs MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_docsC | List all available documentation sets on DevDocs.io. Returns name, slug, version, and other metadata for each documentation. |
| search_docA | Search within a specific documentation set for entries matching the query. Returns matching entries with their paths and types. |
| get_doc_contentB | Fetch the full HTML content for a specific documentation entry. Use the path from search results. |
| search_all_docsB | Search across multiple documentation sets. Optionally filter by specific documentation slugs. |
| get_doc_indexB | Get the complete index of entries for a specific documentation set. Useful for browsing available topics. |
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 has a clearly distinct purpose with no overlap: list_docs enumerates available documentation sets, get_doc_index retrieves the index of a specific set, search_doc searches within a set, search_all_docs searches across multiple sets, and get_doc_content fetches full content for an entry. The descriptions explicitly differentiate their scopes and use cases.
All tool names follow a consistent verb_noun pattern using snake_case: list_docs, get_doc_index, search_doc, search_all_docs, get_doc_content. The verbs (list, get, search) are appropriately matched to their actions, and the nouns (docs, doc_index, doc, all_docs, doc_content) clearly indicate the target resources.
With 5 tools, the server is well-scoped for its purpose of accessing DevDocs.io documentation. Each tool serves a specific, non-redundant function in the workflow, from discovery to content retrieval, making the count efficient and appropriate for the domain.
The tool set provides complete coverage for the documentation access domain: list_docs for discovery, get_doc_index for browsing, search_doc and search_all_docs for finding entries, and get_doc_content for reading content. There are no obvious gaps, as it supports the full lifecycle from listing sets to fetching specific entry content.