Paxa Labs
MCP server by Paxa Labs
Speak, transcribe, translate to Thai and OCR documents with Thai, English and Mandarin speech AI, including local audio playback.
Install Paxa Labs
Runs on your machine. Your client starts it with this command:
Needs Node.js on your computer. The setup steps below show where the command goes in each client.
PAXA_API_KEYsecret Paxa Labs API key, created at https://paxalabs.com/app/keysPAXA_OUTPUT_DIRoptional Directory where text_to_speech saves files (default: the working directory)PAXA_DEFAULT_VOICEoptional Voice id used when a call does not pick one (default: foithong)
Share this server
Opens this page, with the install command and setup steps.
mcp.tc/i/paxa-labsAbout
Connects an assistant to the Paxa Labs API for Thai, English and Mandarin speech AI. It can speak through your speakers, queue long content for playback, save speech to audio files, record and transcribe audio, translate any language into Thai, run OCR on PDFs and images, and extract typed fields from documents. It also designs and manages custom voices.
It runs locally over stdio as the npm package @paxalabs/mcp, started with npx and requiring Node. A Paxa API key is required, set as PAXA_API_KEY. New accounts include free credits, and most tools use credits per character, minute or page.
What you can do
- Speak text through local speakers with a managed playback queue
- Synthesize speech to mp3, opus or wav files with optional subtitles
- Transcribe recordings with speaker labels and srt or vtt subtitles
- Translate any language into Thai
- OCR local PDFs and images into Markdown
- Extract typed fields from documents
- Design, refine, save and manage custom voices
- Check credit balance, models and voices
Tools
Paxa Labs lists its tools only to clients with a key, so we can’t show them here.
Example prompts
Read this article aloud using queue_speech
Transcribe meeting.mp4 with speaker labels and give me an srt file
Translate this paragraph into formal Thai
Extract the ID number and date from scan.pdf
Set up
Every client starts Paxa Labs on your machine with the same command. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio paxa-labs --env "PAXA_API_KEY=<YOUR_PAXA_API_KEY>" -- npx -y @paxalabs/mcp- Start Claude Code and type
/mcp. paxa-labs should show as connected.
Add --scope user to make it available in every project. Replace the placeholders with your own values.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"paxa-labs": {
"command": "npx",
"args": [
"-y",
"@paxalabs/mcp"
],
"env": {
"PAXA_API_KEY": "<YOUR_PAXA_API_KEY>"
}
}
}
}- Save the file and restart Claude Desktop. Replace the placeholders with your own values.
Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"paxa-labs": {
"command": "npx",
"args": [
"-y",
"@paxalabs/mcp"
],
"env": {
"PAXA_API_KEY": "<YOUR_PAXA_API_KEY>"
}
}
}
}Needs Node.js on your computer. Replace the placeholders with your own values.
VS Code
Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:
{
"servers": {
"paxa-labs": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@paxalabs/mcp"
],
"env": {
"PAXA_API_KEY": "${input:paxa-api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "paxa-api-key",
"description": "PAXA_API_KEY",
"password": true
}
]
}Needs Node.js on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"paxa-labs": {
"command": "npx",
"args": [
"-y",
"@paxalabs/mcp"
],
"env": {
"PAXA_API_KEY": "<YOUR_PAXA_API_KEY>"
}
}
}
}- Refresh the MCP server list in Cascade. Replace the placeholders with your own values.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add paxa-labs --env "PAXA_API_KEY=<YOUR_PAXA_API_KEY>" -- npx -y @paxalabs/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.paxa-labs]
command = "npx"
args = ["-y", "@paxalabs/mcp"]
env = { PAXA_API_KEY = "<YOUR_PAXA_API_KEY>" }Needs Node.js on your computer. Replace the placeholders with your own values.
Gemini CLI
gemini mcp add -e "PAXA_API_KEY=<YOUR_PAXA_API_KEY>" paxa-labs npx -- -y @paxalabs/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"paxa-labs": {
"command": "npx",
"args": [
"-y",
"@paxalabs/mcp"
],
"env": {
"PAXA_API_KEY": "<YOUR_PAXA_API_KEY>"
}
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs Node.js on your computer. Replace the placeholders with your own values.
Embed
Show Paxa Labs in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/paxa-labs)<a href="https://mcp.tc/i/paxa-labs"><img src="https://mcp.tc/i/paxa-labs/badge.svg" alt="Paxa Labs on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/paxa-labs.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/paxa-labs" title="Paxa Labs on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/paxa-labs.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Paxa Labs card to your site.
Add the mcp.tc card for Paxa Labs, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/paxa-labs.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="paxa-labs"><a href="https://mcp.tc/i/paxa-labs">Paxa Labs on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/paxa-labs)
```
Reference: https://mcp.tc/embedChange history
This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.
FAQ
Can I paste mcp.tc/i/paxa-labs into my MCP client?
No. Paxa Labs runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @paxalabs/mcp.
Does Paxa Labs need an API key?
Yes. It reads PAXA_API_KEY from its environment, and PAXA_API_KEY is a secret. Put the value in your client’s config on your own machine, never in a shared file.
Is Paxa Labs a remote or a local server?
Local. Your client starts it as a process on your computer with npx -y @paxalabs/mcp, which needs Node.js.
What can Paxa Labs do?
You can speak text through local speakers with a managed playback queue, synthesize speech to mp3, opus or wav files with optional subtitles and transcribe recordings with speaker labels and srt or vtt subtitles.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Does mcp.tc track changes to Paxa Labs?
Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Paxa Labs’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Paxa Labs. This page was built from Paxa Labs’s public metadata, last checked on 1 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.