NexusAPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEXUS_API_KEY | Yes | Your NexusAPI key. Obtain from NexusAPI and keep it in the server environment. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nexusapi_list_modelsA | List the models currently exposed by the public NexusAPI catalog, optionally filtered by kind or search text. |
| nexusapi_get_model_schemaA | Read the live OpenAPI parameter schema for one NexusAPI model id before constructing a generation request. |
| nexusapi_generateA | Create a paid asynchronous generation task. Call nexusapi_get_model_schema first and ask the user to approve potentially billable generation. |
| nexusapi_get_taskA | Get the status, result or error of a previously created NexusAPI generation task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
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.
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.
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.
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.