Skip to main content
Glama
tomkit

sc2-mcp

by tomkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to sc2-mcp

No user-submitted related servers found.

    Related Servers

    • sc-bwapi-mcp

      ainaxiya
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants such as Trae or Claude to control StarCraft 1.16.1 matches through BWAPI, providing tools to read game state, train units, build, move, attack, gather, and chat.
      9
      -

    • RAG MCP Server

      torkian
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to search custom knowledge bases using retrieval-augmented generation via a simple MCP tool.
      MIT

    • Forja MCP Server

      gilsonfiho
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.
      1
      MIT

    • stellavault

      Evanciel
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to read, search, and analyze your entire knowledge vault locally via MCP tools like search, drafting, and linting.
      39 npm
      5
      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.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: auth (login/logout), account info, knowledge search, replay upload/list, report reading, coach run, follow-up Q&A, and paid unlocks. The only potential overlaps (get_analysis vs analyze_replay, search_sc2_knowledge vs ask_about_replay) are clearly separated by descriptions as read vs run and general vs replay-specific.

    Naming Consistency4/5

    All names use snake_case and mostly follow verb_noun (get_account, upload_replay, list_my_replays, analyze_replay). The bare verbs login/logout are a minor deviation but still unambiguous and consistent within the auth pair.

    Tool Count5/5

    10 tools is well within the typical 3–15 range and each tool maps to a distinct step in the account/replay analysis workflow. No tool feels redundant or missing from a scope perspective.

    Completeness4/5

    The surface covers the core lifecycle: authentication, account info, knowledge search, replay upload/list, report retrieval, coach analysis, follow-up questions, and paid unlocks. Minor gaps exist (e.g., no delete-replay or direct mineral purchase tool), but they are workaroundable or external to the main workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources