Skip to content
9 min read

Connect AutoWhisper from Your Phone: First Check Whether the App Supports Custom MCP

The short version: MCP works on a phone, but only if the app has an Add custom MCP / Add MCP server entry. Without that entry, no tutorial will make it work. As of November 2026, the major mainland-China assistant apps — Doubao, Kimi, Tencent Yuanbao, Tongyi Qianwen, Wenxin/Wenxiaoyan and Zhipu Qingyan — do not let users add a custom MCP server, and neither does the ChatGPT mobile app. Most users in mainland China should use the official account → external browser path; overseas users can use ChatGPT desktop/web; third-party mobile clients (Kelivo, RikkaHub, Cherry Studio) are for technical users willing to configure a model API.

Choose your path first

There is more than one way to use AutoWhisper on a phone, and the simplest one is not a third-party app:

  • Most users in mainland China: do not install anything. Tap 开始使用 (Start using) in the WeChat official account and copy the website into Safari or Chrome. Follow the phone browser guide for sign-in, uploads and downloads.
  • Overseas users / existing ChatGPT users: add AutoWhisper MCP in the ChatGPT desktop or web app under Connectors / Plugins. The ChatGPT mobile app cannot add custom MCP today, so on a phone, use the web.
  • Technical users who want a third-party agent on the phone: continue with Cherry Studio, Kelivo or RikkaHub below. They require a model API key before MCP; if you do not want to configure one, use the web.

The technical steps below are for the third group.

The gap between phone and desktop is not screen size. It is whether the client exposes the entry point. The same AutoWhisper URL takes one command in Claude Code and has no button at all in most mobile assistant apps. So confirm that first, then worry about the fields.

First: does your app have the entry?

Open the app’s settings and look for MCP, MCP servers, connectors, tools or extensions.

  • An Add custom / Add server entry → keep going.
  • Built-in tools only, no way to add one → this build does not support it. Use another client.
  • No MCP-related word anywhere → same answer. Do not keep trying in the chat.

This check is more reliable than any screenshot. Client updates move and rename these entries; this page documents the fields and flow, and the app’s own UI is the source of truth.

Third-party mobile clients (technical users)

If you do not want to configure a model API, stop here and use your phone browser.

App System How to add Auth Notes
Kelivo iOS / Android (HarmonyOS is on the roadmap) Settings → MCP / tools / connectors → Add server OAuth Per-tool approval; try this first
RikkaHub Android Settings → MCP / tools → Add remote server OAuth 2.1; custom headers also supported Per-tool approval; a good Android option
Cherry Studio Mobile iOS / Android (check the official release for your build) Sidebar → Plugins → MCP → Custom OAuth / headers Remote MCP only (SSE / Streamable HTTP); on first use, enable autowhisper under the Standard-mode agent’s Tools / MCP
Manus Mobile app (version and region dependent) Custom MCP connector Follow the app Availability depends on version and region
Nano AI (360) iOS / Android / HarmonyOS Desktop client / some builds expose MCP; the current mobile app may not Headers (if the entry exists) Do not treat mobile as the default; check the app
Doubao, Kimi, Tencent Yuanbao, Tongyi Qianwen, Wenxin/Wenxiaoyan, Zhipu Qingyan iOS / Android No user-added custom MCP — The big assistant apps cannot do this today
ChatGPT mobile app iOS / Android No custom MCP — Custom MCP / developer mode is web or desktop only

If the entry in the table is missing on your phone, the URL is not the problem — that build does not expose this layer. Switching apps is faster than hunting for a hidden switch.

One prerequisite is easy to miss: Kelivo, RikkaHub and Cherry Studio are bring-your-own-model clients. They do not chat out of the box. After installing, add a model API before adding MCP; otherwise you will have an MCP server but no model to talk to. You can start with Qumge (OpenAI-compatible and reachable from mainland China; it is a separate product, billed separately from AutoWhisper credits), or use your own DeepSeek, Kimi, OpenAI or Gemini key. The full Cherry Studio walkthrough is here.

What to fill in

Remote MCP uses the same fields in Kelivo, RikkaHub and Cherry Studio Mobile:

Field Value
Name autowhisper
Type / transport Streamable HTTP (some clients call it HTTP / Remote MCP; do not choose STDIO)
Server URL https://autowhisper.xyz/mcp
Auth OAuth first; if the app only accepts headers, use Authorization: Bearer <API token>

Stop the URL at /mcp, with no trailing slash. https://autowhisper.xyz/skill is the install instruction for command-capable assistants, not the MCP server address.

Walkthrough with Kelivo

  1. Update Kelivo, open MCP / tools / connectors in settings, and choose to add a remote MCP server.
  2. Name it autowhisper, choose Streamable HTTP, and enter https://autowhisper.xyz/mcp.
  3. Save. If the app opens a browser, sign in to AutoWhisper and click Approve. That is OAuth; you do not copy a token.
  4. Back in the app, make sure autowhisper is enabled and tool calls / per-tool approval are on.
  5. Run the read-only check below. Real account data means it is connected.

The same fields work in RikkaHub on Android. RikkaHub also supports custom headers in the server settings; if it does not start OAuth, use the device-code flow below. Cherry Studio Mobile is under Sidebar → Plugins → MCP group → Custom. The mobile build supports remote MCP only (SSE / Streamable HTTP), with OAuth or headers. After connecting, enable autowhisper under the Standard-mode agent’s Tools / MCP, or it will not appear in the tool list. The full walkthrough from model API to MCP is in the Cherry Studio setup guide. Manus depends on the version and region.

About Nano AI

Nano AI (360) exposes an MCP entry in its desktop client and some builds; the currently installed mobile app does not show an MCP servers / MCP management option. Do not assume that a desktop tutorial means the phone build has it too. Only if you actually see MCP services → Add custom on your phone should you fill in the fields above; otherwise use Kelivo, RikkaHub or Cherry Studio Mobile. Check the app itself.

Auth: OAuth first; device code only for header-only clients

Add https://autowhisper.xyz/mcp, save, and let the client open AutoWhisper’s approval page. Sign in, check the requesting app, and click Approve. The tool list appears when you return.

Nothing is copied, and no token goes into a chat. Kelivo, RikkaHub and some builds of Cherry Studio Mobile support this path.

Option 2: a device-code API token

Some clients only support request headers. Use the device-code flow and approve from a browser:

curl -X POST https://autowhisper.xyz/device/code \
  -H "Content-Type: application/json" \
  -d '{"device_name":"My phone"}'

The response contains device_code, user_code, verification_uri, verification_uri_complete, expires_in and interval. Open verification_uri_complete, sign in, and click Approve.

Then poll every interval seconds:

curl -X POST https://autowhisper.xyz/device/token \
  -H "Content-Type: application/json" \
  -d '{"device_code":"the device_code from the previous step"}'
  • authorization_pending: not approved yet; keep waiting.
  • slow_down: poll more slowly.
  • access_denied or expired_token: start over with a new device code.
  • Success returns access_token and token_type. Put access_token in the client’s Authorization: Bearer <token> header.

This token carries your account’s API permissions. Enter it only in a client you trust — never paste it into a chat, note or screenshot. AutoWhisper’s settings page deliberately does not display the token; when you need a new one, run the device-code flow again.

To cut everything off at once: Settings → Connect your agent → Disconnect. It clears the account’s API token, so every agent, connector and command-line tool stops working — not only this phone. You must approve again to reconnect.

Check it with a read-only prompt

Do not start by generating or publishing. Paste this first:

Call AutoWhisper and list my workspace names and IDs, my current workspace and credit balance. Read only — do not generate or publish anything.

Real workspace names, IDs and a balance mean it is connected. If it only says “I can help with that”, or the tool list is empty, go to the next section.

Troubleshooting

401 / Unauthorized. The handshake did not include an Authorization header, or the token is no longer valid. Re-approve with OAuth, or run the device-code flow again for a header-based client. After Disconnect, the old token is invalid immediately and every client must reconnect.

tools/list is empty. Usually the client has not allowed tool calls, or OAuth only half-finished. In the app’s server settings, confirm autowhisper is enabled and tool calls / per-tool approval are on, then start a new conversation.

SSE or Streamable HTTP? Choose Streamable HTTP. SSE is the older streaming transport. If the client only offers SSE and no Streamable HTTP, switch to Kelivo, RikkaHub or Cherry Studio Mobile.

Trailing slash? No. Use exactly https://autowhisper.xyz/mcp, not /mcp/.

OAuth dynamic client registration (DCR) fails. Some clients do not support dynamic registration, so OAuth cannot complete. Update the app first; if it still fails, use a client that supports DCR, or use a header-capable client with the device-code flow. Do not paste someone else’s Client ID or Secret.

The client cannot set custom headers. Prefer an OAuth client (Kelivo, RikkaHub, some builds of Cherry Studio Mobile). If it is header-only and has no OAuth, it must at least support Authorization. If it supports neither, change apps.

Can the ChatGPT mobile app connect? No. Custom MCP / developer mode is currently web or desktop only. The big mainland-China assistants (Doubao, Kimi, Tencent Yuanbao, Tongyi Qianwen, Wenxin/Wenxiaoyan, Zhipu Qingyan) also do not support user-added custom MCP.

Nano AI’s mobile app has no MCP management. The current mobile build may not expose it; the desktop client and some builds do. On a phone, use Kelivo, RikkaHub or Cherry Studio Mobile, or wait for an update. Check the app itself.

Start now

Open Settings → Connect your agent, copy https://autowhisper.xyz/mcp, and add it to a mobile client using the fields above. Run the read-only check before you let it make content.

For what to do after connecting — platform connections and a first post — read One MCP Server for a Dozen Platforms. For the difference between MCP, Skills and client types, read MCP vs. Skill.

Ready to start?

Create your first product, let AI CMO generate your content plan. 15 minutes to get started.