flomo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOMO_API_URL | Yes | Flomo webhook URL for posting notes |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_noteB | Write note to flomo |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_notes | Summarize all notes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| First Note | A text note: First Note |
| Second Note | A text note: Second Note |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of overlap or confusion between tools. The intent is unambiguous.
The single tool name 'write_note' follows a clear verb_noun pattern, which is consistent and predictable even with only one tool present.
With only one tool, the server feels very thin for a Flomo integration. A typical note-taking service would require multiple operations (e.g., read, update, delete), so the small count is likely a limitation rather than a deliberate scope.
The tool surface is severely incomplete for the stated purpose. Only 'write_note' (create) is available, with no way to retrieve, update, list, or delete notes, leaving obvious dead ends for any real workflow.