flomo-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
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
Only one tool exists, so there is no possibility of overlap or misselection. Its purpose (write note to flomo) is completely distinct and unambiguous.
The single tool name write_note follows a clear verb_noun snake_case convention. With no other tools to compare, it is consistent by default.
A single tool is too few for a flomo integration, which typically would include reading, listing, searching, or managing notes. The surface feels under-scoped for the server's apparent domain.
The server only supports writing notes; there is no way to retrieve, list, search, update, or delete notes. This leaves significant gaps for any agent needing to interact with existing flomo content.