Skip to main content
Glama
cgitato

gequbao

by cgitato
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to gequbao

No user-submitted related servers found.

    Related Servers

    • qq-music-mcp

      wangkezun
      A
      license
      A
      quality
      D
      maintenance
      Integrates QQ Music API with MCP, enabling LLMs to search music, retrieve song details, lyrics, and playback URLs.
      10
      4
      MIT

    • Music Player MCP

      Irislan0723
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables in-chat music playback by searching song names or specifying Netease song IDs, returning playable music cards with cover, lyrics, and a temporary audio proxy. It relies on a user-configured Netease-compatible API and supports custom card colors.
      3
      MIT

    • LLM Jukebox MCP Server

      jabberjabberjabber
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables LLMs to search, download, and extract information from YouTube music videos, converting them to high-quality MP3 files.
      GPL 3.0

    • CloudMusic Desktop MCP

      Seraph310
      A
      license
      Not graded
      quality
      C
      maintenance
      Controls the official NetEase Cloud Music desktop client on Windows, enabling AI to search, play, manage queues, and adjust playback settings via a local control channel.
      1
      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

    A4.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools serve clearly distinct purposes: search for songs and retrieve a playback URL. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow a consistent snake_case and verb_noun pattern: search_with_full_title and get_music_url. No naming conflicts or style mixing.

    Tool Count3/5

    With only 2 tools, the server is minimal. While it covers a basic search-to-play workflow, the number feels slightly thin for a music service. However, it is not extreme and matches the narrow scope.

    Completeness4/5

    The core workflow of searching for songs and retrieving audio URLs is covered. Minor gaps exist, such as no separate tool for song metadata only, but agents can work around by using the search result data.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources