joplin-mcp-server
Related Servers
Alternatives to joplin-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA MCP server for Joplin note-taking application that enables interaction with Joplin notes through the web clipper API, supporting notebook hierarchy and running in Docker.-
- AlicenseAqualityAmaintenanceA minimal MCP server that enables interaction with Joplin notes and notebooks through the local Web Clipper REST API, providing tools for search, create, update, and note management.13MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Joplin Server that gives LLMs full access to notes, notebooks, tags, and attachments via the REST API.5MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides standardized tools for querying and retrieving notes from Joplin personal knowledge manager through its API, enabling AI assistants to access and reference personal notes contextually.9MIT
- MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI assistants read/write access to Joplin notes through the local REST API, with 20 tools for managing folders, notes, todos, tags, and bulk operations.MIT
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized around specific resources (folders/notebooks, notes) and actions (create, delete, edit, list, read, search), making it easy for an agent to select the right tool for any task.
Tool names follow a consistent verb_noun pattern throughout (e.g., create_folder, delete_note, edit_note, list_notebooks). All tools use snake_case and clear, descriptive verbs that match their actions precisely.
With 11 tools, this server is well-scoped for managing Joplin notes and notebooks. Each tool earns its place by covering essential CRUD operations and additional utilities like search and multi-note reading, without being overwhelming or too sparse.
The toolset provides complete CRUD/lifecycle coverage for both folders/notebooks and notes, including create, read, edit, delete, list, and search operations. There are no obvious gaps, ensuring agents can handle all core workflows without dead ends.