Flomo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOMO_API_URL | Yes | Your Flomo API URL from https://v.flomoapp.com/mine |
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 |
|---|---|
| newNoteC | Create a new note in 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 'newNote' has a single, clear purpose: creating a new note in Flomo, so an agent cannot misselect between non-existent alternatives.
The single tool name 'newNote' follows a clear verb_noun pattern (new + Note), and with only one tool, consistency is inherently perfect. There are no other tools to compare against, so no inconsistencies can arise.
A single tool is too few for a note-taking server like Flomo, which typically involves operations beyond just creation, such as retrieving, updating, deleting, or listing notes. This minimal set severely limits agent functionality and feels incomplete for the domain.
The tool surface is severely incomplete for a note-taking service. It only supports creating notes (newNote), with no tools for reading, updating, deleting, searching, or managing notes. This creates significant gaps that will cause agent failures in common workflows.