https://mcp.percify.io/mcp to Claude, ChatGPT, Cursor, Claude Code or Codex, and the assistant can price and run image, video and voice models, make an avatar speak a script, and wait for the result. Claude signs in to your Percify account with OAuth; clients without a browser sign-in send a Percify API key.
Server details
Connections set up with the earlier URL
https://api.percify.io/v3/mcp keep working.
Which sign-in should I use?
Which plan you need depends on how your client signs in. Connecting over OAuth works on every plan, including the free one: you sign in to Percify in the browser, click Authorize, and the assistant spends credits from your balance like the app does. A client that cannot open a browser needs an API key instead, and keys are created on the developer page on the Scale and Ultra plans. Credits themselves are pay as you go: a one-time pack needs no subscription and never expires. See Authentication.
What it costs to start
Three facts, because they are usually assumed to be one:
So an agent can be talking to Percify on a free account in two clicks, with no card and no subscription. Credits are pay as you go: packs start at 200 credits for $5, need no plan, and never expire — buy them when you need them and they sit on the account until you spend them. A subscription only changes how many credits arrive each month; it is not what unlocks the server.
Add Percify to your client
- Claude
- ChatGPT
- Claude Code
- Cursor
- Codex CLI
These steps follow Claude’s custom connector guide for individual Free, Pro and Max plans. Free plans can add one custom connector.On Team and Enterprise plans, an Owner first adds the connector under Organization settings > Connectors; members then click Connect in Customize > Connectors.
1
Add the connector
In Claude, go to Customize > Connectors, click +, then Add custom connector. Paste
https://mcp.percify.io/mcp as the remote MCP server URL and click Add. Leave the OAuth client fields in advanced settings empty.2
Connect and sign in
Click Connect. A Percify sign-in page opens. Sign in, and on the screen that asks you to allow the connection, click Authorize.
3
Use it in a chat
Turn the connector on for a conversation with the + button at the lower left of the chat, then Connectors. Then ask, for example: “What would a 10 second lip-sync video cost with Percify?”
https://mcp.percify.io/mcp and send Authorization: Bearer pk_live_… on every request.
What tools does the Percify MCP server have?
Read-only tools are marked read-only in their MCP annotations, so clients can approve them without asking. Tools that spend credits are not.Models and generations
Avatar personas
Attaching a voice with
create_avatar requires voiceConsent: true, which only you can confirm. The assistant should ask you before setting it.
Short videos
Video replication
Batches
A batch takes a
budgetCredits ceiling, enforced before each submission rather than reported afterwards. The same thing over REST is POST /v1/batches.
Avatar persona images
Speaking avatars
Composer rounds and Library
The same rounds the app’s Plays tab deals: three cards, face down. Actions taken here are logged as an agent’s, not a person’s.
The same loop over REST is the Composer API.
Brand OS
Reading a brand, writing its words into a proven short video format, rendering it and publishing it. Requires a brand on the account.Other
How the tools behave
- Asynchronous. Spending tools return an id right away. The assistant then calls
wait_for_generationorwait_for_job, which return when the job ends or after about 45 seconds withstillRunning: true. - No double charges on retry.
generate,avatar_say,analyze_video,replicate_videoandmake_videoaccept anidempotencyKey; a repeat call with the same key returns the original job. - Refunds. Failed generations return their credits, as in the REST API.
- Errors are JSON with a code. A failed tool call returns
isError: trueand a body such as{"code": "INSUFFICIENT_CREDITS", "message": "…", "requiredCredits": 44, "currentCredits": 12, "topUpUrl": "https://app.percify.io/billing"}. Codes:INSUFFICIENT_CREDITS,MODERATION_REJECTED,CONSENT_REQUIRED,NAME_TAKEN,NOT_FOUND,RATE_LIMITED,TIMEOUT,INVALID_INPUT,INTERNAL. - Rate limits. 60 requests a minute per API key or OAuth token, and 60 generation starts a minute per account. See Errors and rate limits.
Troubleshooting
Opening the URL in a browser shows a web page, not the server
Opening the URL in a browser shows a web page, not the server
That is expected. A browser visit to
https://mcp.percify.io/mcp is sent to the setup page on percify.io. MCP clients use POST requests, which reach the server.A GET request returns 405
A GET request returns 405
The server only answers
POST. It does not offer a server-sent event stream, so a 405 on GET is the expected answer.The assistant says there are not enough credits
The assistant says there are not enough credits
The tool error includes the credits needed and your balance. Top up at app.percify.io/billing, or ask the assistant to run
estimate_cost first.Disconnect
Remove the Percify connector in your client’s connector settings. For clients that use a key, revoke the key on the developer page; it stops working at once.For client developers
- OAuth protected resource metadata: mcp.percify.io/.well-known/oauth-protected-resource. The authorization server is
https://api.percify.io, with dynamic client registration and PKCES256. - Agent registration guide: api.percify.io/auth.md.
- The server accepts cross-origin requests from any origin and exposes the
WWW-Authenticateheader, so browser-based MCP clients can sign in.
Related
API overview
The REST API behind the same tools.
Authentication
Create the pk_live key for Claude Code, Cursor and Codex.
Talking avatar pipeline
What avatar_say does, step by step.
Credits and usage
Balance, spend and key caps.