GetNote MCP Server
Related Servers
Alternatives to GetNote MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Joplin through its API, allowing search, creation, editing, organization, tagging, import, and deletion of notes, notebooks, and tags.-
- 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
- AlicenseBqualityDmaintenanceIntegrates with Get笔记 (GetBiji) API to enable AI-powered knowledge base search and retrieval. Provides tools for enhanced semantic search, raw content recall, and rate limit monitoring.34 npm2MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to manage Joplin Notes through the Web Clipper API, supporting note creation, updates, search, notebook organization, and tag management.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Joplin notes, notebooks, and tags through a standardized interface, supporting search, creation, editing, deletion, tagging, trash recovery, and file imports.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Joplin notes, notebooks, and tags through a standardized interface, supporting search, creation, updates, deletion, tagging, trash recovery, and file import.-
TDQS
Scored across 49 tools
The set is broadly split into notes, topics, uploads, and content sources, but several tools overlap in practice: list_notes, list_topic_notes, get_notes, recall, and recall_knowledge all find/read notes, and the upload credential/operation tools have parallel image-vs-file variants with intricate boundaries. Descriptions are detailed and often disambiguate, but the sheer number of similar read/search paths leaves real misselection risk.
Most tools follow a snake_case verb_noun pattern (list_notes, create_topic, delete_topic_directory, follow_topic_blogger), and related tools cluster predictably. Minor deviations exist: save_note instead of create_note, recall without a noun, singular/plural tag inconsistency (add_note_tags vs delete_note_tag), and generic get_upload_operation for the image-specific operation.
49 tools is very heavy for a single MCP server, even for a broad note/knowledge-base platform. Many granular facets (attachments, timeline, chapters, quick note, todos, marks, transcripts) and parallel upload flows could be consolidated or grouped, reducing agent selection burden.
Note operations are fairly complete: create, read, update, delete, tags, sharing, batch reads, semantic search, attachments, transcripts, and topic membership. However, knowledge-base lifecycle coverage is incomplete with no update/delete/fetch-detail topic operations, and blogger/live tools support follow/list/detail but no unfollow, creating notable dead ends in management workflows.