Summary
Capture without a context switch: one call and the note is in flomo.
One tool with one argument sets the boundary clearly — this is a capture path, not a way to work with an existing flomo library, since reading, editing and tag management are all absent. Because the account is addressed by FLOMO_API_URL, pointing notes at a different account is a configuration change rather than a sign-in, which is what makes it usable from a shared or headless environment.
What it is
A single-tool server that posts note content to a flomo account through the API URL configured for it.
What you get
- write_note sends a note's content to flomo in one call, with content as its only argument
- The destination is fixed by FLOMO_API_URL rather than by a login, so no session is held open and no token is refreshed mid-conversation
Requirements
FLOMO_API_URL for the account the notes should land in. MIT licensed.
Setup effort
One command — npx -y @chatmcp/mcp-server-flomo