Skip to main content
Glama
PHLemp

nexus-mods-mcp

by PHLemp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nexus-mods-mcp

No user-submitted related servers found.

    Related Servers

    • ModWrench MCP Server

      171county
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • modrinth-mcp

      justinscott12
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search, read, and publish Minecraft mods on Modrinth, including creating projects and uploading jar files as new versions.
      7
      45 npm
      MIT

    • nexus-mcp

      Talya1412
      A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      135
      1
      MIT

    • modrinth-kit

      TejasLamba2006
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to manage Modrinth projects and organizations, upload versions, edit pages and galleries, view analytics, and interact with moderators, with safety controls for destructive actions.
      686 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 22 tools

    Disambiguation4/5

    There is real overlap: nexus_get_mod vs nexus_mod_overview, nexus_get_mod_files, and nexus_get_mod_changelogs all target the same mod resource, and nexus_find_mods vs nexus_list_mods vs nexus_graphql all cover search/discovery. The descriptions work hard to disambiguate ('prefer this over chaining', 'narrow follow-up tool', 'START HERE'), which largely resolves the boundaries for an attentive agent.

    Naming Consistency4/5

    Every tool uses a consistent nexus_ snake_case prefix with mostly verb_noun patterns (nexus_find_mods, nexus_upload_mod_file, nexus_endorse_mod). A few are noun-only (nexus_mod_overview, nexus_upload_status, nexus_mod_file_targets), a minor deviation but still readable and predictable.

    Tool Count4/5

    22 tools sits at the upper edge of the comfortable band, but each maps to a distinct capability across auth, discovery, mod lifecycle, uploads/publishing, and a GraphQL escape hatch. The upload chain (targets → upload → status → publish) justifies several tools, though a few read-only report tools could arguably be merged.

    Completeness5/5

    The surface is unusually thorough: authentication, quota checks, game/category resolution, search (name, MD5, feeds), mod metadata and files, changelogs, endorsements, tracking, the full upload/publish/recover workflow, file rename, and a documented GraphQL escape hatch. No obvious lifecycle gaps or dead ends for managing mods on Nexus.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources