agent-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPO_URLS | Yes | JSON array of GitHub repository URLs |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_agent_docsA | Read agent documentation and coding guidelines from configured repositories. Use this when you need context about how to work with a codebase, understand coding patterns, architecture decisions, or get implementation guidelines. The documentation provides best practices, conventions, and important context for making code changes. |
| search_agent_docsA | Search through agent documentation for specific information about coding patterns, architecture, APIs, or implementation details. Use this when you need to find specific guidance before implementing a feature or fixing a bug. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Agent Documentation: https://github.com/octocat/Hello-World | Agent documentation and coding guidelines from https://github.com/octocat/Hello-World |
| Agent Documentation: https://github.com/octocat/Hello-World2 | Agent documentation and coding guidelines from https://github.com/octocat/Hello-World2 |
TDQS
Scored across 2 tools
read_agent_docs and search_agent_docs are clearly differentiated by mode: one retrieves full documentation/context, the other finds specific guidance. There is some conceptual overlap since both access the same docs, but descriptions make the boundary clear.
Both tools follow the same verb_noun pattern: read_agent_docs and search_agent_docs. The naming is consistent, predictable, and clearly indicates what each tool does.
With only two tools, the server feels minimal, but the scope is narrowly focused on documentation access. This falls into the borderline range where 1-2 tools feels thin, though it is not unreasonable for a docs-only server.
Read and search cover the main documentation-retrieval workflows with no obvious dead ends. A list/discovery tool could be a minor enhancement, but it is not strictly necessary since search can locate relevant docs.