Skip to main content

Overview

FineVoice provides a Model Context Protocol (MCP) Server that lets MCP-compatible AI clients — such as Claude Desktop, Cursor, and VS Code — call the FineVoice API directly, without writing any custom integration code. The MCP Server exposes largely the same capabilities as the REST API, including text-to-speech, voice conversion, speech-to-text, podcast generation, sound effect generation, audio separation, voice management, voice cloning, music generation, and audio enhancement. Endpoint
Transport: Streamable HTTP

Authentication

The MCP Server uses the same authentication method as the REST API — a Bearer token passed in the Authorization header:
When configuring your MCP client, add this header to the corresponding headers field (see the client configuration examples below).
Keep your API key private. Do not commit it to public repositories or expose it in plain text in shared client configuration files.

Client Configuration

Add the following to claude_desktop_config.json:
After configuring, restart your client. You can then ask the AI to call FineVoice tools directly in conversation (for example, “Convert this text to speech using the voice james”).

Available Tools

Each tool on the MCP Server maps to a FineVoice REST API endpoint, with the same parameters and response structure. Asynchronous tasks are polled with the task status tool, just like the REST API.

Text to Speech / Podcast

Speech to Text

Sound Effects & Audio Separation

Voices / Voice Cloning

Music Generation

Audio Enhancement

Scoring & Other

Task Polling


Notes

  • MCP tool calls share the same quota and billing as the REST API — see API Pricing.
  • For asynchronous tasks (such as music generation or voice clone training), poll the result with the Get Task Status tool after submitting the request via MCP.