技能 效率工具 Cherry 工具路由指南

Cherry 工具路由指南

v20261028
cherry-tool-guide
Cherry Studio 一方 MCP 工具的路由指南,涵盖知识库、记忆、定时任务、会话、技能库、MCP 服务器、联网搜索及内置 bun/uv/rg 运行时,指导在尝试 shell 绕行前先查阅对应参考文档。
获取技能
54 次下载
概览

Cherry Tool Guide

Cherry Studio injects first-party tools into your session over four MCP servers
(mcp__cherry-tools__*, mcp__agent-memory__*, mcp__skills__*, mcp__mcp-manager__*)
and gives shell-capable general agents bundled runtimes for local execution. The MCP
tools act on the running app — the user's knowledge bases, IM channels, schedules,
managed CLIs, skill library, and MCP server registry — through boundaries only Cherry
owns. Shell and file tools cannot reach those app boundaries correctly; use the bundled
runtimes only for the local execution cases routed below.

This file is a router. It carries only the global rules and the intent → tool →
reference table. Each reference holds that domain's prerequisites, sequencing,
conditional availability, output interpretation, recovery, and examples. Read the one
reference the task needs (and any it cross-links to) before calling — don't work from
this page alone.

Tool names here are fully qualified (mcp__server__tool); the exact names exposed in
your session are authoritative if they ever differ. This guide never restates argument
shapes — the live tool schema in your session is the authoritative source for
parameter names, enums, and required fields. Read it before every call.

Global rules

  • Check availability first. Several tools are conditional (each reference says

which). If a tool is not in your live tool list, its capability is unavailable *in
this session* — say so honestly and stop; never pretend a call succeeded or fabricate
a result.

  • Don't reach around Cherry's mutation boundaries. Knowledge bases, IM channels,

schedules, managed CLIs, skills, and registered MCP servers are mutated only through
these tools. Do not shell out to npm install, git clone, crontab, or hand-edit
knowledge or MCP settings files to accomplish these — the tool does bookkeeping (registration, scoping, approval, sync)
that a raw shell command skips. Shell is fine for inspection (e.g. command -v to
probe PATH) — just not to perform the owned mutation.

  • Honor approval. mcp__cherry-tools__kb_manage, mcp__cherry-tools__cli_install,

mcp__cherry-tools__session_create, mcp__cherry-tools__session_send,
mcp__skills__install_skill, and mcp__mcp-manager__install_mcp_server are gated by
the session's approval mode. Call them only once the user's intent is clear; if approval is
declined, stop and report — do not retry the same effect through another route.

  • Intent still gates auto-approved effects. Memory writes, schedule changes,

notifications, Session renames, and agent/channel configuration may execute without an approval card.
Do not call them merely because they are available; first make sure the user requested
the effect or it is necessary to complete an already-approved task.

Routing table

User intentRoute toReference
Look up current/online facts, news, docsmcp__cherry-tools__web_search → mcp__cherry-tools__web_fetchweb.md
Browser interaction (click, forms, screenshots)Automation REPL when Browser is enabled; load cherry-browserweb.md
Native desktop applications (open, type, click, screenshots)Automation REPL when Computer Use is enabled; load cherry-computerautomation.md
Answer from the user's own documentsmcp__cherry-tools__kb_list → mcp__cherry-tools__kb_search → mcp__cherry-tools__kb_readknowledge.md
Add / delete / re-index knowledgemcp__cherry-tools__kb_manage (resolve IDs first; needs approval)knowledge.md
Read or convert a local documentmcp__cherry-tools__to_markdown → read the returned temporary Markdown path as neededdocuments.md
Recall a past fact, correction, or preferencemcp__agent-memory__memory (search) before re-askingmemory.md
Save durable knowledge vs. a one-off eventmcp__agent-memory__memory (update vs. append)memory.md
Schedule a recurring / future taskmcp__cherry-tools__cron (Cherry scheduling only)autonomy.md
Proactively message the user or send a filemcp__cherry-tools__notify (needs configured recipients)autonomy.md
Inspect / connect / repair IM channels, rename agentmcp__cherry-tools__configautonomy.md
Rename the current or another Agent Sessionmcp__cherry-tools__session_renamesessions.md
Find, create, message, or inspect work across Agent Sessionsmcp__cherry-tools__session_list / session_search / session_create / session_send / session_deliveriessessions.md
Generate an imagemcp__cherry-tools__generate_image (needs a painting model)outputs.md
Declare final deliverable file(s)mcp__cherry-tools__report_artifactsoutputs.md
Run JS/TS or Python, invoke a one-off package, search local code/filesbundled bun, uv / uvx, or rg according to task lifetimecli.md
Find / install a command-line toolcommand -v check → mcp__cherry-tools__cli_list → mcp__cherry-tools__cli_search → mcp__cherry-tools__cli_install (approval)cli.md
Find / install a new capability skillmcp__skills__search_skills → mcp__skills__install_skill (approval)skills.md
Register a new MCP server the user suppliedmcp__mcp-manager__install_mcp_server (approval; never invent the config)mcp.md

When a tool isn't there

Two different situations, don't confuse them:

  • The tool is absent from your live list → the capability is unavailable this

session (e.g. no knowledge base in scope, or CLI management disabled for a shell-less
agent). Explain what's missing and what the user can do; don't work around it with
shell/file tools. The reference for that domain says exactly when it can be absent.

  • The tool is listed but reports a missing dependency → e.g.

mcp__cherry-tools__generate_image with no painting model. It stays listed and
returns a note; relay the note and point the user at configuration — don't retry
blindly or fake success.

On any tool error result (bad ID, unsupported channel/file, invalid recipe), read
the message and correct the call; don't silently retry the same arguments. On **declined
approval**, stop and report — never re-attempt the mutation through a different route.

Out of scope

Not covered here: SDK-native Read/Edit/Bash and orchestration tools; calling the
tools of a third-party (user-configured) MCP server — only registering one is in scope,
see mcp.md; the AI-SDK chat read_file attachment reader (a
chat-path tool, not exposed on this MCP surface); and the role-specific
mcp__assistant__* navigation/diagnosis tools, which belong to the Cherry Assistant and
its own guide.

信息
分类 效率工具
名称 cherry-tool-guide
版本 v20261028
大小 20.22KB
更新时间 2026-10-28
语言