Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FLOMO_APP_PATHNoPath to the flomo desktop app, for when flomo is not installed at the default location (e.g. "/你的路径/flomo.app"). No API key or credentials are needed — authentication is handled by the logged-in flomo desktop client over the Chrome DevTools Protocol (127.0.0.1:9222)./Applications/flomo.app

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
whoamiA

验证 flomo 连接:显示当前登录账号、笔记与标签总数。未登录时报错,需先在 flomo 应用中登录

list_memosA

列出笔记。mode=recent 最近更新(最新在前,最多200条);mode=all 全量按时间升序游标翻页(每页最多100条);传 tag 按标签过滤(前缀匹配含子标签,如 阅读 也含 阅读/读书,全量扫描后按更新时间降序翻页,忽略 mode)

search_memosA

按关键词搜索笔记(匹配正文与标签,大小写不敏感,结果按更新时间降序)。flomo 无远程搜索接口,每次调用全量拉取后本地过滤;翻页时传 next_cursor 且 keyword 保持不变

get_memoA

获取单条笔记全文(HTML 与纯文本)。update_memo 前先调用本工具取当前内容

create_memoA

创建笔记。标签用 #标签名 语法写在 content 中(flomo 无独立建标签接口,标签由内容隐式创建)

update_memoA

更新笔记内容(全量替换,自动保留原创建时间/置顶状态/附件)。先 get_memo 取原内容再修改回写

delete_memoB

删除笔记(移入回收站,可在 flomo 回收站恢复)

syncA

手动触发同步(等同点击 flomo 界面左下角同步按钮):拉取服务端最新笔记/标签到本地并推送本地待同步修改,返回同步统计。已有同步在进行中时返回 code=SYNCING

list_tagsA

浏览标签树:不传参数=一级标签;传 tag_name=其直接子级;加 recursive=true=其下全部后代。count 为 null 表示计数不可用

rename_tagB

重命名标签(层级用 / 分隔,如 开发/Linux)

pin_tagC

置顶标签

unpin_tagC

取消置顶标签

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 12 tools

Disambiguation4/5

Each tool maps to a distinct resource+action, and the pin/unpin pair, get_memo vs update_memo, and the tag operations are all cleanly separated. The only mild overlap is list_memos vs search_memos, which both paginate over the memo set, but the descriptions clarify recent/all/tag-filter vs keyword-filter well enough to avoid misselection.

Naming Consistency4/5

Almost everything follows a consistent snake_case verb_noun pattern (list_tags, rename_tag, list_memos, create_memo, get_memo, update_memo, delete_memo). Only whoami and sync break the pattern, but both are widely understood conventional names so the set stays readable.

Tool Count5/5

Twelve tools is well within the ideal range and every tool earns its place: six memo CRUD/search operations, four tag operations, plus a health check and an explicit sync. Nothing feels redundant or padded for a single-domain note app.

Completeness4/5

Memo lifecycle is fully covered (create, list, search, get, update, delete-to-trash) and tags cover list/rename/pin/unpin; tag creation is explicitly noted as implicit via #tag in content. The gap is the absence of tag deletion/merge and any trash restore tool, which agents cannot work around within this surface.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues