Skip to main content
Glama
yomi

yomi

Official
by RikaiDev

Yomi (読み) — 个人 LINE MCP 服务器

Yomi 是一个面向你个人账户的开源 LINE MCP 服务器。你可以从 Claude 或任何本地 AI 代理读取、回复、发送图片,并搜索所有对话——无需浏览器、机器人账户或 LINE 自己的客户端。

这个名字有多种读法。読み(yomi)——一种阅读:不仅仅是解析你的消息,而是像你一样读懂情境。詠み(yomi)——吟诵:它不会沉默地阅读,而是把内容读回给你。还有 黄泉(yomi)——不可触及的领域;正是 黄泉帰り(yomigaeri)中的 yomi,意为“从黄泉归来”。如同在两个领域之间穿梭的信使,Yomi 穿越封印与沉默,将你对话深处仍可读的消息带回光明。它不会召唤已经失去的历史;它帮助尚未消失的东西被再次看见。

与 LINE 官方 Bot MCP 服务器不同,后者通过 Messaging API 将 AI 代理连接到 LINE 官方账户,而 Yomi 作为辅助设备连接到您现有的个人 LINE 账户和对话。

Yomi 直接使用 LINE 的 TCompact-over-HTTPS 协议,解密 Letter-Sealing(E2EE)消息和媒体,并通过一个小型 stdio MCP 服务器将结果暴露给任何 AI 代理。将 Claude Desktop(或任何 MCP 客户端)指向它,代理就能像你一样跟上你的 LINE——读取、回复、发送图片、提及某人,并在本地搜索你的全部历史——而且通过 get_insight,还能读取情境:哪些对话在等待你的回复,谁将你的世界联系在一起,以及哪些已经逾期。

没有官方 API,没有机器人账户,没有 webhook。Yomi 以辅助设备身份登录你自己的账户。

指南:什么是 LINE MCP 服务器? · LINE MCP 是什么?Yomi、官方 Bot 与桌面自动化的差异。

license runtime protocol npm

非官方。 Yomi 是一个独立的个人项目,与 LINE 无关,也未获得 LINE 的认可。使用它可能违反 LINE 的服务条款,并且在你的账户上运行额外的客户端可能面临限流或封禁的风险。它旨在用于阅读你自己的账户。请自行承担使用风险。参见免责声明。


快速开始

原生桌面预览

Yomi Desktop 将 LINE 收件箱和本地代理工作区整合到一个原生应用中。它自带运行时:用户无需安装 Node、打开终端、克隆此仓库或配置 YOMI_RUN_MJS。 原生桌面版与下文描述的 Claude Desktop MCPB 扩展是分开的。

平台

普通用户包

签名状态

安装体验

macOS 14+, Apple Silicon

Yomi-Desktop-macOS-arm64-<version>.dmg

已使用 Developer ID 签名并通过 Apple 公证

打开 DMG → 将 Yomi 拖到应用程序 → 打开 Yomi

Windows 10/11 x64

Yomi-Desktop-Windows-x64-<version>-Setup.exe

可信 OSS 签名申请进行中

在签名和安装程序冒烟测试通过之前,下载仍不可用

macOS 包已经过真实下载应用路径的测试:隔离的 DMG、安装到 /Applications、Gatekeeper 评估、首次启动、捆绑运行时消息刷新,以及无终端的 LINE 登录表单。Windows 安装程序包含等效的应用内手机/PIN 登录流程,并在发布前在原生 Windows 运行器上进行测试。

桌面构建是实验性的且非官方。LINE 的变更可能会破坏它们,运行额外的客户端可能使账户面临风险。建议使用测试账户并保留当前备份。预览安装程序仅在平台签名可用后作为 GitHub 预发布版发布。

参见桌面发布流程、代码签名政策和隐私政策。

MCP 服务器和桌面扩展

你需要 Node.js 和一个 LINE 账户。Yomi 通过 npx 在本地运行;你无需克隆此仓库、安装 Bun 或构建任何东西。首先运行 node --version,如果命令缺失或版本不受支持,请安装当前的 LTS 版本。

Yomi 的本地搜索索引使用 Node 内置的 node:sqlite,因此需要 v22.13 或更高版本——除了 v23.0–v23.3,这些版本虽然比 v22.13 新,但仍然缺少该模块(它在 22.13.0 和 23.4.0 中都被取消了标志)。任何当前的 LTS 都可以。这是 package.json 中的 engines.node;Yomi 的其余部分可以在较旧的 Node 上运行,但搜索、范围和捕获功能则不行。

⚠️ Yomi 需要一个在你自己的机器上运行它的客户端。 仅云端工具(ChatGPT、Claude.ai 网页版)无法运行 Yomi。在 Claude Desktop 或 Claude Code 中配置 Yomi,它就能在聊天和 Cowork 中工作,因为 Desktop 会在你的机器上启动 Yomi,而 Cowork 的本地会话会加载它。不要要求 Cowork 为你安装 Yomi:Cowork 的 shell 运行在一个一次性的虚拟机中,而不是你的机器上,所以它在其中安装的任何东西在会话结束时都会消失。请按照以下步骤,在你自己的终端中操作。

选择你实际使用的客户端,只遵循该部分。Claude Code 和 Claude Desktop 有各自的 MCP 设置;配置一个不会配置另一个。

这是最简单的路径,也是唯一完全不需要命令行的路径。Claude Desktop 自带 Node 运行时,因此无需安装其他任何东西。

  1. 从最新发布下载适合你机器的捆绑包:

    机器

    文件

    Windows (Intel/AMD)

    yomi-win32-x64.mcpb

    Mac (Apple Silicon)

    yomi-darwin-arm64.mcpb

    Linux (x64)

    yomi-linux-x64.mcpb

  2. 在 Claude Desktop 中,打开 设置 → 扩展,将下载的文件拖到该页面(或直接双击该文件)。

  3. 查看它要求的内容,点击 安装。

  4. 开始对话并说 “登录 LINE”。Yomi 会显示一个表单,你输入手机号码,然后在手机上确认。全程无需终端。

这完全跳过了配置文件,也绕过了下文描述的 Windows MSIX 错误。

Cowork 用户注意: 不要要求 Cowork 为你安装 Yomi。Cowork 的 shell 运行在一次性的虚拟机中——而不是你的机器上——它不会输入到你的真实终端。请按照上面的三次点击自行安装捆绑包;安装后,Cowork 的本地会话可以像使用任何其他工具一样使用 Yomi。

  1. 找到 npx 的完整路径:

    macOS / Linux: which npx
    Windows:       where npx
  2. 打开 Claude Desktop 配置文件:

    macOS:   ~/Library/Application Support/Claude/claude_desktop_config.json
    Windows: %APPDATA%\Claude\claude_desktop_config.json

    ⚠️ Windows:文档中的路径可能不是 Claude 实际读取的路径。 Claude Desktop 以 MSIX 包形式发布,其文件系统是虚拟化的。应用从以下位置读取配置:

    %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json

    而 设置 → 开发者 → 编辑配置 打开的是非虚拟化的 %APPDATA%\Claude\ 文件。它们是两个不同的文件,永远不会同步,因此写入文档路径的正确 Yomi 配置会被静默忽略——没有错误,没有日志,Yomi 根本不会出现。这是 claude-code#26073,仍然开放。如果重启后 Yomi 没有出现,请将相同的配置也写入上面的 LocalCache 路径。(不适用于 Claude Code,或非 MSIX 安装的 Desktop。)

  3. 在 mcpServers 下添加 Yomi,将示例 command 替换为步骤 1 中打印的完整路径。在 Windows 上,JSON 要求路径中的每个 \ 都写成 \\:

{
  "mcpServers": {
    "yomi": {
      "command": "/opt/homebrew/bin/npx",
      "args": ["@rikaidev/yomi"]
    }
  }
}

例如,Windows 路径可能看起来像 "C:\\Program Files\\nodejs\\npx.cmd"。请使用你自己机器上报告的路径,而不是盲目复制任一示例。

⚠️ 你在这里指定的 npx 并不决定哪个 Node 运行 Yomi。 在 macOS 和 Linux 上,npx 是一个以 #!/usr/bin/env node 开头的脚本,因此它会运行 Claude Desktop 的 PATH 中排在最前面的 node——而不是你刚刚指向的 npx 旁边的 Node。Desktop 从桌面会话继承其 PATH,这通常不是你的终端的 PATH,而版本管理器(nvm、fnm、asdf、volta 等)会将自己的 node 放在所有其他内容之前。所以 which npx 可能报告一个完全现代的安装,而 Yomi 仍然在旧 Node 上启动。

症状很具体:登录、读取和发送都正常,但搜索、范围和捕获失败,日志显示 No such built-in module: node:sqlite。Yomi 会在该错误中打印它实际获得的运行时——请阅读它,而不是假设。

解决方案是给服务器一个 PATH,其第一个条目包含受支持的 node:

"yomi": {
  "command": "<the npx path from step 1>",
  "args": ["-y", "@rikaidev/yomi"],
  "env": { "PATH": "<dir holding a supported node><sep><a base PATH>" }
}

分隔符:macOS/Linux 上为 :,Windows 上为 ;。在其后保留一个可用的基础路径(/usr/local/bin:/usr/bin:/bin 或你平台的等效路径)——这会替换服务器的 PATH 而不是前置到它,而 npx 需要普通工具。

在 command 中指定绝对的 node 是不起作用的,无论看起来多么合理:npx 会将包自己的 bin 作为子进程启动,并再次从 PATH 中解析 node,所以 command 只决定谁运行 npx,而不是谁运行 Yomi。设置 PATH 才是真正到达服务器的。

使用 AI 代理配置? MCP 配置现在大多由代理编写,而不是手工编写,因此上述步骤是针对阅读自己机器的人类用户。代理应该解析这些值,而不是输出占位符,而且这个设置有一个值得直说的陷阱:在 command 中指定 npx 并不固定运行时。步骤:

  1. 找到一个实际拥有 Yomi 索引所需模块的 Node——不要从版本号推断:

    node -e 'require("node:sqlite")' && command -v node    # POSIX
    node -e "require('node:sqlite')" && where node         # Windows

    如果它抛出异常,该 Node 无法用于搜索/范围/捕获。尝试其他安装(which -a node、nvm ls、fnm list 等),直到有一个通过;然后才继续。

  2. 按照上面的 JSON,将该 Node 的目录写入 env.PATH,并在其后保留一个基础 PATH。在目标机器上解析该目录(步骤 1 中路径的 dirname);不要从本 README 中复制示例——它们是 Apple Silicon Homebrew 路径,几乎在所有地方都是错误的。

    不要改为在 command 中放置绝对路径的 node。这看起来像是更强的修复,但实际上不是:npx 会将包的 bin 作为子进程启动,并为其从 PATH 重新解析 node,所以 command 只决定谁运行 npx。这是经过测量而非假设的——当 Node 20 在 PATH 中排在首位时,command 固定仍然给服务器提供了 Node 20。

    command -v 也可能返回一个包装器而不是真正的二进制文件——堆垫片、本地优先的 npx 包装器和版本管理器存根都很常见,有些会根据客户端的工作目录表现不同。不要试图推理出“真正的”那个。步骤 3 会解决这个问题。

  3. 使用一个触及索引的工具进行验证。yomi version 不是验证——它打印一个字符串而不打开 SQLite,所以它在一个无法运行搜索的 Node 上也会成功。调用 get_scope_policy:它需要 SQLite 且不需要 LINE 登录。如果它返回策略文本,则运行时正确。如果失败,错误会指出实际运行的 Node 及其所需内容。

  4. 完全退出并重新打开 Claude Desktop。首先确认 Yomi 已加载在 Settings → Developer 下:如果 Yomi 未列在那里,说明 Claude 从未读取你的配置——在 Windows 上,请参阅步骤 2 中的 MSIX 警告。一旦列出,工具即可在聊天和 Cowork 的本地会话中使用。

你不需要为此设置安装 Claude Code。

claude mcp add yomi -- npx @rikaidev/yomi

启动一个新的 claude 会话。Yomi 工具应该会自动出现。此命令仅配置 Claude Code;它不配置 Claude Desktop。

此形式将运行时留给 PATH,只要你的 claude 会话解析到的 node 是受支持的版本就没问题——这是你可以看到的同一个 PATH,与 Claude Desktop 的不同。使用 node -e 'require("node:sqlite")' 检查。如果它抛出异常,或者你根本不想依赖 PATH,请显式指定 Node:

claude mcp add yomi -e PATH="$(dirname "$(command -v node)"):$PATH" -- npx -y @rikaidev/yomi

无论哪种方式,请使用 get_scope_policy 而不是 yomi version 进行验证:版本命令打印一个字符串而不打开 SQLite,所以它在一个无法运行搜索的 Node 上也会通过。

在此仓库的克隆中运行 Claude Code? 请明确指定 @rikaidev/yomi@latest。如果没有标签,npx 会先查找本地 bin,而在此仓库中 package.json 声明了 "bin": {"yomi": ...},但没有任何东西将其链接到 node_modules/.bin——所以 npx 会跳过安装并以 sh: yomi: command not found 失败。显式标签会使其获取已发布的包。仅影响 Yomi 本身的工作副本;其他任何地方,未加标签的形式都没问题。

此标准配置适用于大多数 MCP 客户端:

{
  "mcpServers": {
    "yomi": {
      "command": "npx",
      "args": ["@rikaidev/yomi"]
    }
  }
}

Cursor Settings → MCP → Add new MCP Server → 命名为 yomi,命令类型,值:npx @rikaidev/yomi

或者添加到项目根目录的 .cursor/mcp.json。

添加到 .vscode/mcp.json:

{
  "servers": {
    "yomi": {
      "command": "npx",
      "args": ["@rikaidev/yomi"]
    }
  }
}

添加到 ~/.config/opencode/opencode.json:

{
  "mcp": {
    "yomi": {
      "type": "local",
      "command": ["npx", "@rikaidev/yomi"],
      "enabled": true
    }
  }
}
codex mcp add yomi npx @rikaidev/yomi

或者添加到 ~/.codex/config.toml:

[mcp_servers.yomi]
command = "npx"
args = ["@rikaidev/yomi"]

添加到 cline_mcp_settings.json:

{
  "mcpServers": {
    "yomi": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@rikaidev/yomi"]
    }
  }
}

添加到 ~/.codeium/windsurf/mcp_config.json — 与标准配置相同的 JSON。

amp mcp add yomi -- npx @rikaidev/yomi

Advanced settings → Extensions → Add custom extension → 命名为 yomi,类型 STDIO,命令:npx @rikaidev/yomi

grok mcp add yomi -- npx @rikaidev/yomi

首次登录

连接后,告诉代理:

"登录 LINE — 我的号码是 +8869XXXXXXXX。"

在手机上批准设备(参见 登录),然后:

"总结我未读的 LINE 消息,并告诉我谁在等待回复。"


Related MCP server: line-desktop-mcp

你能做什么

Yomi 通过 MCP 暴露 20 个工具(值得命名的那些;见表格)。大型读取结果使用 token 高效的 TOON;小型状态和写入结果使用紧凑的 JSON。错误保持纯文本,媒体使用原生 MCP 图像/音频/资源内容。 下面的“诚实错误”是指明确命名问题的失败(例如 missing_decrypt_material)——Yomi 从不伪造回退、占位符或虚假成功。

读取

工具

功能

get_unread_digest

一次性:每个有未读消息的会话,包含其最新消息,E2EE 解密,发送者名称已解析。专为“总结我的未读并建议下一步”而设计。只读——从不标记任何已读。

list_conversations

聊天/群组/房间,包含未读计数和解密后的最后一条消息预览。最新活跃的排在最前。

get_chat_messages

单个会话,已解密。使用 before 游标深入分页。每条消息携带任何原始 MENTION 元数据,以便你看到谁被 @ 提及(文本中的字面 @name 不是提及)。

get_message_media / get_message_image

任何解密的附件(图像/视频/音频/文件)。非媒体时给出诚实错误。

find_contact / list_contacts

按名称子字符串查找好友列表,或完整列表。原始 LINE 数据——无模糊评分,无亲和力排名。

get_group_members

持久群组的成员。没有群组记录的临时房间会诚实地失败,而不是返回虚假的空列表。

洞察(读取情境,而不仅仅是消息)

工具

功能

get_insight

一个紧凑的上下文网络,覆盖你的本地索引——代理推理的结构,而不是消息转储。返回 connectors(出现在你的 ≥2 个聊天中的人,以及结构性的桥梁,移除它们会分裂你的联系人图)、relationships(每个会话的参与度和你在那里的典型回复节奏),以及 open(最新消息不是你的会话,按它们相对于该节奏的逾期程度排序,每个都有预览)。它只计算结构和统计:它故意不决定消息是发给谁的、是开放请求还是结束确认,或昵称的真实身份——那是代理从每个预览中读取的语言,仅在线程值得判断时才解引用 get_chat_messages。编码为 TOON,约为等效 JSON 的 ¼ token。

写入(这些真的会发送——不是草稿)

工具

功能

send_message

立即发送 E2EE 文本消息(1:1 使用配对密钥,群组/房间使用群组密钥)。可选的 mentions 附加真实的 @ 提及,LINE 会高亮并通知;省略它们,字面 @name 只是不会通知任何人的文本。每次调用发送一次,无重试。

send_image

加密、上传到 LINE OBS,并立即发送 E2EE 图像。适用于 1:1、群组和房间。每次调用发送一次。如果无法解析密钥或上传被拒绝,则诚实失败。

mark_read

发送对方可见的已读回执。仅显式操作——读取消息和后台捕获从不标记任何已读。

搜索(本地、跨会话——LINE 没有这样的原语)

工具

功能

search_messages

对所有已索引的对话进行混合搜索。首次使用时自动收集,跨聊天多样化结果,并返回每个命中点周围的小段上下文窗口。返回 mode(hybrid/semantic/keyword),确保没有任何内容被隐藏。

collect_messages

显式批量索引到本地数据库 + 嵌入以支持语义搜索。唯一允许批量获取的工具;每次调用只运行一次,绝不在定时器上运行。

范围与隐私(全部离线工作,无需 LINE 会话)

工具

功能

exclude_chats

将对话加入拒绝列表 并清除 其已索引的数据。不仅仅是阻止未来捕获——如果拒绝列表把旧数据留在索引中,那就是虚假的隐私。

include_chats

重新允许某个对话(不会恢复已清除的数据)。

list_excluded_chats / get_scope_policy

显示拒绝列表 / 完整隐私策略(从 PRIVACY.md 读取)。

会话

工具

功能

login / login_complete

无密码的辅助设备登录。详见下文。login 是唯一可以在没有现有会话的情况下调用的工具。


登录

前提条件: 在你的主手机上,启用 設定 › 我的帳號 › 允許自其他裝置登入 (设置 › 账户 › 允许从其他设备登录)。没有它,LINE 永远不会向此设备提供登录提示——这是首次登录看似卡住的最常见原因。

⚠️ 单一桌面会话限制: LINE 每个账户只允许 一个桌面客户端会话同时存在。 由于 Yomi 以桌面辅助设备(DESKTOPMAC)身份连接,登录 Yomi 将使你的官方 LINE Desktop 应用退出登录(而重新登录 LINE Desktop 将使 Yomi 的会话失效)。你不能同时使用 Yomi 和官方 LINE Desktop 客户端。

你只需以 E.164 格式向代理提供你的电话号码——它会在调用工具时自行提供 地区(例如 +886 号码对应 TW)。

Yomi 驱动 LINE 的 无密码(辅助设备) 流程。登录如何呈现 取决于你的 MCP 客户端:

  • 具有 MCP elicitation 能力的客户端 — login 会提示你输入 电话/地区,在对话框中显示 PIN,并阻塞至完成。一次调用,无需 通过模型传递 PIN。你的电话号码永远不会进入对话记录。

  • 不具备该能力的客户端(例如当前的 Claude Desktop) — 需要两次调用。login(使用你的 电话 + 地区)在其结果中返回 PIN;在你的主手机上于 LINE 中输入 PIN 并批准该设备;然后调用 login_complete,它会阻塞直到 手机确认。代理应立即调用 login_complete——它负责 等待,因此你无需回报任何内容。

  • 从终端 — npx @rikaidev/yomi login 在 stdout 上运行整个流程,包括 PIN 和 所有内容。始终可作为后备方案使用。

唯一重要的截止时间是 LINE 的: 从 PIN 显示时起,你大约有 3 分钟 来输入 PIN 并批准设备。Yomi 自己的客户端会在那之后继续 监听很多分钟,所以手机慢永远不会是失败原因——只有 LINE 的 3 分钟代码有效期才是。

登录后,会话——包括登录 证书——会被持久化 (参见 下文),未来的登录 完全跳过 PIN。

还有一个实验性的 MCP Apps UI(一个 ui://yomi/login 卡片),适用于渲染交互式视图的客户端。它在 规范上是正确的,并且能在 MCP Inspector 下渲染,但某些宿主在获取资源时 未完成视图握手,因此它 仅用于显示,绝不在关键路径上—— 上述流程无论如何始终有效。

会话与凭据

Yomi 拥有自己的登录。启动时它调用一次 resumeSession(),从 macOS 钥匙串(服务 dev.rikai.yomi.credentials,账户 line)读取 LINE 会话,并在需要时静默刷新令牌。

  • 第一方凭据。 无密码登录会持久化认证令牌、 刷新令牌、证书、MID 以及 E2EE 密钥对本身——然后读回 它们以验证写入确实落盘。无法持久化的登录会在 登录时大声失败,而不是在下次重启时静默失败。

  • 共享会话。 会话存储在规范的 dev.rikai.yomi.credentials 钥匙串条目(或本地凭据存储)中,使 Yomi MCP 和 Yomi Desktop 能够 无缝共享完全相同的 LINE 登录会话。

  • 平台说明。 在 macOS 上,会话位于登录钥匙串中。在 Linux 和 Windows 上,Yomi 目前回退到本地 JSON 文件——功能可用,但 保护程度不如操作系统密钥存储,且经过的测试也不如 macOS 路径。 原生安全存储后端(libsecret / DPAPI)已计划中;在此之前,请 相应对待非 macOS 安装。

除 login 和离线范围/搜索工具外,每个工具在没有会话时 都会返回诚实的错误。Yomi 在其他方面是纯查询服务器——它从不轮询, 从不后台回填;每次工具调用只发出它需要的 LINE 请求, 而 collect_messages 是唯一一次跨多个聊天获取的路径。


搜索

LINE 没有跨对话搜索;Yomi 在本地构建了一个。索引是 仓库中被 gitignore 的 SQLite 数据库(data/search-index.db)——没有任何内容离开 你的机器。

搜索在设计上是 混合式 的。它始终运行 FTS5 关键词搜索(对 bigram 预处理文本进行 bm25,因此覆盖了没有词边界的 CJK 子串),并且 在存在嵌入时运行语义搜索,然后通过 倒数排名融合(Reciprocal Rank Fusion) 融合两个排名列表。纯语义搜索会静默丢弃 存在于未嵌入消息中的精确匹配;纯关键词会漏掉释义;融合两者 能同时呈现精确术语和语义匹配。响应的 mode 字段始终 报告哪些方法做出了贡献。

语义排名将每条消息保持为独立的向量。针对真实索引的 LINE 对话进行测试发现,嵌入重叠的对话窗口会稀释 中心消息并降低检索质量。因此上下文仅在排名之后添加: Yomi 限制单个聊天淹没顶部结果,并为每个胜出结果扩展 两侧各两条消息,使代理能看到赋予该命中意义的对话交流, 而不会削弱嵌入本身。

语义排名使用 Xenova/bge-small-zh-v1.5(BAAI 通用嵌入,小型, 以中文为主但支持多语言),通过 transformers.js 实现。嵌入 推理完全在 进程内 CPU 上运行——你的消息文本绝不会被发送到任何地方。

唯一的注意事项是 一次性模型下载:在首次 collect_messages 或 search_messages 时,transformers.js 会从 huggingface.co 获取模型(约 90 MB) 并在本地缓存;之后的每次运行完全离线。首次获取是 向 HuggingFace 发出的出站 HTTPS 请求,用于获取模型权重——它携带你的 IP 和 正在下载的模型信息,但不包含任何消息内容和 LINE 数据。如果你需要 Yomi 完全气隙运行,请在首次搜索前预填充 transformers.js 缓存(或将其指向 本地模型目录),这样就不会发出任何网络调用。


辅助设备的现实(在相信"我无法获取旧消息"之前请先阅读)

Yomi 以你账户上的 辅助设备 身份运行。这决定了它能看到什么:

  • 未启用 Letter Sealing 的群聊在 LINE 服务器上是明文——完整 历史和媒体,无任何限制。

  • 启用 Letter Sealing 的群聊是 E2EE 加密的,此时纪元(epoch)很重要。 此类 群组使用共享的 群组密钥 加密,该密钥会轮换(在成员变更或 客户端配置新密钥时)。LINE 只会向设备提供 当前 群组密钥——没有 API 可以获取已被取代的密钥。因此辅助设备只能解密 从其持有的密钥对应的纪元开始的消息;在 较早纪元——即 Yomi 获取当前密钥之前——发送的消息 可能无法解密,即使是在它 可以 读取较早历史的群组中 也是如此。这是 Letter Sealing 按纪元轮换群组密钥的固有限制, 不是这里的 bug。它也可能横向影响:你的手机持有的纪元 与 Yomi 持有的纪元不一定相同,因此 两个设备可能各自读取 同一个群组的不同片段。

  • 安装 Yomi 本身不会轮换任何内容,因此"在我安装 Yomi 之前"是 错误的边界。 Yomi 只会 解析 现有的群组密钥;它从不 注册(生成)密钥,因为生成会为每个成员轮换群组的共享密钥, 并使所有在旧密钥下加密的消息无法读取。因此全新安装 会获取 当前 密钥并读回到上次轮换——这可能早于 安装日期数月。边界是上次重新加密,而不是你的安装日期。而且 一旦 Yomi 见过某个纪元,它就会保留该密钥,因此安装 之后 的轮换 使其能够读取两侧的消息。如果某个群组一直到 今天 都无法解密, 那不是此限制——请报告该问题。

  • 1:1 媒体 使用账户级 E2EE 密钥链,辅助设备完全拥有 它(LINE 在配对期间同步它)——Yomi 可以 解密它能看到的 1:1 图片/文件。

  • 1:1 历史 回填 是唯一真正的限制。 LINE 不会像对群组那样 向辅助设备提供 过去的 1:1 消息历史。Yomi 连接期间 收到的消息可以正常解密;深入滚动到配对之前 的 1:1 历史可能会返回空。这是 LINE 服务端的限制, 不是这里的 bug。

当解密真正失败时,Yomi 会返回明确的 missing_decrypt_material 错误——绝不会返回虚假的卡片或占位符。沉默是诚实的;捏造的结果不是。


开发

适用于从事 Yomi 源代码的贡献者(需要 bun 或 Node.js 24+ — .nvmrc 固定了 CI 安装的相同 24 版本,因此在此目录中 nvm use 会选用它;请注意 nvm 不读取 engines,这就是为什么两者 分开声明并由测试守护):

bun install                 # install dependencies (or npm install)
bun run.mjs                 # run the stdio MCP server
bun run.mjs login           # run the login flow in a terminal
npm run build               # tsc --noEmit — type-check only (Yomi ships & runs from src/)
npm test                    # bun test

构建仅进行类型检查和编译;此仓库在自身构建过程中不会与实时 LINE 服务器通信。连接 MCP 客户端并调用 login 才是 真正开始会话的方式。

src/
  line/     LINE protocol core: TCompact/Thrift codec, E2EE (Letter-Sealing,
            group keys, media), Talk/Auth/Sync service clients, session state,
            passwordless login flow.
  auth/     Credential store (macOS Keychain, JSON-file fallback off-darwin).
  search/   Local cross-conversation index (SQLite + FTS5) and the offline
            embedding pipeline (transformers.js).
  mcp/      The stdio server: tool schemas, handlers, the privacy-policy loader,
            and the experimental MCP Apps login view (mcp/ui/).
  util/     [TAG]-prefixed logger (stderr only — stdout is the MCP JSON-RPC stream).

Yomi 写给人类的所有内容都输出到 stderr;stdout 保留给 MCP JSON-RPC 流。一个多余的 console.log 会破坏协议——不要在 服务器可达的任何路径上添加它。


隐私

默认情况下,Yomi 会将所有对话索引到本地、设备端搜索索引中,以便代理可以跨对话进行搜索——这是一种默认全量捕获、按聊天逐个选择退出的方式。任何内容都不会被上传;离开你设备的唯一数据就是代理本身在其回复中呈现的内容。(Yomi 自身发起的唯一非 LINE 网络调用是首次搜索时从 HuggingFace 一次性下载嵌入模型——只下载模型权重,不传出任何消息内容;参见搜索。)PRIVACY.md 是权威政策文档,Yomi 会在连接时(以及通过 get_scope_policy)向代理展示同一文本,以便代理在任何批量读取之前披露默认行为。


免责声明

Yomi 是一个独立的、非官方的个人项目,用于学习和访问自己的 LINE 账户。它与 LINE 公司无关联、未经授权、也未获认可。"LINE" 是其各自所有者的商标。

运行 Yomi 可能违反 LINE 的服务条款,在账户上运行额外的客户端可能导致该账户被限速或封禁。Yomi 旨在用于访问你自己的账户和数据。你需自行承担使用方式的责任。本软件按"原样"提供,不附带任何形式的担保——参见LICENSE。

致谢

Yomi 的 LINE 协议实现参考了三个开源项目编写,这些项目的字段布局、E2EE 块排序、请求结构和 Thrift 定义为本独立实现提供了参考:

  • evex-dev/linejs(MIT)——请求结构和 Letter-Sealing E2EE 载荷布局。

  • DeachSword/CHRLINE(BSD-3-Clause)——协议字段布局和无密码登录流程。

  • er1ce/LINE-Protocol(Apache-2.0)——Thrift 枚举定义(ContentType、MessageRelationType、ServiceCode)。

根据其许可证要求,其版权声明和完整许可证文本已在NOTICE中转载。

许可证

MIT

Available Tools

41 tools
accept_invitationA

Accepts a group/chat invitation for your LINE account — you join the chat. Use for a group you were invited to (its chatId appears with invited status). One accept per call.

NameRequiredDescriptionDefault
chatIdYesLINE group/room MID whose invitation to accept, as returned by list_conversations.
add_friendA

Adds a person to your LINE friends by their MID (e.g. from get_group_members or find_contact). One add per call.

NameRequiredDescriptionDefault
midYesMID of the person to add as a friend, e.g. from get_group_members.
block_contactA

Blocks a contact for your LINE account — they can no longer message you. Reversible with unblock_contact. One block per call.

NameRequiredDescriptionDefault
midYesMID of the contact to block.
cancel_reactionA

Removes this account's reaction from a LINE message. Undoes a react_message. One cancellation per call.

NameRequiredDescriptionDefault
messageIdYesLINE message id whose reaction to remove, as returned by get_chat_messages.
collect_messagesA

Bulk-fetch recent messages from LINE conversations into Yomi's local cross-conversation search index (LINE has no native cross-chat search). Fetches up to perChat per chat (default 100) for chatIds, or all conversations when omitted, and best-effort embeds them for semantic search — re-running also repairs any messages still missing a vector. A background capture loop keeps the index current on its own, so call this only to force a reconcile or backfill specific chats. Undecryptable messages are skipped, not fabricated.

NameRequiredDescriptionDefault
chatIdsNoLINE chat/group/room MIDs to collect from, as returned by list_conversations. Omit to collect from all conversations.
perChatNoMaximum recent messages to fetch per chat (default 100).
create_groupA

Creates a new LINE group/room immediately with the given members (no message is sent). chatType 0 = group (invitees must accept before joining), 1 = room (members added directly); default 1. Provide name and mids (initial members, e.g. from find_contact). One create per call.

NameRequiredDescriptionDefault
midsYesMIDs of the initial members to add.
nameYesName for the new group.
chatTypeNoLINE chat type: 0 = group (invite-based), 1 = room (direct add). Default 1.
exclude_chatsA

Add conversations to Yomi's privacy denylist. Excluded chats are (1) skipped by future collect_messages/search_messages auto-collect — never fetched or indexed — and (2) PURGED now: their already-indexed messages and embeddings are deleted from the local index in the same call. A real privacy action, not just a future filter. Local-index operation; works without a live LINE session.

NameRequiredDescriptionDefault
chatIdsYesLINE chat/group/room MIDs to exclude, as returned by list_conversations.
find_contactA

Find LINE friends whose display name contains name (case-insensitive substring). Returns each match's mid for send_message. Raw friend-list lookup — no ranking, no fuzzy scoring.

NameRequiredDescriptionDefault
nameYesSubstring to match against friends' display names, case-insensitive.
get_chat_messagesA

Fetch messages from one LINE conversation. Text is E2EE-decrypted when keys are available; each message has fromName (resolved sender), a mediaType flag (image/video/audio/file) plus messageId for get_message_media, and mentions (LINE's raw contentMetadata.MENTION, or null — a literal "@name" in text is not itself a mention). Without before, returns the most recent count. With before (id/deliveredTime of the oldest message already seen), returns one older page — repeat to page further back.

NameRequiredDescriptionDefault
countNoMaximum number of messages to return (default 50).
beforeNoCursor to fetch messages older than this point. Use the id and/or deliveredTime of the oldest message already seen.
chatIdYesLINE chat/group/room MID, as returned by list_conversations.
get_group_membersA

List the members of one LINE group (mid + displayName each). Resolves persistent groups (c...); ad-hoc rooms (r...) without a group record return an honest error, never a fabricated empty list.

NameRequiredDescriptionDefault
chatIdYesLINE group chat MID, as returned by list_conversations.
get_insightA

A compact "what needs my attention" context network over the local index — you make the final call, this assembles the evidence cheaply. Nodes: connectors (people across ≥2 of your chats, with structural bridges) and relationships (per-conversation engagement, reply rhythm, recency). open: conversations whose latest message is NOT yours, ranked by how overdue they are relative to your usual reply rhythm there, each with fromName (last speaker), a preview of the latest message, overdueRatio/typicality, and a lastMessageId pointer. It carries NO message threads and makes NO judgement about addressee, nicknames, or open-request vs closing-ack — those are language understanding you do by reading each preview (a group message may be addressed to someone else, who then owns it), fetching the full thread with get_chat_messages only for the few worth it. Reads across all conversations (denylist-excluded dropped). Empty only when the index is empty.

NameRequiredDescriptionDefault
chatIdNoOptional focus: restrict `relationships` and `pending` to this chat (as returned by list_conversations). Omit to scan all conversations.
sinceHoursNoLookback window in hours, measured back from the newest captured message (not wall-clock). Default 504 (21 days).
get_message_imageA

Download and decrypt one LINE image message. Legacy alias of get_message_media restricted to images; prefer get_message_media for video/audio/file.

NameRequiredDescriptionDefault
chatIdYesLINE chat/group/room MID the message belongs to. Required to locate E2EE key material.
previewNoFetch the smaller preview object instead of the full-resolution original.
messageIdYesLINE message id, as returned by get_chat_messages.
get_message_mediaA

Download and decrypt one LINE media message of any downloadable type (image, video, audio, file). Returns image/audio MCP content, or an embedded resource blob (with filename when known) for video/file. Non-media messages (text, sticker refs, unsupported types) return an honest error naming the content type — never fabricated bytes.

NameRequiredDescriptionDefault
chatIdYesLINE chat/group/room MID the message belongs to. Required to locate E2EE key material.
previewNoFetch the smaller preview object instead of the full-resolution original (images/video only).
messageIdYesLINE message id, as returned by get_chat_messages.
get_scope_policyA

Return Yomi's data-capture privacy policy (the disclosure to show the user) plus the current list of excluded conversations. Call this to show the user, in concrete terms, what Yomi captures by default and how to exclude conversations.

NameRequiredDescriptionDefault

No parameters

get_unread_digestA

One-shot unread digest: every LINE conversation with unread messages (all pages of the inbox, newest activity first), each with its most recent messages (default 10), E2EE-decrypted, with resolved sender names. Saves calling list_conversations then get_chat_messages per chat. Read-only: never marks anything read, never touches the search index; denylist-excluded conversations are omitted. Returns an empty list when nothing is unread — never fabricated.

NameRequiredDescriptionDefault
limitNoMaximum number of unread conversations to return, most recently active first (default: all of them).
perChatNoMaximum recent messages to include per unread conversation (default 10).
include_chatsA

Remove conversations from Yomi's denylist, re-allowing future capture. Does NOT restore data purged when the chat was excluded — capture resumes from empty history going forward. Local-index operation; works without a live LINE session.

NameRequiredDescriptionDefault
chatIdsYesLINE chat/group/room MIDs to re-include.
invite_memberA

Invites members into a LINE group immediately. Invitees must accept before joining. Provide mids (from find_contact or get_group_members). One call per invite batch.

NameRequiredDescriptionDefault
midsYesMIDs of the people to invite.
chatIdYesLINE group/room MID to invite into, as returned by list_conversations.
kick_memberA

Removes (kicks) members from a LINE group immediately — they lose access at once (re-adding needs a fresh invite); visible to every member. Provide mids (from get_group_members). One call per removal batch.

NameRequiredDescriptionDefault
midsYesMIDs of the members to remove.
chatIdYesLINE group/room MID to remove members from, as returned by list_conversations.
leave_groupA

Makes THIS LINE account leave a group immediately — it loses access to the group and its history. One leave per call.

NameRequiredDescriptionDefault
chatIdYesLINE group/room MID to leave, as returned by list_conversations.
list_contactsA

List the authenticated user's full LINE friend list as-is (mid + displayName). No ranking, no interaction-frequency ordering.

NameRequiredDescriptionDefault

No parameters

list_conversationsA

List LINE conversations (chats, groups, rooms) with unread counts, a preview of the last message, and a human-readable name (group title, or the other party's display name for a 1:1).

NameRequiredDescriptionDefault
limitNoMaximum number of conversations to return (default 20).
list_excluded_chatsA

List the conversations currently on Yomi's privacy denylist. Returns [{ chatId, name }]; name is best-effort resolved when a live LINE session exists, otherwise null — never a fabricated placeholder. Local-index operation; works without a live LINE session.

NameRequiredDescriptionDefault

No parameters

list_stickersA

List the sticker packages this LINE account OWNS — the only stickers it can send. Returns each package's packageId (STKPKGID), title, and version (STKVER). Get individual sticker ids via search_stickers, then send_sticker. Read-only.

NameRequiredDescriptionDefault
languageNoLocale for package titles, e.g. 'en' or 'zh-Hant'. Defaults to 'en'.
loginA

Log in to LINE via the passwordless secondary-device flow. Requires 設定 > 我的帳號 > 允許自其他裝置登入 enabled on the primary phone — with it off LINE never prompts that phone and NO login can succeed, so raise this with the human up front rather than after a failure. On MCP clients with form elicitation, this call first confirms that setting, then prompts for phone/region and PIN and completes login by itself; if the human says the setting is off, it returns the enabling steps without starting a login (relay them verbatim, then call login again). On clients without it (e.g. Claude Desktop), phone/region come from the arguments or a persisted login, and this returns as soon as LINE issues the PIN (or reports none needed) — then call login_complete IMMEDIATELY (do not wait for the human). LINE gives ~3 minutes from PIN display to confirm on the phone; login_complete blocks past that, so calling it late only wastes that window.

NameRequiredDescriptionDefault
phoneNoPhone number in E.164 form, e.g. +8869XXXXXXXX. Omit to be prompted (elicitation) or to reuse a persisted number.
regionNoRegion code, e.g. TW, JP, TH, ID, US. Omit to be prompted (elicitation) or to reuse a persisted region.
login_completeA

Finish a passwordless login that login started on a client without form elicitation (not needed on form-elicitation-capable clients). No arguments. Call immediately after login returns — do not wait for the human. Blocks while they enter the PIN (skipped if a stored certificate is valid) and approve the device, then returns the profile. LINE's real deadline is ~3 minutes from PIN display. Errors if no login is pending.

NameRequiredDescriptionDefault

No parameters

mark_readA

Send a LINE read receipt (mark a conversation read up to messageId, or the latest when omitted) — a real action the other party can see. Use ONLY when the user explicitly wants to mark a chat read; reading (get_chat_messages, get_unread_digest) and background capture never mark read. Fails honestly if there is nothing to mark.

NameRequiredDescriptionDefault
chatIdYesLINE chat/group/room MID to mark read, as returned by list_conversations.
messageIdNoOptional message id to mark read up to. Omit to mark read up to the latest message.
preview_stickerA

Show sticker preview images (MCP image content from the public sticker CDN) so you and the user can SEE them before sending. Give a packageId (from list_stickers/search_stickers) to preview its first stickers, or add a stickerId to preview just one. Each image is labeled with its stickerId + packageId for send_sticker. Read-only.

NameRequiredDescriptionDefault
limitNoMax stickers to preview when no stickerId is given (default 8).
packageIdYesSticker package id (STKPKGID) to preview.
stickerIdNoOptional specific sticker id (STKID) to preview just that sticker.
react_messageA

Adds a reaction to a LINE message, visible to the conversation. reactionType: 2 = 👍 LIKE, 3 = ❤️ LOVE, 4 = 😆 LAUGH, 5 = 😮 SURPRISE, 6 = 😢 SAD, 7 = 😡 ANGRY (default 2). One reaction per call.

NameRequiredDescriptionDefault
messageIdYesLINE message id to react to, as returned by get_chat_messages.
reactionTypeNoPredefined reaction: 2=👍LIKE, 3=❤️LOVE, 4=😆LAUGH, 5=😮SURPRISE, 6=😢SAD, 7=😡ANGRY. Default 2.
rename_groupA

Renames a LINE group/chat immediately; the new name is visible to every member. Works on groups/rooms (chatId starting with c/r). One rename per call.

NameRequiredDescriptionDefault
nameYesNew group name.
chatIdYesLINE group/room MID to rename, as returned by list_conversations.
search_messagesA

Search across your LINE messages. Hybrid ranking: FTS5 keyword search (covers every indexed message, so exact matches are never dropped) fused with semantic similarity when embeddings are available — the mode field reports which contributed (hybrid | semantic | keyword). If the index is empty and a session is live, it auto-collects all conversations first; a populated index searches locally with no network. Empty index with no session returns an honest notice, never a fabricated match list.

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default 20).
queryYesSearch query. Plain keywords and natural-language descriptions both work — keyword matching catches exact terms, semantic matching catches paraphrases.
search_stickersA

Search the account's OWNED sticker packages by title and expand each match into its individual sticker ids (STKID), ready for send_sticker. Case-insensitive substring match on the package title. Read-only.

NameRequiredDescriptionDefault
limitNoMax matching packages to expand with sticker ids (default 8).
queryYesSubstring to match against owned package titles (case-insensitive).
languageNoLocale for package titles to match against, e.g. 'en' or 'zh-Hant'. Defaults to 'en'.
send_audioA

Sends an E2EE audio message to a LINE conversation immediately (same pipeline as send_file). Provide exactly one of filePath or audioBase64; optional durationMs sets the recipient player length. Works for 1:1/group/room. One send per call.

NameRequiredDescriptionDefault
chatIdYesLINE chat/group/room MID to send to, as returned by list_conversations.
fileNameNoOptional original filename (used for the upload name; defaults to the basename of filePath or audio.m4a).
filePathNoLocal filesystem path to the audio file. Mutually exclusive with audioBase64.
durationMsNoOptional audio duration in milliseconds, for the recipient player progress bar.
audioBase64NoBase64-encoded audio bytes. Mutually exclusive with filePath.
send_contactA

Shares a LINE contact card to a conversation immediately — the recipient sees a tappable card for contactMid (e.g. from find_contact or get_group_members). displayName is optional (resolved from the mid when omitted). Works for 1:1/group/room. One send per call.

NameRequiredDescriptionDefault
chatIdYesLINE chat/group/room MID to send to, as returned by list_conversations.
contactMidYesMID of the person whose contact card to share, as returned by find_contact or get_group_members.
displayNameNoOptional display name for the card. Resolved from contactMid when omitted.
send_fileA

Sends an E2EE file attachment (any type — .docx, .pdf, .zip, …) to a LINE conversation immediately (same pipeline as send_image; the original filename is sealed end-to-end). Works for 1:1/group/room; fails honestly if the key cannot be resolved or the upload is rejected. One send per call. Provide exactly one of filePath or fileBase64; fileName is required with fileBase64 (and overrides the basename when given with filePath).

NameRequiredDescriptionDefault
chatIdYesLINE chat/group/room MID to send to, as returned by list_conversations.
fileNameNoOriginal filename shown to the recipient (sealed E2EE). Required with fileBase64; optional with filePath (defaults to its basename).
filePathNoLocal filesystem path to the file. Mutually exclusive with fileBase64.
fileBase64NoBase64-encoded file bytes. Mutually exclusive with filePath; requires fileName.
send_imageA

Sends an E2EE image to a LINE conversation immediately (encrypt → upload to OBS → send). Works for 1:1/group/room; fails honestly if the key cannot be resolved or the upload is rejected. One send per call. Provide exactly one of imagePath or imageBase64.

NameRequiredDescriptionDefault
chatIdYesLINE chat/group/room MID to send to, as returned by list_conversations.
imagePathNoLocal filesystem path to the image file. Mutually exclusive with imageBase64.
imageBase64NoBase64-encoded image bytes. Mutually exclusive with imagePath.
send_locationA

Sends a location (map pin) to a LINE conversation immediately — latitude/longitude plus optional title (place name) and address. Works for 1:1/group/room. One send per call.

NameRequiredDescriptionDefault
titleNoOptional place name shown on the pin.
chatIdYesLINE chat/group/room MID to send to, as returned by list_conversations.
addressNoOptional address shown under the pin.
latitudeYesLatitude in decimal degrees.
longitudeYesLongitude in decimal degrees.
send_messageA

Sends a text message to a LINE conversation immediately (not a draft). Always E2EE (pairwise for 1:1, group key for group/room); fails honestly rather than sending plaintext if the key cannot be resolved. One send per call. To @mention someone, put the visible "@name " into text AND pass a matching mentions entry — without mentions, "@name" is plain text and notifies no one. Resolve MIDs via get_group_members or find_contact first.

NameRequiredDescriptionDefault
textYesPlain-text message body, including the literal "@name" text for any mentions — mentions only mark up text that is already there.
chatIdYesLINE chat/group/room MID to send to, as returned by list_conversations.
mentionsNoOptional @mentions. Each entry marks a span of `text` as a mention of one user, which LINE highlights and notifies. Omit to send `text` as plain, non-notifying text.
replyToMessageIdNoOptional message id (from get_chat_messages) this replies to — LINE renders a quoted reply. Omit for a normal message.
send_stickerA

Sends a LINE sticker to a conversation immediately, named by stickerId (STKID) + packageId (STKPKGID). Only OWNED stickers can be sent — get ids from search_stickers/list_stickers. Works for 1:1/group/room. One send per call.

NameRequiredDescriptionDefault
chatIdYesLINE chat/group/room MID to send to, as returned by list_conversations.
versionNoSticker version (STKVER). Defaults to "1".
packageIdYesLINE sticker package id (STKPKGID).
stickerIdYesLINE sticker id (STKID).
send_videoA

Sends an E2EE video to a LINE conversation immediately (same pipeline as send_file; uses LINE chunked video encryption so it plays and integrity-verifies on official clients). Provide exactly one of filePath or videoBase64; optional durationMs sets the scrubber length. Works for 1:1/group/room. One send per call.

NameRequiredDescriptionDefault
chatIdYesLINE chat/group/room MID to send to, as returned by list_conversations.
fileNameNoOptional original filename (used for the upload name; defaults to the basename of filePath or video.mp4).
filePathNoLocal filesystem path to the video file. Mutually exclusive with videoBase64.
durationMsNoOptional video duration in milliseconds, for the recipient player scrubber.
videoBase64NoBase64-encoded video bytes. Mutually exclusive with filePath.
unblock_contactA

Unblocks a previously blocked contact for your LINE account. Undoes block_contact. One unblock per call.

NameRequiredDescriptionDefault
midYesMID of the contact to unblock.
unsend_messageA

Retracts (unsends) one of YOUR OWN LINE messages for everyone — deletes it from the conversation for all participants and CANNOT be undone. LINE allows unsending only your own messages. SAFETY GATE: you must pass confirm: true, or the call refuses so it can never fire by accident. One unsend per call.

NameRequiredDescriptionDefault
confirmYesMust be true to proceed. Retraction is irreversible; the call refuses unless this is explicitly true.
messageIdYesLINE message id to retract (must be your own), as returned by get_chat_messages.

Tool Schema Changelog

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

  1. 1 tool updatev0.6.2
    • Changedget_unread_digest1 field changed
      • changedInput schema / properties / limit / description
        Previous value: -"Maximum number of conversations to scan for unread (default 20)."New value: +"Maximum number of unread conversations to return, most recently active first (default: all of them)."
  2. 39 tool updatesv0.4.1
    • Addedaccept_invitation
    • Addedadd_friend
    • Addedcancel_reaction
    • Addedcollect_messages
    • Addedcreate_group
    • Addedexclude_chats
    • Addedfind_contact
    • Addedget_chat_messages
    • Addedget_group_members
    • Addedget_insight
    • Addedget_message_image
    • Addedget_message_media
    • Addedget_scope_policy
    • Addedget_unread_digest
    • Addedinclude_chats
    • Addedinvite_member
    • Addedkick_member
    • Addedleave_group
    • Addedlist_contacts
    • Addedlist_conversations
    • Addedlist_excluded_chats
    • Addedlist_stickers
    • Addedlogin_complete
    • Addedmark_read
    • Addedpreview_sticker
    • Addedreact_message
    • Addedrename_group
    • Addedsearch_messages
    • Addedsearch_stickers
    • Addedsend_audio
    • Addedsend_contact
    • Addedsend_file
    • Addedsend_image
    • Addedsend_location
    • Addedsend_message
    • Addedsend_sticker
    • Addedsend_video
    • Addedunblock_contact
    • Addedunsend_message
  3. 38 tool updatesv0.3.0
    • Removedaccept_invitation
    • Removedadd_friend
    • Removedcancel_reaction
    • Removedcollect_messages
    • Removedcreate_group
    • Removedexclude_chats
    • Removedfind_contact
    • Removedget_chat_messages
    • Removedget_group_members
    • Removedget_message_image
    • Removedget_message_media
    • Removedget_scope_policy
    • Removedget_unread_digest
    • Removedinclude_chats
    • Removedinvite_member
    • Removedkick_member
    • Removedleave_group
    • Removedlist_contacts
    • Removedlist_conversations
    • Removedlist_excluded_chats
    • Removedlist_stickers
    • Removedlogin_complete
    • Removedmark_read
    • Removedpreview_sticker
    • Removedreact_message
    • Removedrename_group
    • Removedsearch_messages
    • Removedsearch_stickers
    • Removedsend_audio
    • Removedsend_contact
    • Removedsend_file
    • Removedsend_image
    • Removedsend_location
    • Removedsend_message
    • Removedsend_sticker
    • Removedsend_video
    • Removedunblock_contact
    • Removedunsend_message
  4. 40 tool updatesv0.2.0
    • First observedaccept_invitation
    • First observedadd_friend
    • First observedblock_contact
    • First observedcancel_reaction
    • First observedcollect_messages
    • First observedcreate_group
    • First observedexclude_chats
    • First observedfind_contact
    • First observedget_chat_messages
    • First observedget_group_members
    • First observedget_message_image
    • First observedget_message_media
    • First observedget_scope_policy
    • First observedget_unread_digest
    • First observedinclude_chats
    • First observedinvite_member
    • First observedkick_member
    • First observedleave_group
    • First observedlist_contacts
    • First observedlist_conversations
    • First observedlist_excluded_chats
    • First observedlist_stickers
    • First observedlogin
    • First observedlogin_complete
    • First observedmark_read
    • First observedpreview_sticker
    • First observedreact_message
    • First observedrename_group
    • First observedsearch_messages
    • First observedsearch_stickers
    • First observedsend_audio
    • First observedsend_contact
    • First observedsend_file
    • First observedsend_image
    • First observedsend_location
    • First observedsend_message
    • First observedsend_sticker
    • First observedsend_video
    • First observedunblock_contact
    • First observedunsend_message

TDQS

A4.1/5.0

Scored across 41 tools

Disambiguation4/5

Most tools target a distinct resource+action, and descriptions actively disambiguate the tricky clusters (get_unread_digest vs list_conversations vs get_insight; find_contact vs list_contacts; search_stickers vs list_stickers). The only real overlaps are the explicitly-flagged legacy alias get_message_image vs get_message_media and collect_messages vs search_messages' auto-collect, both of which are documented so an agent won't misselect.

Naming Consistency5/5

Nearly every tool follows a clean snake_case verb_noun pattern (get_*, list_*, send_*, search_*, create_/rename_/invite_/kick_/leave_group, block_/unblock_contact). The send_* family, group-management family, and privacy family are each internally uniform. Only 'login' / 'login_complete' deviate slightly, which is negligible.

Tool Count3/5

41 tools is heavy and sits well above the comfortable 3-15 range, largely because seven distinct send_* variants (message/image/file/audio/video/location/contact/sticker) plus a full login pair inflate the surface. Each tool is genuinely distinct and earns its place in a rich LINE domain, but some consolidation (e.g. a single send_media with a type param) would be reasonable.

Completeness5/5

The surface covers the full lifecycle: auth (login/login_complete), conversation listing/search/digest/insight, message fetch and media download, all outbound message types, group CRUD and membership, contact add/block/find, reactions/unsend, stickers, and a complete privacy denylist lifecycle (exclude/include/list/policy). No obvious dead ends for the stated purpose.

Maintenance

ActivityNo data
ResponsivenessOutdated data

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI tools to read and send messages through LINE Desktop via MCP, supporting manual or automatic sending without official LINE API tokens.
    118 npm
    127
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI tools to read and send LINE messages by automating the LINE Desktop application, with macOS OCR-based reading and idle-aware scheduling.
    118 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants to read, search, and reply to personal LINE messages, including end-to-end-encrypted chats and media, all decrypted locally.
    MIT