spt-forge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_modsA | Search and filter SP-Tarkov mods on the Forge. Supports full-text search via |
| get_modA | Get full details for a specific SP-Tarkov mod by its numeric ID. Includes description, versions, license, and category by default. |
| get_mod_versionsA | Get the full version history for a mod. Includes SPT version constraints, download counts, Fika compatibility status, and dependency info. |
| check_mod_updatesA | Check for available updates for installed mods against a target SPT version. Handles dependency validation and prerelease logic. |
| resolve_mod_dependenciesB | Resolve the full recursive dependency tree for one or more mod versions. Detects version conflicts and provides download links. |
| search_addonsB | Search SP-Tarkov addons (supplemental content for mods, like music packs or texture overrides). |
| get_addonB | Get full details for a specific addon by its numeric ID. |
| list_categoriesA | List all available mod categories on the Forge. Useful for discovering category slugs to filter searches. |
| get_spt_versionsB | List available SPT versions with mod counts and release links. Useful for determining which SPT version constraint to filter mods by. |
| pingA | Health check — returns pong if the Forge API is reachable. |
| get_addon_versionsC | Get the full version history for an addon. Includes mod version constraints, download counts, and file sizes. |
| resolve_addon_dependenciesA | Resolve the full recursive dependency tree for one or more addon versions. Uses addon ID or slug as identifier (not GUID). |
| get_categoryA | Get a single mod category by its numeric ID or slug. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
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.
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).
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).
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.