sharedoc-mcp
Related Servers
Alternatives to sharedoc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for structured document management of markdown and YAML files, with RBAC, git-based approval workflows, and semantic search, enabling agents to read, edit, and maintain documents under governance.MIT
- AlicenseNot gradedqualityBmaintenanceA stdio MCP server providing everyday tools and Markdown skills for the Sesha agent, enabling notes, web research, coding, docs, scheduling, and safety/governance.GPL 3.0
- AlicenseAqualityBmaintenanceAn MCP server that lets AI publish markdown documents to a clean, themed web UI. One tool call creates a shareable doc.84MIT
- AlicenseAqualityNot gradedmaintenanceAn MCP server that enables AI agents to instantly convert Markdown into beautiful, ready-to-deliver Word, PDF, HTML with sidebars, and Slideshow documents, bridging the "last mile" of AI content generation.728 npm1-

chat-shareofficial
FlicenseNot gradedqualityBmaintenanceMCP server for publishing AI agent conversations as public links with optional password protection and expiration, also providing tools to revoke shared chats and retrieve link metadata.-- AlicenseNot gradedqualityAmaintenanceMCP server for Nyxdoc, a document system where humans and external agents collaborate on documents with version history, agent to-dos, and workspace permissions.MIT
TDQS
Scored across 9 tools
Each tool targets a distinct operation on shared docs: create, append, replace content, extend expiry, reset password, update title, revoke, delete, and search. Even the two update-titled tools are clearly separated by attribute (content vs title), and revoke vs delete are explicitly differentiated in descriptions.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_shared_doc, update_shared_doc_title, search_shared_docs). Verbs are specific and the noun remains 'shared_doc(s)' throughout, making the pattern predictable and easy to navigate.
With 9 tools, the server is well-scoped for managing shared documents. Each tool covers a necessary operation without redundancy, and the count fits comfortably within the ideal 3-15 range.
The surface covers create, read via search, full update of content/title/password/expiry, revoke, and delete, which is nearly complete for a document lifecycle. A minor gap is the lack of a direct 'get' tool to fetch full content of a single doc by ID, but search with content_query can partially work around this.