Nexus Mods MCP
Related Servers
Alternatives to Nexus Mods MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables any MCP client to search, browse, download, and manage Nexus Mods content—games, mods, files, comments, collections, and user preferences—through a unified REST and GraphQL interface with caching and OAuth2 support.13540 PyPI1MIT
- FlicenseBqualityBmaintenanceEnables interacting with Nexus Mods: search and download mods, manage endorsements and uploads, and use a browser session for comments, forums, and private messages.57-
- AlicenseNot gradedqualityDmaintenanceA local MCP server for Nexus Mods mod discovery, research, and downloading, backed by the v2 GraphQL API and the website's DownloadPopUp widget.73 npm2MIT
- FlicenseAqualityAmaintenanceExposes the Nexus Mods API to AI agents so they can search and inspect mods, browse authors' catalogues, and upload or publish mod files from a local archive in a few aggregated tool calls. It handles authentication, caching, reporting quotas, and the multi-step v3 upload flow, while gating write and publish operations behind opt-in permissions.22-
- AlicenseNot gradedqualityCmaintenanceA local MCP server for Nexus Mods mod discovery and research, backed by the v2 GraphQL API, enabling search of games, mods, collections, and users.73 npm1ISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to search, browse, and manage mods across Nexus Mods, mod.io, Thunderstore, and Modrinth, as well as perform local diagnostics like detecting games and parsing crash logs.MIT
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.