A
licenseNot graded
qualityB
maintenanceEnables AI agents to query and manage a document knowledge base via MCP, with RAG-powered search and grounded answers with citations.
MIT
agentdocs-mcp
by hoornet
Related Servers
Alternatives to agentdocs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, search, and write to a public wiki knowledge base via MCP.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents and users to search a unified organizational knowledge warehouse, create and iterate on documents, manage folders and reviews, and curate shareable knowledge packs through any compatible MCP client.-
- AlicenseAqualityCmaintenanceEnables MCP clients to search, browse, read, and manage IMA knowledge base content, including notes, web imports, and file uploads, using the official IMA OpenAPI.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to maintain a persistent Markdown knowledge base by ingesting sources, searching and reading notes, and creating or updating wiki pages with optimistic locking.6AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with a persistent, searchable knowledge library via MCP tools, allowing them to create books, manage pages, perform semantic search, and retrieve usage guides.5MIT
TDQS
A4.1/5.0
Scored across 19 tools
Disambiguation4/5
Most tools target a distinct resource and action, and page CRUD versus comment CRUD versus search are clearly separated. Some ambiguity exists between create_page, bulk_create_pages, and import_markdown, and between search_docs and semantic_search, but the descriptions are detailed enough to guide correct selection.
Naming Consistency4/5
The dominant pattern is verb_noun (create_page, list_pages, delete_comment, upload_image), which is consistent and predictable. Minor deviations like whoami, semantic_search, and append_to_page break the pattern slightly but do not cause real confusion.
Tool Count3/5
At 19 tools, the server is in the heavy 16-25 band and feels more sprawling than a focused docs API needs to be. The count is defensible given the wide feature set, but page creation is split across three tools and search across two, making the surface feel larger than necessary.
Completeness4/5
The server covers the core documentation lifecycle well: page CRUD plus append, bulk creation and import, comment threads, search, sharing, and image upload. Minor gaps exist—notably no version restore tool despite versioning being mentioned, and no workspace/space management beyond listing—but these are workaroundable gaps rather than blocking dead ends.
Maintenance
ActivityActive
ResponsivenessNo issues