Plugins and external tools

Plugins let an agent access other services within your authorization, such as reading Feishu documents, organizing Notion pages, or finding routes with Amap.

The model interprets the task; the plugin accesses the service. Select a text model supporting tool calling first.

Connect and use a plugin

Open Plugins in the sidebar and select a service.
Read its capabilities, examples, and permissions, then tap Connect.
Complete the account authorization or enter the required service key.
Return to Cherry Studio and confirm the account/workspace if requested, until it shows Connected.
Give a specific request in chat. Optionally use ＋ → Plugins to insert the target plugin, then add your question.

For example: “Use Feishu to summarize three conclusions from this document: [link].” The inserted name appears in the composer and sent message.

Connected plugins work across agents without separate authorization for each. Composer selection makes the intended service explicit. The ＋ → Plugins option in the chat composer is hidden when no usable plugin is connected.

iPhone · Choose a service from the plugin list

iPhone · Read capabilities, examples, and authorization details before connecting

Common connections

Plugin	Useful for	Connection notes
Feishu	Documents, Base tables, tasks, calendars	Set up a Feishu application and authorize your account; organization approval may be required. This connection currently supports Feishu accounts, not international Lark accounts
Notion	Find/read/edit pages and database records	Authorize a workspace and confirm the account; workspace permissions still apply
GitHub	Read repositories/discussions and manage issues/pull requests	Use app authorization or a personal access token; organization access may need approval
Amap	Places, nearby services, weather, routes	Use a Web Service Key from Amap's platform; route queries do not automatically read device location
DingTalk	Documents, calendar, tasks, other office operations	Authorize an account and organization; some actions require further authorization
WeCom	Authorized documents, spreadsheets, schedules, other office data	Paste the generated authorization link into WeCom's File Transfer Assistant and open it there, then return to Cherry Studio

A listed capability is not a promise of account access. Plans, organization settings, resource permissions, and quotas determine what your account can use.

Preparing Feishu

The “application” in this flow is a Feishu authorization configuration, not another phone app to install. Follow the connection page's Configure application or setup-guide link. If using an existing application, enter its App ID and App Secret, enable the permissions needed for documents/tasks/calendar, then authorize your personal account.

Partial grants can still produce a usable connection. To add capabilities later, enable the corresponding application permissions, complete organization approval, and update authorization. Reconnecting alone does not grant missing permissions.

Additional DingTalk approval

Complete the requested action authorization in DingTalk, then return and request the operation again. Authorization does not automatically replay the failed action.

Expired WeCom link

Links last five minutes. Generate a new link and open it inside WeCom, rather than only in an ordinary browser.

What can I do after connecting?

Start with a read. Replace the bracketed text with your links, names, or dates, then check the sources and coverage of the result.

Plugin	Adaptable request	What to check
Feishu	“Read this document: [link]. List conclusions, tasks, owners, and deadlines. Mark missing information as unconfirmed; do not create tasks yet.”	Whether owners and dates are explicit; task creation is a separate next step
Notion	“Read this page: [link]. Summarize recent project progress and retain source links.”	Workspace access and whether relevant page content was fully read
GitHub	“Read the last week's issue discussions in [repository URL], group them by topic, and include links.”	Repository visibility, date range, and whether discussion conclusions are confirmed
Amap	“Compare public transport from [city and starting point] to [destination], including walking, transfers, and estimated duration.”	City and address for duplicate place names; estimates are not live departure times
DingTalk	“Read this document: [link] and summarize material about [topic]. Do not edit it.”	Organization and document access, plus any further authorization in DingTalk
WeCom	“Read this document: [link]. Summarize three key conclusions with sources, without editing.”	The authorized account's access and tools actually available on the connection

Turn document notes into saved tasks

For example, use two requests with Feishu:

“Read these meeting notes: [link]. List proposed tasks, owners, and deadlines, but do not create them.”
After checking: “Create only items 1 and 2 as Feishu tasks with the owners and dates we confirmed. Return the results and links.”

Document reading, people lookup, and task creation must all be available where needed. Resolve duplicate names and unclear dates first. A task table in the chat is not proof that tasks were saved. Assignment and invitations may also notify other people.

Read and update Base tables or databases

Provide the table link and view, then state the filter: “Read only records with status In progress in this view. List names and deadlines without making changes.” A project may have several tables or views with similar names.

Before editing, identify the exact record and field. Ask the agent to state coverage when results have pagination or limits; one query is not necessarily the whole database. The current Notion connection does not provide attachment handling or access to Notion agents.

Can tools work together?

Available connected tools can cooperate in one task—for example, reading a document and saving a checklist file. When copying material between services, specify the destination and exact content, then check each result. Success in one step does not automatically roll back if another fails.

For approval, result checks, and failure handling, see Let AI Use Tools.

I closed authorization, but it is not connected

Closing a browser neither cancels authorization nor proves connection succeeded. Return to the connection page, use Open authorization page or Check again if needed, and finish account confirmation.

Restart expired or denied requests. To switch accounts, follow the instruction to disconnect the existing account first.

Disconnect and revoke

Use connection management or the detail menu to Disconnect. That removes local access.

If remote revocation is unconfirmed, use Manage authorization on the provider website. Local removal and provider-side revocation do not always finish together.

Plugin credentials stay on this device and are not transferred by desktop configuration import; another phone needs a separate connection. Retrieved content may be used by the model. See data and privacy.

Add a custom MCP service

MCP connects an agent to additional tool services. Use this when you already have a remote tool-server address; built-in plugins are simpler when they meet your needs.

Open Settings → MCP → Add server.
Enter the supplied server address, preferably https://.
If authentication is required, fill Headers with one Name=Value entry per line, such as Authorization=Bearer your-token, using the service's instructions.
Save, wait for connection, and inspect the Tools list. Disable unwanted tools.
Enable the corresponding server in the target agent’s editor, then send a new request. If the agent is new, save it first and reopen its editor to configure tools.

The server must be connected and enabled, the tool enabled globally, and the corresponding server enabled for the agent. Automatic approval bypasses none of those requirements.

This field accepts remote addresses, not desktop startup commands such as npx or uvx. iOS can block plain http://; prefer the service's secure address.

A connected plugin still cannot do the task

Check connection status and model tool-calling support. Provide the target link/name/date range. Permission errors need repair at the service, not changes to agent instructions.

For writes, first ask it to read and list the proposed changes. Whether execution asks for confirmation depends on tool approval.