Skip to main content
Glama
slshults

gpra-chord-charts-mcp

by slshults
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to gpra-chord-charts-mcp

No user-submitted related servers found.

    Related Servers

    • Chess.com MCP Server

      pab1it0
      A
      license
      B
      quality
      C
      maintenance
      Provides access to Chess.com player data, game records, and public information through standardized MCP interfaces, allowing AI assistants to search and analyze chess information.
      10
      90
      MIT

    • mcp-chess

      pipeworx-io
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Chess.com player profiles, ratings, game histories, and leaderboard rankings through a natural language MCP interface.
      258 npm
      MIT

    • CloudChampion MCP Server

      frdeange
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server to query Cloud Champion's training catalog. Enables AI agents to search, filter, and get statistics about Microsoft partner resources like webinars, videos, learning paths, and podcasts.
      MIT

    • c64-kb

      bdgscotland
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and developers to query a structured Commodore 64 knowledge base over MCP, combining semantic search and knowledge graph traversal for hardware references, techniques, recipes, pitfalls, timing budgets, and compatibility checks.
      28 npm
      23
      BSD 3-Clause
    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.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct retrieval route: by numeric ID, by chord name, and by daily feature. The by_id tool explicitly states its ID comes from get_chord_chart_by_name, so an agent will not confuse it with a direct name lookup.

    Naming Consistency4/5

    All tools use snake_case with a get_ prefix and follow a get_<object>_<qualifier> shape. The first two share the exact get_chord_chart_by_ pattern, while get_chord_of_the_day is a slight structural variation but remains predictable.

    Tool Count5/5

    Three tools is well-scoped for a focused, read-only chord chart server. Each tool serves a clear purpose without redundancy, so the count is neither too thin nor bloated.

    Completeness4/5

    The core workflows are covered: lookup by name, re-fetch by ID, and the daily chord. Minor gaps exist such as no search/browse tool for the 12,708 chord names, but they are not fatal to the server's stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources