Skip to main content
Glama
TaylorChen

flomo-mcp

by TaylorChen
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

flomo-mcp MCP Server

flomo-mcp

一个基于 MCP（Model Context Protocol）的服务，将文本快速发布到 flomo。

功能特性

  • 提供 write_note 工具：把文本作为一条 flomo 笔记发布

  • 提供资源/提示示例：示例 notes 资源、summarize_notes 提示

安装与构建

  1. 克隆仓库

  2. 安装依赖：npm install

  3. 构建：npm run build

配置

  • 以环境变量或启动参数设置 Flomo Webhook：

    • 环境变量：FLOMO_API_URL="https://flomoapp.com/iwh/xxx/yyy/"

    • 启动参数：--flomo_api_url=https://flomoapp.com/iwh/xxx/yyy/

在 Cursor 中使用

  1. 打开 ~/.cursor/mcp.json，新增：

{
  "mcpServers": {
    "flomo-mcp": {
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/flomo-mcp/build/index.js"],
      "env": {
        "FLOMO_API_URL": "https://flomoapp.com/iwh/xxx/yyy/"
      }
    }
  }
}

  1. 在 Cursor 侧边栏 MCP 中启用 flomo-mcp

  2. 调用工具 write_note，传入：

{ "content": "今天开发了一个 MCP 服务器，很开心记录一下" }

本地调试（可选）

  • 运行 Inspector：npm run inspector

  • 交互测试资源、提示与工具

许可协议

  • 本项目使用 MIT License，详见 LICENSE

贡献

  • 欢迎 PR/Issue，提交前请：

    • 代码通过 npm run build

    • 不要提交 build/、node_modules/、私密信息

write notes 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

Related MCP server: flomo-mcp-server

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

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_noteB

Write note to flomo

ParametersJSON Schema
NameRequiredDescriptionDefault
contentYesText content of the note

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Write note to flomo' without mentioning authentication requirements, side effects, or success/failure behavior, leaving significant ambiguity for an agent.

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

Conciseness5/5

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

The description is a single, concise sentence with no unnecessary words. It is front-loaded and easily parsed.

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?

Given the tool's simplicity (one parameter, no output schema), the description is arguably sufficient for basic invocation, but it lacks contextual details about the flomo service or expected behavior. It is adequate but leaves room for improvement.

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 provides a complete description of the single 'content' parameter, and the description adds no additional syntax or usage details. With 100% schema coverage, a baseline score 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 states a clear verb ('Write') and a specific resource ('note to flomo'), making the tool's function immediately understandable. With no sibling tools, it doesn't need differentiation, though 'flomo' may be an unfamiliar service to some users.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It simply states the action without context.

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. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.1
    • First observedwrite_note
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of overlap or confusion between tools. The intent is unambiguous.

Naming Consistency5/5

The single tool name 'write_note' follows a clear verb_noun pattern, which is consistent and predictable even with only one tool present.

Tool Count2/5

With only one tool, the server feels very thin for a Flomo integration. A typical note-taking service would require multiple operations (e.g., read, update, delete), so the small count is likely a limitation rather than a deliberate scope.

Completeness1/5

The tool surface is severely incomplete for the stated purpose. Only 'write_note' (create) is available, with no way to retrieve, update, list, or delete notes, leaving obvious dead ends for any real workflow.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TaylorChen/flomo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server