mcp-docs-helper
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-mcp-docsB | Search MCP documentation with context-aware results for building servers |
| get-implementation-templateC | Get code templates for common MCP patterns |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build-server | Start building a new MCP server with guided assistance |
| debug-server | Get help debugging an MCP server issue |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| complete-mcp-docs | Full MCP protocol specification and TypeScript SDK documentation - optimized for building MCP servers |
| quick-start | Essential information to start building MCP servers immediately |
| tools-reference | Complete guide to implementing MCP tools |
| resources-reference | Complete guide to implementing MCP resources |
| prompts-reference | Complete guide to implementing MCP prompts |
| transport-reference | Guide to stdio, HTTP, and SSE transports |
| examples-reference | Working examples of MCP server implementations |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one searches documentation, the other retrieves code templates. There is no overlap or ambiguity.
Both tools follow the consistent verb_noun pattern with underscores, making naming predictable and clear.
With only two tools, the server feels minimal for a documentation helper. While the tools are useful, the scope is narrow and may require additional tools for comprehensive coverage.
The server covers search and template retrieval but lacks other expected documentation features such as browsing categories, listing versions, or retrieving full guides. This leaves notable gaps.