Skip to main content
Glama
shengchao73

MCP-Suno

by shengchao73
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP-Suno

No user-submitted related servers found.

    Related Servers

    • suno-v6-kie-mcp

      xaxeane
      F
      license
      A
      quality
      C
      maintenance
      MCP server that enables generating songs or instrumental music using Suno V6, V6_MINI, and V6_WILD models via the Kie.ai API, with support for checking task status and retrieving audio URLs.
      2
      -

    • suno-mcp

      runapi-ai
      A
      license
      B
      quality
      A
      maintenance
      A RunAPI MCP server for the Suno music generation models, enabling task creation (text-to-music, covers, mashups, etc.), polling, and pricing lookup through a single API key.
      21
      640 npm
      1
      Apache 2.0

    • Tunova

      erliona
      A
      license
      A
      quality
      D
      maintenance
      Generate music with Suno (v5.5) from any MCP client — async, and billed only on successful renders (a failed render auto-refunds). Hosted Streamable-HTTP server; tools generate_song / wait_for_song / check_song.
      3
      9 npm
      MIT

    • Suno-Hmnn-MCP

      SialkiLabs
      A
      license
      Not graded
      quality
      A
      maintenance
      A FastMCP server that provides full programmatic access to Suno Premier features, including music generation, clip extension, stem separation, and audio retrieval using your Suno account.
      3
      MIT
    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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    generate_lyrics and generate_music have clearly distinct outputs: one returns text (lyrics), the other returns audio/video (music). Their names and descriptions make the separation unambiguous.

    Naming Consistency5/5

    Both tools follow the exact same 'generate_<noun>' pattern, using snake_case consistently. This creates a predictable and coherent naming convention.

    Tool Count3/5

    With only 2 tools, the server feels thin for a music generation service. While the tools cover core generation, the count is borderline and would benefit from additional management or status tools.

    Completeness2/5

    The server only offers generation, lacking any way to list, retrieve, or manage past generations. For a realistic workflow, agents need status checks or history access, making the surface significantly incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources