agentdocs-mcp
Related Servers
Alternatives to agentdocs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read, search, list, create, and update Markdown wiki articles with tags, knowledge-graph links, backlinks, and version history under a shared permission model. All access is scoped by per-article read/write permissions and requires MFA-authenticated logins.1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to publish markdown as shareable pages with permanent links, update existing pages in place, and read or manage page content, versions, and collections through MCP tools.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query and manage a document knowledge base via MCP, with RAG-powered search and grounded answers with citations.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to read and write Markdown documents, HTML pages, data files, PDFs, screenshots, and videos through a standard remote MCP server with OAuth, per-agent revocable project permissions, version history, and stable artifact links.8 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, search, and write to a public wiki knowledge base via MCP.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search, read, update, and batch-manage persistent documents and workspace knowledge through MCP tools, prompts, and resources.-
TDQS
Scored across 19 tools
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.
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.
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.
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.