nexus-mcp
Related Servers
Alternatives to nexus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP clients to browse the Nexus Mods catalogue and manage a local Vortex installation by reusing the user's existing Vortex login, including queuing download, install, enable/disable, deploy, and removal operations with job polling.21MIT
- 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 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
- 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-
- 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 gradedqualityCmaintenanceEnables MCP clients to search and retrieve Modrinth projects, versions, dependencies, users, and tags through trimmed, agent-friendly API responses.MIT
TDQS
Scored across 135 tools
Several clusters of tools have nearly identical purposes: mod file listings (nexus_get_mod_files, nexus_get_files_v2, nexus_get_files_by_uid), MD5 lookups (nexus_search_by_md5, nexus_get_file_hash, nexus_get_file_hashes), and exact user lookups (nexus_get_user_v2, nexus_get_user_by_name). The descriptions are thorough and often point out differences, but agents must read carefully to avoid mis-selecting, and v1/v2 duplicates create genuine boundary ambiguity.
Almost every tool follows a nexus_verb_noun snake_case pattern, and subdomain prefixes like oauth_ and graphql_ are internally consistent. Minor deviations from strict verb-first structure and inconsistently applied _v2 suffixes prevent a perfect score.
135 tools is an extreme count by any MCP standard, far above the 50+ threshold for a mismatch. Even for a broad platform API, this creates severe navigation and selection burden and would be better split into focused servers or consolidated tool groups.
The surface covers lifecycle operations for mods, files, collections, revisions, comments, tags, users, preferences, OAuth, moderation, and more, plus a raw GraphQL introspect/query escape hatch. There are no obvious dead ends for the domain this server targets.