dingtalk-wiki-mcp
Related Servers
Alternatives to dingtalk-wiki-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI assistants to perform CRUD operations, search, batch operations, and commenting on iSpace Wiki documents.32MIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Yuque (语雀) platform through MCP protocol, supporting knowledge base management, document operations, search, and team collaboration features.10MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to directly read, write, and manage Feishu documents, spreadsheets, and multi-dimensional tables. It supports automated documentation tasks and rich text management, including Mermaid diagrams and image uploads.1816 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, search, and write to a public wiki knowledge base via MCP.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients to read and write Yuque documents through MCP, providing tools for managing user info, knowledge bases, and documents with dual authentication modes (official API or cookie).-
- FlicenseNot gradedqualityCmaintenanceEnables users to read, create, and edit Feishu Docx/Wiki pages and browse knowledge spaces through user-authorized Feishu credentials.-
TDQS
Scored across 11 tools
Most tools have distinct purposes targeting different resources (wiki docs, departments, users, nodes, workspaces). However, get_wiki_node and get_wiki_workspace could potentially be confused with list_wiki_nodes and list_wiki_workspaces, as the naming suggests similar scopes but different actions (get vs. list). The descriptions clarify the difference, but the overlap in naming might cause initial ambiguity.
The naming follows a consistent verb_noun pattern with snake_case throughout, such as create_wiki_doc, list_departments, and get_user_info. There are minor deviations like set_operator and show_config, which use different verbs but maintain the same structure, keeping the overall pattern readable and predictable.
With 11 tools, the count is well-scoped for a DingTalk wiki MCP server, covering user management, department listing, wiki operations (create, list, get, search), and configuration. Each tool appears to serve a specific purpose without redundancy, fitting the domain appropriately.
The tool set provides good coverage for wiki operations (create, list, get, search) and user/department management, with configuration tools like set_operator and show_config. Minor gaps exist, such as no update or delete operations for wiki documents, which could limit full lifecycle management, but agents can likely work around this for basic workflows.