flomo-mcp
Related Servers
Alternatives to flomo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables users to create and save notes in Flomo directly through AI chat interactions using natural language commands. Seamlessly integrates with AI assistants like Claude and Cursor to capture thoughts and information.162 npm17MIT
- FlicenseBqualityDmaintenanceEnables writing and managing notes to flomo via MCP. Provides tools for creating notes, resources for accessing them, and prompts for summarization.112 npm-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Memos instances for personal note-taking and knowledge management. Supports creating, searching, updating, and organizing memos with tags, dates, and visibility settings through natural language.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Memos instances for knowledge management. Supports searching, creating, updating, and retrieving memos with markdown content, tags, and visibility controls.45MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Memos instances, supporting multi-instance connections, note management, tags, attachments, and shortcuts.1619 npm2MIT
- FlicenseAqualityDmaintenanceEnables to interact with Memos note-taking service, allowing search, creation, retrieval, and updating of notes through natural language.44-
TDQS
Scored across 12 tools
Each tool maps to a distinct resource+action, and the pin/unpin pair, get_memo vs update_memo, and the tag operations are all cleanly separated. The only mild overlap is list_memos vs search_memos, which both paginate over the memo set, but the descriptions clarify recent/all/tag-filter vs keyword-filter well enough to avoid misselection.
Almost everything follows a consistent snake_case verb_noun pattern (list_tags, rename_tag, list_memos, create_memo, get_memo, update_memo, delete_memo). Only whoami and sync break the pattern, but both are widely understood conventional names so the set stays readable.
Twelve tools is well within the ideal range and every tool earns its place: six memo CRUD/search operations, four tag operations, plus a health check and an explicit sync. Nothing feels redundant or padded for a single-domain note app.
Memo lifecycle is fully covered (create, list, search, get, update, delete-to-trash) and tags cover list/rename/pin/unpin; tag creation is explicitly noted as implicit via #tag in content. The gap is the absence of tag deletion/merge and any trash restore tool, which agents cannot work around within this surface.