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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_noteC | Create a new note |
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 |
|---|---|
| This is note 1... | A text note: This is note 1 |
| This is note 2... | A text note: This is note 2 |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool has a clear, unique purpose.
The tool name 'write_note' follows a consistent verb_noun pattern, which is clear and predictable even as a standalone.
A single tool for a Flomo integration feels insufficient for the apparent scope of a note-taking service. Most such servers would include at least retrieval or management operations, making this too few.
The tool surface is severely limited, providing only note creation with no ability to read, update, delete, or list notes. This leaves obvious gaps that would prevent agents from performing common workflows.