MCP Fish Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACEDATACLOUD_API_TOKEN | Yes | Your AceDataCloud API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fish_generate_audioB | Generate speech audio from text using Fish TTS. |
| fish_get_usage_guideA | Get a comprehensive guide for using the Fish TTS tools. |
| fish_list_modelsB | List available Fish voice models from the API. |
| fish_get_modelA | Get a Fish voice model by ID. |
| fish_get_taskA | Query the status and result of a Fish audio generation task. |
| fish_get_tasks_batchA | Query the status of multiple Fish tasks at once. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fish_guide | Guide for choosing the right Fish TTS tool. |
| fish_workflow_examples | Common workflow examples for Fish TTS tasks. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clear, distinct role: generating audio, retrieving individual models, listing models, checking single or batch task status, and providing usage guidance. There is no meaningful overlap between any of the tools.
All tools follow a consistent fish_ prefix with a clear verb_noun pattern: generate_audio, get_model, get_task, get_tasks_batch, get_usage_guide, list_models. The naming is predictable and easy to navigate.
Six tools is an appropriate, well-scoped count for a TTS-focused server. Each tool serves a necessary function without redundancy or bloat.
The surface covers the core generation workflow: create a task, poll its status, check batches, and browse voice models. Minor gaps like canceling a task or listing all tasks without IDs are absent, but the main workflow is fully supported.