Brainiall TTS MCP

by fasuizu-br

Not rated
GitHub

About

Hosted text-to-speech MCP server with 54 neural voices in 9 languages, including Brazilian Portuguese, using API-key authentication and pay-per-use billing.

Details

Author
fasuizu-br
Categories
Other

Remote server (recommended — nothing to install)

Use the](https://www.brainiall.com/transcreve/integracoes/dify-transcreve-ptbr-pipeline)project-scoped Codex configuration. It readsBRAINIALL_API_KEYfrom the environment, allowlists the three Brainiall tools, and prompts before every call.

Use theenvironment-backed Claude Code configuration. It keeps the key out of.mcp.json, scopes the server to the current project, and documents the external-data and metered-usage boundary.

Claude Desktop / any client with.mcp.json-style config

{ "mcpServers": { "brainiall-tts": { "type": "http", "url": "https://api.brainiall.com/mcp/tts/mcp", "headers": { "Authorization": "Bearer YOUR_BRAINIALL_API_KEY" } } } }
{ "mcpServers": { "brainiall-tts": { "url": "https://api.brainiall.com/mcp/tts/mcp", "headers": { "Authorization": "Bearer YOUR_BRAINIALL_API_KEY" } } } }

Use the official one-click deeplink and the explicit local-model privacy boundary in theLM Studio setup guide.

Use the remote-server schema and environment-backed Bearer header in theOpenCode v2 setup guide.

Use themanual Msty Studio field guidefor a Streamable HTTP connection. The reference file is not presented as an official integration or import preset.

Use theadministratorMCP_SERVERSexampleand a tool-capable model. The guide documents the shared-key boundary for base servers.

Use the zero-dependency[partial OpenAI-shaped TTS adapterwhen a client can configure an OpenAI-style speech route but cannot call Brainiall's native endpoint. The adapter returns WAV only, declares the sample rate observed in the WAV header, never retries a metered request, and documents the exact compatibility limits. It is a local reference adapter, not a claim that the hosted Brainiall API is natively OpenAI-compatible.

Hosted text-to-speech for AI agents via theModel Context Protocol.

54 neural voices, 9 languages— including nativeBrazilian Portuguese(pf_dora,pm_alex,pm_santa) — served from a hosted, pay-per-use API. No GPU, no model downloads, no ElevenLabs subscription: bring one API key and pay$0.008 per 1,000 characters($10 free credits on signup).

Every other TTS MCP server either runs models locally (heavy, slow to set up) or wraps a third-party key you already pay a subscription for. This one is a hosted, metered API:

- Zero setup— remote server, nothing to install
- Pay per use— $0.008/1K characters, billed against your Brainiall balance
- $10 free credits— sign up at
app.brainiall.com
- WAV out— 16-bit PCM, 24 kHz mono, returned as playable MCP audio content or base64 JSON

Get an API key atapp.brainiall.com($10 welcome credits, no card required).

The button installs the remote server in discovery mode, so VS Code can list its tools without a secret. Synthesis still fails closed until you add your Brainiall API key. For a secure workspace configuration that prompts once and stores the key in VS Code's secret storage, copy.vscode/mcp.jsoninto your project or clone this repository, then startbrainiallTtsfromMCP: List Servers.

{ "inputs": [ { "type": "promptString", "id": "brainiall-api-key", "description": "Brainiall API key", "password": true } ], "servers": { "brainiallTts": { "type": "http", "url": "https://api.brainiall.com/mcp/tts/mcp", "headers": { "Authorization": "Bearer ${input:brainiall-api-key}" } } } }

Use Brainiall TTS to list the Brazilian Portuguese voices, then read “Olá do VS Code” withpf_dora.

The install URL format and secret-input configuration follow theofficial VS Code MCP guideandconfiguration reference.

Use therestricted remote-server configurationfor Copilot cloud agent or Copilot code review. It allowlists the three Brainiall tools and resolves the Bearer token from the repository'sCOPILOT_MCP_BRAINIALL_API_KEYAgents secret; no API key is committed.

Copy the ready-to-useContinue MCP blockto.continue/mcpServers/brainiall-tts.yaml, then putBRAINIALL_API_KEY=your-keyin.continue/.env. Keep that.envfile out of version control.

The block uses Continue's supportedstreamable-httptransport and resolves the key through${{ secrets.BRAINIALL_API_KEY }}; no credential is committed. See theContinue setup and smoke test.

For a Dify speech workflow, use the open-sourceBRAINIALL Speech providerand keep the API key in Dify's credential store. Thebounded Dify intent routeexplains the caller-owned boundary; it is not a Dify partnership or a guarantee of production behavior.

Remote server (recommended — nothing to install)

Use theproject-scoped Codex configuration. It readsBRAINIALL_API_KEYfrom the environment, allowlists the three Brainiall tools, and prompts before every call.

Use theenvironment-backed Claude Code configuration. It keeps the key out of.mcp.json, scopes the server to the current project, and documents the external-data and metered-usage boundary.

Claude Desktop / any client with.mcp.json-style config

{ "mcpServers": { "brainiall-tts": { "type": "http", "url": "https://api.brainiall.com/mcp/tts/mcp", "headers": { "Authorization": "Bearer YOUR_BRAINIALL_API_KEY" } } } }
{ "mcpServers": { "brainiall-tts": { "url": "https://api.brainiall.com/mcp/tts/mcp", "headers": { "Authorization": "Bearer YOUR_BRAINIALL_API_KEY" } } } }

Use the official one-click deeplink and the explicit local-model privacy boundary in theLM Studio setup guide.

Use the remote-server schema and environment-backed Bearer header in theOpenCode v2 setup guide.

Use themanual Msty Studio field guidefor a Streamable HTTP connection. The reference file is not presented as an official integration or import preset.

Use theadministratorMCP_SERVERSexampleand a tool-capable model. The guide documents the shared-key boundary for base servers.

Use the zero-dependencypartial OpenAI-shaped TTS adapterwhen a client can configure an OpenAI-style speech route but cannot call Brainiall's native endpoint. The adapter returns WAV only, declares the sample rate observed in the WAV header, never retries a metered request, and documents the exact compatibility limits. It is a local reference adapter, not a claim that the hosted Brainiall API is natively OpenAI-compatible.

Run locally (stdio-free, still calls the hosted API)

The server itself is a thin wrapper — you can self-host it and it will proxy toapi.brainiall.comwith your key:

docker build -t brainiall-tts-mcp . docker run -p 8080:8080 -e APIM_KEY=YOUR_BRAINIALL_API_KEY brainiall-tts-mcp # MCP endpoint: http://localhost:8080/mcp

"Read this paragraph out loud in Brazilian Portuguese with a female voice"

The agent callssynthesize_speech(text=..., language="pt", voice="pf_dora")and receives playable WAV audio.

For copy-ready prompts and smoke tests for narration, accessibility, language practice, and agent alerts, seeAgent workflow recipes.

For REST client testing and automation, import thePostman collection. It contains health, voice-list and two-character synthesis smoke tests and keeps the API key in a collection variable rather than the request URL.

For no-code automation, import then8n text-to-WAV workflow. It uses n8n's Header Auth credential instead of embedding a key in the workflow, sends editable text, voice and speed fields to the hosted API, and returns the WAV in the binary propertyspeech. The template is statically validated; select your credential and run it in your own n8n instance to validate the live integration.

For code generation, API clients, and directory discovery, use the machine-readableOpenAPI 3.1 specification. The specification documents the authenticated voice catalog and WAV synthesis endpoints without embedding an API key.

Pass your Brainiall API key as a Bearer token (see configs above). Usage is metered per character against your account balance — the same key works across all Brainiall APIs (STT, OCR, NLP, image and more atbrainiall.com).

- MCP (Streamable HTTP):https://api.brainiall.com/mcp/tts/mcp
- Health:https://api.brainiall.com/mcp/tts/health
- Underlying REST API:POST https://api.brainiall.com/v1/tts/synthesize

Hosted MCP server for AudioPod's audio AI: text-to-speech, voice cloning, music generation, stem and speaker separation, transcription, denoise, and voice conversion.

AI-powered text-to-speech MCP server with instant voice cloning. Generate speech from Claude Desktop, Claude Code, or n8n using 5 built-in voices (English, German, French, Spanish) or clone any voice from a short audio sample. Runs fully local, no API keys, no cloud. Supports stdio, SSE, and HTTP transports.

Local-first voice toolkit: STT (25 langs, ~19x faster than Whisper on Apple Silicon via CoreML, ONNX fallback), TTS (Kokoro + Vosk-TTS + 180 macOS voices, SSML), VAD, language detection (107 langs). Rust engine, OpenClaw skill. No cloud, no API keys.

A text-to-speech server using the macOS say command.

AI transcription from URLs or local files: 119 languages, speaker diarization, word-level timestamps, SRT/VTT/text export.

Production speech AI MCP server with pronunciation scoring, speech-to-text, and text-to-speech — 10 tools, 7 resources, 3 prompts.

A Model Context Protocol server that exposes the canonical WordCast knowledge surface — voice and TTS workflows, blog topics, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.

An AI voice toolkit with TTS, voice cloning, and video translation, now available as an MCP server for smarter agent integration.

Generate high-quality text-to-speech and text-to-voice outputs using the DAISYS platform.

Interact with MiniMax's powerful Text-to-Speech, image, and video generation APIs.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.