“Centralizar el procesamiento de audio redujo la lógica especial que manteníamos en cada cliente.”
Álvaro P.
Líder técnico, Valencia
Claude's custom connectors reach Voxmin's MCP server directly. You add Voxmin once in your Claude account, sign in with your Voxmin account, and it works in Claude on the web, in Claude Desktop and in the mobile apps.
In Claude, open Settings → Connectors and choose Add custom connector.
Name it Voxmin and paste the MCP server URL:
https://api.voxmin.com/auth/mcp
Keep Authentication on Sign in now, and the OAuth client on Use Claude's published identity. Voxmin supports it, so there is nothing else to fill in. Leave Request headers empty.
Choose Add, then Connect. Claude opens Voxmin in your browser: log in if you are asked, check that the page names Claude, and choose Approve. You are taken back to Claude.
get_account and answers with your credits.Voxmin lists Claude under AI Integrations → Connected apps. Sign out there stops it at once.
If your Claude Desktop cannot add custom connectors, add Voxmin through its config file. That file starts local servers, so Voxmin is reached through mcp-remote, a small bridge that needs Node.js 18 or newer.
On AI Integrations, make a token. It starts with vxm_ and is shown only once, so copy it then.
In Claude Desktop, open Settings → Developer → Edit Config. That opens claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd a voxmin entry under mcpServers (keep any servers already there), with your token in place of <your token>:
{
"mcpServers": {
"voxmin": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.voxmin.com/auth/mcp",
"--header",
"Authorization:${VOXMIN_AUTH}"
],
"env": {
"VOXMIN_AUTH": "Bearer <your token>"
}
}
}
}
The header is written as Authorization:${VOXMIN_AUTH} with no space on purpose: on Windows, Claude Desktop does not escape spaces inside args. The space between Bearer and the token lives in env, where it is safe.
Quit Claude Desktop completely and open it again. The config file is only read at start-up.
| What you see | Why | What to do |
|---|---|---|
| "Couldn't reach the MCP server" when adding | The URL has a typo, or a space at either end | Paste the URL again exactly as shown above |
| The Voxmin page says the sign-in has ended | It waited more than 10 minutes, or was already answered | Choose Connect again in Claude |
| Voxmin is connected but not in the tools menu | It is switched off for this chat | Turn it on in the chat's tools menu |
| "Custom header names need Anthropic approval" | A request header was added | Remove the connector, add it again with no request headers, and sign in instead |
| Voxmin stopped working | It was signed out on Voxmin, or not used for 90 days | Choose Connect again in Claude's Connectors |
| "Daily credit cap reached" (token setup) | Today's spend through this token would pass its cap | Wait until midnight UTC, or make a token with a higher cap |
| "Not enough credits" | Your balance is lower than the tool's price | Top up on the Pricing page |
429 Too Many Requests | More than 60 requests in a minute | Wait a minute and try again |
| The request is refused | It did not pass Voxmin's content checks | Change the request. A refused picture is not charged |
See the overview for every tool, its price and how billing works.
De desarrolladores que integran la API de Voxmin en sus aplicaciones.
“Centralizar el procesamiento de audio redujo la lógica especial que manteníamos en cada cliente.”
Álvaro P.
Líder técnico, Valencia
“La documentación nos ayudó a validar los payloads antes de conectar nuestro procesador por lotes.”
Mateo C.
Ingeniero de plataforma, Bogotá
“Usamos los estados de trabajo para mostrar un progreso claro sin bloquear nuestra aplicación.”
Sofía R.
Desarrolladora full-stack, Buenos Aires
“La API asíncrona encaja bien con nuestra cola de trabajos y mantiene la integración sencilla.”
Irene V.
Desarrolladora backend, Madrid