nexusmods-mcp-server
Related Servers
Alternatives to nexusmods-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceExposes 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 gradedqualityBmaintenanceEnables 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
- 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
- AlicenseNot gradedqualityCmaintenanceA local MCP server for Nexus Mods mod discovery, research, and downloading, backed by the v2 GraphQL API and the website's DownloadPopUp widget.79 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI agents to search, read, and publish Minecraft mods on Modrinth, including creating projects and uploading jar files as new versions.742 npmMIT
- 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.79 npm1ISC
TDQS
Scored across 57 tools
Most tools are clearly grouped by resource and action, but get_mod and get_mod_details both read as generic mod-info lookups, and get_mod_files/get_mod_file/get_mod_file_versions/get_upload_targets are easy to confuse despite different id systems. graphql_query also overlaps with every typed read tool, though the description advises preferring typed tools.
The majority of tools follow a clear snake_case verb_noun pattern like get_mod, list_games, delete_collection_comment, and track_mod. There are minor deviations such as md5_lookup, forum_list, forum_topic, web_status, and pm_list/pm_read, plus get_mod_bug vs get_mod_bugs plural inconsistency, but the conventions are still mostly predictable.
With 57 tools, this server far exceeds the 25+ threshold and presents a heavy selection burden, even though the tools cover many Nexus Mods subdomains. The surface could be better scoped by consolidating related web-session, PM, and media tools into smaller grouped tools.
The server covers a remarkably broad domain: mod browsing, search, files, downloads, tracking, endorsements, comments, bugs, collections, forums, PMs, media, uploads, and changelogs. Minor gaps exist such as collection creation/editing and bug-status updates, but agents can generally accomplish end-to-end workflows without dead ends.