Fish Audio Text-to-Speech MCP Adapter

This service bridges the capabilities of the Fish Audio API into the MCP framework, enabling programmatic transformation of textual input into highly realistic vocal output with granular control over audio characteristics.

Core Capabilities

• Standard Synthesis: Converts arbitrary strings into lifelike spoken audio streams.
• Parametric Control: Allows precise configuration of output specifications such as encoding format and bitrate.
• MCP Interoperability: Designed for plug-and-play integration with any MCP-compliant application environment.

Setup Instructions

Install required libraries:

bash pip install -r requirements.txt

Alternatively, use direct package installation:

bash pip install fish-audio-sdk mcp python-dotenv

Configuration

Establish a .env file in the root directory containing authentication and endpoint identifiers:

API_KEY=your_fish_audio_api_key MODEL_ID=your_fish_audio_model_id

Ensure these placeholders are replaced with your valid credentials obtained from Fish Audio.

Execution

Service Launch

Initiate the local MCP service listener:

bash python app.py

Or utilize the MCP command-line utility:

bash mcp run --file app.py

Demonstration Script

Run the provided example script for a quick test:

bash python example.py

Invocation via MCP Client

Interaction example using an MCP consumer client:

python

Client-side example

from mcp.client import MCPClient

Assuming the service is running locally or accessible via the specified address

client = MCPClient("subprocess://python app.py") response = client.call("text_to_speech", {"text": "Greetings, digital world!"}) print(response) # Output will be the resultant audio file locator

Exposed RPC Endpoints

text_to_speech

Performs fundamental text-to-voice conversion.

Arguments: - text: The input sequence to be vocalized. - output_path (optional): Destination path for the generated file; a temporary file is created if omitted.

Returns: The filesystem path to the synthesized audio resource.

advanced_text_to_speech

Offers enhanced control over the synthesis process and output characteristics.

Arguments: - text: The textual content for conversion. - output_path (optional): File location specification. - format: Desired audio container type (e.g., mp3, wav, pcm). Default is mp3. - mp3_bitrate: Specific bitrate setting for MP3 output (e.g., 64, 128, 192 kbps). Default is 128. - chunk_length: Segment size parameter (range 100-300). Default is 200. - normalize: Boolean flag for text preprocessing normalization. Default is True. - latency: Operational mode selection (normal or balanced). Default is normal.

Returns: The filesystem path to the synthesized audio resource.

get_model_info

Retrieves metadata regarding the currently active synthesis model.

Returns: A dictionary containing the Model Identifier and a truncated API Key prefix.

get_available_models

Fetches a comprehensive catalog of all accessible Fish Audio synthesis models.

Returns: A list structure detailing model attributes.

Licensing

MIT

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea