Media · Remote MCP server
PyAI Voice AI
Speech, transcription, voice agents, Trace, Recap, dubbing and narration with browser OAuth.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.atomsai/pyai- Version
- 0.3.3
- Status
- Active
- Category
- media
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-09
- Updated
- 2026-09-09
- Publisher
- atomsai (GitHub) · 2 servers with pages here
- Listed under
- Browser automation MCP servers
- Website
- pyai.com/mcp
- Repository
- github.com/atomsai/pyai-platform-backend (folder mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.pyai.com/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @pyai/mcp | 0.3.3 | stdio |
How to connect PyAI Voice AI
PyAI Voice AI is a remote MCP server: there is nothing to install. Its endpoint is https://api.pyai.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @pyai/mcp version 0.3.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @pyai/mcp@0.3.3.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pyai": {
"command": "npx",
"args": [
"-y",
"@pyai/mcp@0.3.3"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from atomsai (GitHub)
| Server | Runs |
|---|---|
| ContextDB Customer MemoryCustomer memory with recall, confirmation, forgetting, and pre-action evidence checks. | Remote · HTTP |
More media servers
| Server | Runs |
|---|---|
| puppetry.comTurn a portrait photo and a script into a talking-head AI video via the Puppetry API. | Local · stdio |
| Pure Report — Neutral NewsNeutral, bias-scored news for AI agents: compare left/right media-bias framing, fact-check receipts. | Remote · HTTP |
| PurrplanSocial media scheduler your AI agent can drive: plan, publish, inbox, analytics on 12+ networks. | Remote · HTTP |
| PVPWireHand-compiled game-mechanics data for Diablo 2, Path of Exile, Diablo 3 and GW2, plus live signal. | Local · stdio |
| PZEROPrepaid inference for agents over hosted MCP. Chat, image, and video. | Remote · HTTP |
| QencodeCreate video experiences with the Qencode API, straight from your AI assistant. | Remote · HTTP |
| Qpost MCPMCP server for QPost — lets AI agents publish video and image posts to YouTube, TikTok, Instagram. | Remote & Local · HTTP, stdio |
| QQuickpickSearch movies/TV by mood, genre, score, cast, and awards, filtered to what's streaming near you. | Remote · HTTP |