notepm-mcp-server
Related Servers
Alternatives to notepm-mcp-server
No user-submitted related servers found.
Related Servers
AlicenseBqualityCmaintenanceAn MCP server that enables AI assistants to interact with the Notion API, allowing them to search, read, comment on, and create content in Notion workspaces through natural language commands.19152,494 npm4,641MIT- AlicenseAqualityDmaintenanceAn MCP server that provides AI assistants with full access to Notion workspaces, enabling search, read, create, and update pages, databases, and blocks.1312 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets AI assistants search, read, and write to a Wiki.js personal wiki, enabling persistent knowledge management through Markdown pages.181 npm2Apache 2.0
- AlicenseAqualityAmaintenanceAn unofficial MCP server that lets AI clients create and update article drafts on your own note.com account using session cookies.4MIT
- AlicenseAqualityBmaintenanceA personal notes MCP server that allows AI assistants to create, search, edit, and manage notes stored in a local SQLite database.6MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to search, read, and create notes across six note-taking platforms (Feishu, Obsidian, Notion, Yuque, OneNote, Evernote) through a single unified interface.MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource-and-action pair: folders, notes, pages, and tags are clearly separated, and actions like list, create, get, update, and search do not overlap. While the relationships between notes, folders, and pages could be conceptually confusing, the descriptions make each tool's purpose unambiguous.
All tool names follow a consistent lowercase snake_case verb_noun pattern, such as list_folders, create_page, update_page, and search_pages. There are no mixed conventions, vague verbs, or irregular variations.
Eight tools is a well-scoped set for a NotePM integration covering folder listing, note listing, page operations, and tag operations. Each tool serves a clear purpose without redundancy or excessive surface area.
Page operations cover create, read, update, and search but lack delete, which is a notable lifecycle gap. Tags support create and list but not update or delete, and folders/notes are read-only, so the surface is functional but not fully complete.