Yonote MCP Server
Related Servers
Alternatives to Yonote MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables interaction with Yuque (语雀) knowledge base platform through their API. Supports document management, search, and repository operations including creating, reading, updating, and deleting documents in multiple formats.933 npm3MIT
- AlicenseNot gradedqualityCmaintenanceLets an agent read and write Yuque knowledge bases, documents, tables of contents, notes, and resources through the Yuque open API. It bundles the upstream server and prompts for a personal token at first run or when a token expires, so all 19 tools stay visible and a single call continues after credentials are supplied.BSD 2-Clause "Simplified"
- AlicenseNot gradedqualityFmaintenanceEnables interaction with SiYuan Note through its API for comprehensive note management. Supports searching, creating, editing documents, managing notebooks, and daily notes operations through natural language commands.44 npm15Apache 2.0
- AlicenseBqualityCmaintenanceEnables interaction with note.com through API to search and read articles, manage posts and drafts, handle comments and likes, retrieve analytics, and access membership information.3317 npm30ISC
- AlicenseBqualityDmaintenanceEnables access to Yuque (语雀) documentation through cookie-based authentication, supporting document retrieval, search, TOC navigation, and content management from knowledge bases via URL or namespace.4523 npm4MIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents access to a persistent document workspace, letting them search, read, and update notes, guides, and project documentation across a full catalog of tools, prompts, and resources. It connects either to the hosted Cloud endpoint over Streamable HTTP with OAuth or API-key auth, or to a self-hosted instance through a stdio bridge.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: collections_list retrieves collections, documents_info gets details of a specific document, and documents_list lists documents. There is no overlap in functionality, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent verb_noun pattern with snake_case: collections_list, documents_info, and documents_list. The naming is predictable and readable throughout, with no deviations or mixed conventions.
With only 3 tools, the server feels thin for a note-taking domain, as it lacks essential operations like creating, updating, or deleting collections or documents. While the tools are well-scoped individually, the count is borderline low for covering basic CRUD workflows.
The tool surface is significantly incomplete for a note-taking server. It only provides read operations (list and get info) for collections and documents, with no ability to create, update, or delete resources. This will likely cause agent failures when trying to perform common tasks like adding or modifying notes.