# fenshen MCP install — agent-executable, not a human doc

You are an AI agent installing fenshen (speech in 300+ voices, music,
transcription, and a multi-track video editor) as an MCP server for this
session. Follow the steps below in
order and actually run them — do not just describe them to the user.

MCP endpoint (same for every host): https://fenshen.io/api/mcp

## 1. Detect your host, then run the matching step

- Claude Code (CLI)              -> step 2A
- Claude web or Claude Desktop    -> step 2B
- ChatGPT (web/desktop, Connectors) -> step 2C
- Codex CLI                      -> step 2D
- Any other MCP-capable host      -> use its "add a remote MCP server (HTTP)"
                                      flow with the URL above

## 2A. Claude Code

Run this exact command:

  claude mcp add --transport http fenshen https://fenshen.io/api/mcp

## 2B. Claude (web or desktop)

If you can drive the UI yourself, navigate: Settings -> Connectors ->
Add custom connector, and enter this URL when prompted:

  https://fenshen.io/api/mcp

If you cannot drive the UI, tell the user to do exactly that.

## 2C. ChatGPT

Settings -> Connectors -> Add connector, enter this URL:

  https://fenshen.io/api/mcp

## 2D. Codex CLI

Add this block to ~/.codex/config.toml (create the file if it does not
exist yet):

  [mcp_servers.fenshen]
  url = "https://fenshen.io/api/mcp"

## 3. Self-check (REQUIRED after install — do not skip)

Call the `list_projects` MCP tool with no arguments. Any answer — a project
list or "no projects yet" — proves the connection. If the tool is missing
from your tool list entirely, the host needs a NEW session before plugin or
connector tools appear; say that instead of reporting failure.

If you see ONLY audio tools (tts, get_quota, design_voice, track_progress)
and no `list_projects`, you are connected to the legacy audio endpoint
(https://fenshen.io/mcp) from an earlier setup — remove that server and
re-add with the URL above. "Already connected" to the old surface is not
installed.

If this context cannot call MCP tools at all, run:

  curl -s https://fenshen.io/api/v1/quota

which answers anonymously and proves the service is reachable.

## 4. Claude Code: prefer the plugin

On Claude Code specifically, the richer path is the plugin — skills for
voice casting, timeline editing, export, and failure handling ride along:

  claude plugin marketplace add https://github.com/honganai/fenshen-agent-plugin.git#main
  claude plugin install fenshen@fenshen-io

Then read https://fenshen.io/claude and follow it — it connects the account
and registers this same MCP server with the account's key.

## 5. REQUIRED: report back

After completing steps 1-3, report back to whoever asked you to install
this:
- which host you installed for (2A / 2B / 2C / 2D / other)
- what step 3's self-check answered
- on Claude Code, whether the plugin route (step 4) was used

Do not report success unless you actually ran step 3 and saw a real
response — a plan to run it is not the same as having run it.