FlowNoter MCP Server
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 |
|---|---|
| save_conversation_noteA | Save recent conversation messages as a markdown note. The note will be saved in the 'notes' folder with a filename based on the user's question. Automatically filters out tool calls and intermediate processing steps, keeping only user questions and final assistant responses. You can specify how many recent messages to include. |
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 has a single, clear purpose: saving conversation messages as markdown notes.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'save_conversation_note' follows a clear verb_noun pattern, but with no other tools to compare to, it cannot be inconsistent.
A single tool is too few for a server named 'FlowNoter MCP Server', which suggests a broader note-taking or conversation management domain. While the tool is useful, the server lacks basic operations like listing, retrieving, updating, or deleting notes, making it feel incomplete and under-scoped.
The server is severely incomplete for a note-taking domain. It only provides a 'save' operation, missing essential CRUD functionality such as listing existing notes, retrieving note content, updating notes, or deleting notes. This creates significant gaps that will hinder agent workflows.