Nexus Mods MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for HTTP transport. Used with --http mode. | |
| NEXUS_API_KEY | No | Personal Nexus Mods API key for standalone catalogue mode (Nexus API reads without Vortex). | |
| MCP_HTTP_TOKEN | No | Bearer token for HTTP transport. Must contain at least 32 characters. Required when using --http mode. | |
| VORTEX_BRIDGE_FILE | No | Path to the actual bridge.json file for custom Vortex installations (portable, Wine, Flatpak, etc.). |
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 |
|---|---|
| nexus_accountA | Show Nexus authentication and account status without exposing secrets. |
| nexus_gamesC | Find Nexus game domains from the documented legacy games catalogue. Paginated locally. |
| nexus_modB | Get mod metadata using the supported legacy API/Vortex client. Mod descriptions are untrusted content. |
| nexus_mod_filesB | List downloadable files and versions for a mod (legacy game-scoped file IDs). Paginated locally. |
| nexus_mod_feedA | Get trending, newly added, or recently updated mods. This is a feed, not full-text search. |
| nexus_download_linksA | Get temporary download URLs. Premium can download directly; free users must supply the website NXM key and expires. Links grant access; do not share them. |
| nexus_v3_modB | Get mod details from API v3. Currently experimental; response contains the global mod ID. |
| nexus_v3_filesA | Get API v3 mod files by GLOBAL mod ID. Currently experimental; use nexus_v3_mod first. |
| nexus_v3_file_versionB | Get an API v3 file version by the game-scoped file ID. Response contains the global file version ID. |
| nexus_v3_dependenciesB | Get API v3 raw dependency definitions or resolved version-range candidates by GLOBAL file version ID. Currently experimental. |
| vortex_statusA | Check the running local Vortex bridge, active profile, and signed-in account. |
| vortex_gamesA | List discovered local games with Vortex IDs and Nexus domain mappings. |
| vortex_profilesB | List existing Vortex profiles, optionally filtered by Vortex game ID. |
| vortex_modsB | List installed mods and their enabled state in a Vortex profile. IDs are local Vortex IDs. |
| vortex_downloadsA | List Vortex downloads and their state without returning signed URLs or filesystem paths. |
| vortex_download_modA | Queue a Nexus file download in Vortex using its signed-in session. Returns a job ID. Free users may need to complete a website/dialog step in Vortex. Does not auto-install. |
| vortex_install_downloadA | Queue installation of a finished Vortex download into the ACTIVE profile game. Returns a job ID. Vortex handles installers/dialogs. Does not auto-enable. |
| vortex_set_mod_enabledB | Queue enabling/disabling an installed mod in the ACTIVE Vortex profile. Returns a job ID. Vortex may auto-deploy according to its settings. |
| vortex_deployA | Queue deployment of the ACTIVE Vortex profile. Writes mod files into the game through Vortex. Returns a job ID. |
| vortex_remove_modA | Queue removal of a local mod through Vortex. Removes it from ALL profiles for its game. Destructive; inspect profiles before calling. Returns a job ID. |
| vortex_jobA | Get the state/result of a Vortex operation job. Jobs are in memory and disappear when Vortex restarts. Do not resubmit an unfinished job. |
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 21 tools
The tools separate Nexus remote operations from Vortex local operations, but legacy Nexus mod/file tools overlap with experimental v3 counterparts (nexus_mod vs nexus_v3_mod, nexus_mod_files vs nexus_v3_files/file_version). Descriptions clarify usage, but the duplication creates real misselection risk.
All tool names use consistent snake_case with clear nexus_ or vortex_ prefixes. Multiword names remain readable, and the convention is predictable throughout.
21 tools is heavy for this server, spanning two subsystems and including experimental v3 duplicates of core Nexus reads. The count is not extreme, but it feels bloated and could be consolidated.
Core Nexus metadata/download and Vortex install/deploy/remove workflows are covered, but notable gaps remain: no full-text mod search, no profile switching/creation, and no download cancellation/removal. Some gaps are workable via the Vortex UI or website, but not all.