Speak
A voiceover, from a sentence.
“Turn this welcome message into warm, natural speech and give me the audio.”
list_voices → synthesize_speech
PyAI × your AI app
Make something you can hear. Build an agent that can listen. Bring PyAI into ChatGPT, Claude, Cursor, Codex and Devin with one connection.
One URL. Browser sign-in. Your chosen project.
Your app. Your PyAI project.
Browser sign-inInstall PyAI, enable the server in Cursor, and complete the browser connection.
{
"mcpServers": {
"pyai": {
"url": "https://api.pyai.com/mcp"
}
}
}Sign in → select a project → approve access. Cursor setup reference
01 / Ask. Create. Keep going.
Start with the result you want. Your AI app discovers the tools, checks the inputs and works with your authorized PyAI project.
Speak
“Turn this welcome message into warm, natural speech and give me the audio.”
list_voices → synthesize_speech
Hear
“Transcribe this interview and help me find the key moments.”
transcribe_audio · transcription jobs
Agents
“Create a booking assistant with a greeting, clear boundaries and a human handoff.”
create_agent · tools · knowledge
Trace
“Find calls with missing disclosures and show the supporting evidence.”
interactions · findings · rule packs
Recap
“Summarize this sales call and extract objections and follow-up actions.”
create_recap → get_recap
Dub
“Dub this English recording into Hindi and give me the finished audio.”
capabilities → job → audio
Cast
“Turn this script into expressive narration. Preview a line before the full render.”
direct → preview → render
02 / A connection you control
Your app opens PyAI in the browser. Choose the project, review what the app can do, and connect.
OAuth keeps credentials out of your prompts and shared configuration. Your app receives access to the project you approve.
Use the hosted URL in chat apps. Prefer a local process? The npm server reuses your saved PyAI CLI login and profiles.
Typed tools, structured results, workflow recipes, readable errors and playable audio help your agent get useful work done.
03 / Give your agent a head start
Public Markdown, live tool discovery and the API contract give coding agents the details they need.
Use the connected PyAI MCP server.
Read get_started and check whoami.
Discover the tools for my use case before acting.
Use https://pyai.com/mcp-agent-guide.md for conventions.
Keep job IDs and return usable audio or transcripts.npx -y @pyai/mcp@latest login
# Then configure your host to launch:
npx -y @pyai/mcp@latestAlready ran pyai login? The MCP server uses that saved profile. Full local setup.
PyAI MCP connects AI apps to the PyAI voice APIs through typed tools. Use it to generate speech, transcribe audio, manage voice Agent profiles, review compliance, summarize calls, dub recordings and render directed narration.
The remote connection uses browser OAuth. Sign in to PyAI, select a project and approve the requested permissions. Your AI app receives a scoped connection; your PyAI API key stays on the server.
An existing signed-in user can go straight to project consent. Setup time also depends on your app, account and workspace policy. A new account or an administrator approval can take longer.
Use a custom app or connector to add PyAI by URL. Public app-directory listings require separate submission and review. Your host’s plan and workspace policies determine whether custom connections and write tools are available.
MCP can create and configure reusable voice Agent profiles. Live microphone and telephone conversations run through the PyAI SDK, widget or telephony integration. Creating a profile does not place a call.
PyAI updates the hosted endpoint through its deployment process. Local @pyai/mcp installations have their own package releases and need restarting after an upgrade. The CLI ships in @pyai/sdk; installed versions do not silently upgrade when a new SDK is released.
Open Connected AI apps in the PyAI console and revoke the connection. Access lasts up to 30 days and also stops when the authorizing user loses project access. Revocation stops new requests; already-submitted jobs may continue.
The MCP connection uses your project’s normal PyAI credits, product pricing and limits. Generated audio, transcription, dubbing and other processing consume usage. Reading the in-server setup guide and workflow recipes does not consume model credits.