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_modelsC | List Fish voices; has_more is boolean for self=true, otherwise possibly null. |
| fish_get_modelA | Get a Fish voice model by ID. |
| fish_create_modelA | Save a cloned voice long-term and publicly; other users may discover and use it. |
| 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 7 tools
Each tool targets a distinct resource+action: audio generation (fish_generate_audio), model lifecycle (create/get/list), task polling (single vs batch), and a documentation tool. The descriptions explicitly pre-empt the main confusion points, e.g. fish_create_model vs fish_generate_audio and fish_get_task vs fish_get_tasks_batch. An agent can select unambiguously.
All seven tools use a uniform fish_<verb>_<noun> snake_case pattern (generate_audio, create_model, get_model, get_task, get_tasks_batch, get_usage_guide, list_models). Verb choices (get/create/list/generate) are used consistently with their intent.
Seven tools is a well-scoped surface for a TTS service: generation, async task polling, and voice model management. No redundant or filler tools; each covers a distinct workflow step.
Voices can be created, fetched, and listed, but there is no delete/revoke operation for publicly saved models — a notable lifecycle gap given there is no private option. Task tracking also lacks a way to list outstanding tasks without knowing IDs in advance, forcing agents to remember task_ids.