ComputeNexa MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CNX_API_KEY | Yes | Required. A ComputeNexa API key (cnxk_…) | |
| CNX_API_URL | No | Only for testing against another ComputeNexa API | |
| CNX_MCP_MAX_LAUNCH_USD | No | Most one call may spend, in US dollars. Default 25 | 25 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Who this server's API key acts as: email, team and role, the team's balance and GPU limit, and whether the key may launch and stop machines. |
| list_gpusA | GPUs with live prices (US dollars per GPU per hour) and stock, cheapest first. |
| list_appsA | The apps a GPU can start with (basic, datascience, chat, imagegen, modelapi, voice): what each is for, the
models it offers and which model we recommend per GPU memory. Give |
| list_machinesB | Your machines, newest first: state, GPU, app, price, time left and cost so far. |
| get_machineA | One machine: its state, how to connect (SSH command, browser apps, API or endpoint address), time left, keep-running status and costs. Never its keys. |
| get_usageB | Spending and GPU-hours over the last N days, by GPU, app, day and project. |
| list_receiptsB | Finished sessions and what each cost in the end (charged minus refunded). |
| list_projectsB | Saved projects (files restored into ~/work on machines launched with them) and their size. |
| list_endpointsA | Endpoints: stable HTTPS addresses for your own server on a machine's port 8000, and the machine each points at now. Never their keys. |
| launch_machineA | Launch a GPU machine. Costs money: call first with confirm=false to get a quote (nothing happens), show it to the person, and only after they agree call again with the same arguments, confirm=true and expected_total_usd. The booked time is charged up front from the team's balance. |
| extend_machineA | Add time to a machine at the price it launched with. Costs money: quote first (confirm=false), then confirm=true with expected_total_usd once the person agrees. |
| set_keep_runningA | Keep running: the machine renews itself |
| stop_machineA | End a machine now: stopped if running, cancelled with a full refund if still starting. Files outside a project are deleted; a project is saved first. Unused time is refunded. Can't be undone. |
| create_endpointA | A new Endpoint (owners and admins): a stable HTTPS address and key for your own server on port 8000, e.g. one per customer you serve. Launch machines for it with launch_machine(endpoint=...). Free. Its key is shown once here; get_endpoint_key shows it again. |
| get_endpoint_keyA | An Endpoint's key (owners and admins). Only when the person asks for it: it gives access to their server. |
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 15 tools
Each tool targets a distinct resource or lifecycle action: GPUs/apps discovery, machine launch/list/get/extend/stop/keep-running, endpoints, projects, usage, receipts, and identity. The potentially closest pair, extend_machine and set_keep_running, is clearly separated by one-off time extension versus automatic renewal, with both having explicit confirmation semantics.
Nearly all tools follow a snake_case verb_noun pattern such as list_machines, get_machine, launch_machine, stop_machine, create_endpoint, and get_endpoint_key. whoami is the lone conventional outlier, and set_keep_running is slightly more phrasal, but the naming remains predictable overall.
Fifteen tools fit the server's scope well: discovery, machine lifecycle, spending, projects, endpoints, and identity each contribute a small set of operations. No obvious redundant tools inflate the surface, and the set stays within a manageable range.
Core GPU machine workflows are well covered: discovering GPUs/apps, launching, inspecting, extending, stopping, and checking costs. However, projects expose only list_projects with no create/get/delete lifecycle, and endpoints expose create/list/get-key but no delete or revoke operation, leaving notable dead ends for resource management.