Skip to main content
Glama
Sign In
audio-mcp

audio-mcp

by narteyr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

audio-mcp

A mock-first Model Context Protocol server for audio generation. It creates deterministic placeholder WAV files locally, making it possible to develop and test an audio-tool workflow without credentials, network calls, or generation fees.

Tools

  • generate_music(prompt, duration_seconds=2.0)

  • generate_sound_effect(prompt, duration_seconds=1.0)

  • get_generation_status(generation_id)

Generation calls complete synchronously and return a generation ID plus a local asset containing its path, file URI, MIME type, format, and duration. Durations must be between 0.1 and 30 seconds.

Related MCP server: io.github.chicogong/ffvoice

Development

Python 3.10 or newer is required.

python -m venv .venv
. .venv/bin/activate
pip install -e '.[dev]'
pytest

The integration test launches the STDIO server, initializes an MCP client, lists the tools, calls every tool, and checks the generated WAV asset.

Run the server

The default transport is STDIO:

python -m audio_mcp.server

Generated files are written to .audio-mcp/. Override that location with AUDIO_MCP_OUTPUT_DIR.

To register a development checkout with Codex CLI:

codex mcp add audio-dev -- python -m audio_mcp.server
codex mcp list

The server intentionally has no paid provider integration. A production provider can later implement the same asset response contract once the MCP workflow has been validated.

Available Tools

3 tools
generate_musicB

Generate a mock music WAV from a text prompt.

Inputs: prompt (required), duration_seconds. Returns: object

generate_sound_effectB

Generate a mock sound-effect WAV from a text prompt.

Inputs: prompt (required), duration_seconds. Returns: object

get_generation_statusA

Return the state and asset metadata for a generation.

Inputs: generation_id (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: generating music, generating sound effects, and checking generation status. The two generation tools are clearly separated by output type, and the status tool is orthogonal to the generation actions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: generate_music, generate_sound_effect, and get_generation_status. The naming is uniform and predictable.

    Tool Count4/5

    Three tools is on the lean side but appropriate for a focused mock audio generation service. The set covers the essential operations without superfluous additions.

    Completeness4/5

    The tools cover the core workflow of starting a generation and checking its status. Minor gaps like canceling or listing generations exist but are not critical for a mock service.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • speaches-mcp

      xavier-hernandez
      F
      license
      C
      quality
      C
      maintenance
      An MCP server that exposes speech-to-text and text-to-speech capabilities using a local speaches instance, allowing AI assistants to transcribe audio and generate speech.
      2
      -

    • STT2TTS MCP

      pygodzilla
      A
      license
      Not graded
      quality
      D
      maintenance
      Local-first speech-to-text and text-to-speech MCP server. Hot-swappable engines via config.yaml — no code changes, no API keys required.
      2
      MIT

    • MCP Voice Soundboard

      mcp-tool-shop-org
      A
      license
      Not graded
      quality
      B
      maintenance
      A text-to-speech MCP server with 48 voices across 9 languages, supporting emotion spans, SFX tags, and multi-speaker dialogue. Deployable via a single npx command with built-in guardrails and swappable backends.
      31 PyPI
      MIT