Connections & Capabilities
Connects To
Capabilities
Quickstart
Install
npx -y @smithery/cli install @HenryHaoson/Yuque-MCP-Server --client claudeExposed MCP Tools (13)
get_current_userRetrieves basic information about the currently authenticated Yuque user.
Read-only operation, no side effects.
get_user_docsLists all knowledge base documents accessible to the current user.
Read-only operation, no side effects.
get_user_reposRetrieves a list of knowledge repositories for a specified user.
Read-only operation, no side effects.
get_repo_docsLists all documents within a specific knowledge repository.
Read-only operation, no side effects.
get_docRetrieves the detailed content of a specific Yuque document.
Read-only operation, no side effects.
create_docCreates a new Yuque document in a specified knowledge repository.
Creates new content, but does not modify existing data without explicit instruction.
update_docUpdates an existing Yuque document with new content or settings.
Modifies existing content, potentially overwriting data.
delete_docDeletes a specified document from a Yuque knowledge repository.
Irreversibly removes data.
searchSearches for documents or knowledge repositories within the Yuque platform.
Read-only operation, no side effects.
get_group_statisticsRetrieves aggregated statistics for a team, including member count and document metrics.
Read-only operation, no side effects.
get_group_member_statisticsRetrieves statistics for individual members of a team, such as edit counts and views.
Read-only operation, no side effects.
get_group_book_statisticsRetrieves statistics for team knowledge repositories, including document counts and readership.
Read-only operation, no side effects.
get_group_doc_statisticsRetrieves statistics for team documents, such as word count and views.
Read-only operation, no side effects.
Safety Assessment
The Yuque MCP server offers a mix of read and write capabilities, making it moderately risky. While it provides tools for managing Yuque documents, the absence of sandboxing and reliance on API token authentication require careful management of credentials and permissions to prevent unauthorized access or data manipulation.
- API token authentication
- Granular MCP tools with varying danger levels
- No shell execution capabilities
- Clear separation of read and write operations
- Supports both HTTP and CLI modes
- Write and delete operations are supported
- Potential for data modification or deletion if API token is compromised
- No explicit sandboxing mechanism described
- Reliance on user-provided API token for authentication
- Exposure to the internet if running in HTTP mode
