Skip to main content
Glama
mat12121212

NexusAPI MCP Server

by mat12121212
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to NexusAPI MCP Server

No user-submitted related servers found.

    Related Servers

    • nexus

      bobuilds
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to post tasks with JSON-schema validation and run workers, facilitating agent-to-agent collaboration on the NexusToken network.
      85 PyPI
      1
      MIT

    • nexus-mods-mcp

      PHLemp
      F
      license
      A
      quality
      B
      maintenance
      Exposes 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
      -

    • Nexus MCP Server

      iamserge
      F
      license
      B
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with Nexus projects, allowing management of projects, bugs, milestones, concepts, and templates through natural language commands.
      20
      -

    • nexus-mcp

      tanakorncode
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to read and update tasks in the Nexus/TaskBridge project management system through its public API.
      109 npm
      ISC
    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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct stage of the workflow: listing models, inspecting schemas, creating generation tasks, and retrieving task results. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent pattern: the 'nexusapi_' prefix followed by a verb_noun combination (list_models, get_model_schema, generate, get_task). This is uniform and predictable.

    Tool Count5/5

    Four tools is well-scoped for the server's purpose of managing generation tasks. Each tool is necessary and there are no redundant or missing tools.

    Completeness4/5

    The tool set covers the core workflow: discover models, inspect schema, generate, and fetch results. A minor gap is lack of a cancel or delete task operation, but the essential lifecycle is covered.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources