Skip to main content
Glama
adou0510

flomo-mcp

by adou0510
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

flomo-mcp MCP Server

write nodes to flomo

This is a TypeScript-based MCP server that implements a simple notes system. It demonstrates core MCP concepts by providing:

  • Resources representing text notes with URIs and metadata

  • Tools for creating new notes

  • Prompts for generating summaries of notes

Features

Resources

  • List and access notes via note:// URIs

  • Each note has a title, content and metadata

  • Plain text mime type for simple content access

Tools

  • create_note - Create new text notes

    • Takes title and content as required parameters

    • Stores note in server state

Prompts

  • summarize_notes - Generate a summary of all stored notes

    • Includes all note contents as embedded resources

    • Returns structured prompt for LLM summarization

Related MCP server: Mowen Notes MCP Server

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Installation

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "flomo-mcp": {
      "command": "/path/to/flomo-mcp/build/index.js"
    }
  }
}

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

Available Tools

1 tool
write_noteC

write note to flomo

ParametersJSON Schema
NameRequiredDescriptionDefault
contentYesText content of the note with Markdown formatting

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden for disclosing behavioral traits. It only states the action ('write note to flomo') but does not mention potential side effects (e.g., creating a new note, overwriting existing content), authentication requirements, rate limits, or return behavior. This is minimal and does not add value beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short ('write note to flomo') to the point of under-specification. While it avoids verbosity, it barely adds information beyond the tool name and lacks a complete sentence structure. It is more under-specified than concisely sufficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and no output schema, so the description need not explain return values. However, the description does not mention what happens on success/failure, response format, or any side effects. It is minimally adequate but leaves gaps that would be important for an agent to know.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for the single parameter 'content', which fully explains its meaning and Markdown formatting. The tool description itself adds no param details, but since the schema covers everything, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'write note to flomo' clearly states the action (write a note) and the target (flomo), making it specific enough to convey the tool's purpose. While it doesn't distinguish from siblings because none are listed, it is not a tautology and adds the destination context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives, prerequisites, or conditions. The description offers no context for if/when this should be chosen, leaving the agent without usage direction beyond the basic action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedwrite_note
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusing it with others. The single tool's purpose is clearly defined as writing a note to Flomo.

Naming Consistency5/5

The tool name 'write_note' follows a clear verb_noun pattern. Consistency is trivially maintained with only one tool.

Tool Count2/5

A single tool is too few for the apparent scope of a Flomo integration, which would typically include reading, listing, updating, or deleting notes. The server feels under-scoped.

Completeness2/5

The server only supports writing notes, lacking essential operations like fetching, listing, updating, or deleting notes. This is a significant gap for a note-taking service.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • approveit MCP Server

    HJH0924
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    A simple notes system that allows creating, storing, and accessing text notes through MCP resources and tools, with built-in prompt support for generating summaries of stored notes.
    -

  • Mowen Notes MCP Server

    z4656207
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables interaction with Mowen Notes to create, edit, and manage rich text content including file uploads and internal note links. It allows users to manage their notes directly within MCP-compatible environments like Cursor or Claude Desktop.
    47
    MIT

  • flomo-mcp

    hutusi
    F
    license
    B
    quality
    D
    maintenance
    Enables writing and managing notes to flomo via MCP. Provides tools for creating notes, resources for accessing them, and prompts for summarization.
    1
    15 npm
    -

Appeared in Searches