Skip to main content
Glama
cebarks

spt-forge-mcp

by cebarks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to spt-forge-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-cli-catalog

      abcpro1
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that publishes CLI tools on your machine for discoverability by LLMs
      10 npm
      1
      MIT
    • @restforge-dev/mcp-server by restforge

      @restforge-dev/mcp-serverofficial

      restforge
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes RESTForge capabilities to AI agents, enabling them to set up, configure, generate code, and manage RESTForge projects through natural language.
      29
      44 npm
      MIT

    • HMCL MCP Server

      vfyjxf
      F
      license
      A
      quality
      C
      maintenance
      MCP server that lets AI agents drive HMCL (Hello Minecraft! Launcher) programmatically to install Minecraft versions, search/download/import modpacks from Modrinth/CurseForge, and launch/stop the game.
      13
      1
      -

    • forge-mcp

      alongkornonline2019
      A
      license
      Not graded
      quality
      D
      maintenance
      The Forge Engine runtime: a thin, MIT-licensed proxy that connects any MCP client to Forge — the design spec AI coding agents read before building and report back to. Serves the full 54-tool surface; discovery works signed out, tool calls authenticate.
      13 npm
      MIT

    • metasearch-mcp

      YeonwooSung
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for using various search tools like Tavily API. Planning to support various search tools (i.e. wiki search, searxng, etc)
      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.8/5.0

    Scored across 13 tools

    Disambiguation5/5

    Tools are clearly separated by entity type (mod vs addon) and action (search, get, list, resolve, check). Each tool has a distinct purpose, with no overlapping functionality. For example, `search_mods` and `search_addons` target different content categories, and `get_mod` vs `get_mod_versions` provide different levels of detail.

    Naming Consistency5/5

    All tool names follow a consistent `verb_noun` pattern using snake_case (e.g., `check_mod_updates`, `get_addon_versions`, `list_categories`). There is no mixing of styles, and verbs accurately describe the operation (get, search, list, resolve, check, ping).

    Tool Count5/5

    With 13 tools, the set is well-scoped for a mod repository query interface. It covers search, details, versions, dependencies, categories, and health check without unnecessary bloat. The number aligns with typical MCP servers (3-15 tools).

    Completeness5/5

    The tool surface appears complete for browsing and resolving dependencies in the SP-Tarkov mod ecosystem. It includes search, detail retrieval, version history, dependency resolution, category exploration, and update checking. The workflow from discovering mods via search to resolving dependencies is fully supported, with no obvious dead ends.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources