Docsy
Server Details
Read versioned developer documentation with original source links using five public MCP tools.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 25.3% over 21 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- getremcp/docsy-plugin
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool targets a distinct action in the documentation retrieval workflow: global search (search), ID resolution (resolve-library-id), library-specific retrieval (query-docs), version listing (list-library-versions), and fetching a specific result or publisher page (fetch). The descriptions explicitly clarify boundaries, such as search returning IDs/URLs versus query-docs retrieving content, so an agent can easily tell them apart.
All names use kebab-case and start with a verb (fetch, list, query, resolve, search), which is mostly consistent. However, fetch and search are bare verbs while the others follow a verb-noun pattern (list-library-versions, query-docs, resolve-library-id), a minor deviation from a strict verb_noun convention.
Five tools is well-scoped for a documentation retrieval server, covering discovery, resolution, retrieval, versioning, and specific fetching without redundancy. Each tool earns its place and the count is neither thin nor bloated.
The surface covers the core read-only lifecycle: search globally, resolve library IDs, query docs, list versions, and fetch specific results. Minor gaps exist, such as no dedicated tool for listing all libraries or retrieving library metadata independently, but agents can work around these via search and query-docs.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
fetch3 fields changed- added
Input schema / properties / libraryIdAdded value: +{ + "maxLength": 500, + "minLength": 3, + "type": "string" +} - added
Input schema / properties / urlAdded value: +{ + "format": "uri", + "type": "string" +} - removed
Input schema / requiredRemoved value: -[ - "id" -]
- Changed
query-docs2 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of documentation chunks to return; omit to use the production default."New value: +"Maximum results to return (snippets or links); omit to use the production default." - added
Input schema / properties / responseAdded value: +{ + "description": "Choose links to search existing publisher/version metadata without loading, parsing, embedding or saving documentation page contents. Defaults to snippets.", + "enum": [ + "snippets", + "links" + ], + "type": "string" +}
1 tool update
- Changed
list-library-versions3 fields changed- added
Input schema / properties / includePrereleaseAdded value: +{ + "type": "boolean" +} - added
Input schema / properties / limitAdded value: +{ + "maximum": 100, + "minimum": 1, + "type": "integer" +} - added
Input schema / properties / offsetAdded value: +{ + "maximum": 100000, + "minimum": 0, + "type": "integer" +}
5 tool updates
- First observed
fetch - First observed
list-library-versions - First observed
query-docs - First observed
resolve-library-id - First observed
search
Related MCP Connectors
Version-true web3 docs, ABIs and human-validated integration recipes over MCP.
Docsy gives AI assistants current, version-specific documentation for libraries, frameworks and SDKs. Resolve library IDs and versions, then search and fetch focused official documentation with original source links using five read-only MCP tools. Hosted Streamable HTTP with OAuth 2.1 sign-in.
Team docs served to AI agents over MCP - search, Markdown reads, version pinning, read audit.
Read-only MCP server over the developer docs for the portfolio's JSON API, MCP, A2A and NLWeb.
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceProvides MCP tools for searching, listing, and retrieving MST developer documentation.24 npmISC- FlicenseNot gradedqualityCmaintenanceExposes NVIDIA Run:ai documentation and API references across multiple versions and docsets (self-hosted, SaaS, multi-tenant, API, legacy) through MCP tools.9 npm-
- FlicenseNot gradedqualityDmaintenanceIndexes public documentation sites into PostgreSQL and exposes retrieval-only MCP tools for listing sources, searching with citations, and fetching documents.5 npm-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search, read, and traverse documentation bundles in Open Knowledge Format via MCP tools.705 npm75MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.