MCP Server Flomo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_noteC | Write note to flomo |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'write_note' has a single, clear purpose that cannot be confused with any other tool in this set.
The naming follows a consistent verb_noun pattern ('write_note'), and with only one tool, there is no inconsistency to evaluate. The pattern is clear and predictable.
A single tool is too few for a note-taking server, as it lacks basic operations like reading, updating, deleting, or searching notes. This minimal set severely limits functionality and will likely cause agent failures in typical workflows.
The tool surface is severely incomplete for a note-taking domain. It only provides write capability, missing essential operations such as get_note, list_notes, update_note, delete_note, and search_notes, which are critical for full lifecycle management.