Skip to main content

ComputeNexa MCP server

Let your AI assistant find, launch and stop private GPUs on ComputeNexa. Ask it "Which GPUs with 48 GB or more are in stock?", "Launch the cheapest one with Data Science for two hours" or "Stop it": it uses your team's API key, shows you what each launch costs, and only spends money after you agree.

Works with Claude Desktop, Claude Code, Cursor, VS Code and other assistants that support the Model Context Protocol. It runs on your computer and talks to the ComputeNexa API; your key stays in your own settings.

Set up

  1. In the ComputeNexa dashboard, open API keys and create a key:
    • Look only to browse GPUs, machines and spending;
    • Launch and stop to also launch, extend and stop machines.
  2. Install uv (it runs the server with uvx, no separate install needed).
  3. Add the server to your assistant (below), with your key as CNX_API_KEY.

Claude Code

claude mcp add --env CNX_API_KEY=cnxk_... --transport stdio computenexa -- uvx computenexa-mcp

Add --scope user to use it in every project.

Claude Desktop

Settings → Developer → Edit config (claude_desktop_config.json):

{
  "mcpServers": {
    "computenexa": {
      "command": "uvx",
      "args": ["computenexa-mcp"],
      "env": { "CNX_API_KEY": "cnxk_..." }
    }
  }
}

Cursor

~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project): the same mcpServers entry as Claude Desktop.

VS Code

.vscode/mcp.json; VS Code asks for the key once and keeps it out of the file:

{
  "inputs": [
    { "type": "promptString", "id": "cnx-key", "description": "ComputeNexa API key", "password": true }
  ],
  "servers": {
    "computenexa": {
      "type": "stdio",
      "command": "uvx",
      "args": ["computenexa-mcp"],
      "env": { "CNX_API_KEY": "${input:cnx-key}" }
    }
  }
}

What it can do

Tool What it does Key
whoami Your email, team, balance, GPU limit and the key's permissions any
list_gpus GPUs with live prices and stock, cheapest first; filter by app, region, memory any
list_apps The apps a GPU starts with, their models, and what's installed any
list_machines · get_machine Your machines; how to connect (SSH, browser apps, API or endpoint address) any
get_usage · list_receipts Spending and GPU-hours; finished sessions and their cost any
list_projects · list_endpoints Saved projects; Endpoints and the machine each points at any
launch_machine Launch a GPU (quote first, then launch when you agree) launch and stop
extend_machine Add time (quote first) launch and stop
set_keep_running Renew a machine automatically until stopped (quote first) launch and stop
stop_machine End a machine now; unused time is refunded launch and stop
create_endpoint · get_endpoint_key A stable HTTPS address for your own server; its key launch and stop

A look-only key only gets the read tools (the first six rows).

Safety

  • Nothing is charged without you. launch_machine, extend_machine and set_keep_running first return a quote, e.g. "NVIDIA RTX A6000 with the datascience app for 2 h: $1.44 charged now ($0.72/h); unused time is refunded if it stops early." Only a second call with confirm=true and the quoted total goes ahead; if the price went up in between, it's refused.
  • A limit per call: a launch, extension or keep-running renewal costing more than $25 is refused. Change it with CNX_MCP_MAX_LAUNCH_USD (in dollars) in the server's env. Your team's GPU limit and prepaid balance still apply on top.
  • Your API key never appears in a tool result. Endpoint keys are shown only when you create an endpoint or ask for its key.
  • Tools that spend money or end a machine are marked as such, so your assistant asks before using them.

Settings

Variable
CNX_API_KEY Required. A ComputeNexa API key (cnxk_…)
CNX_MCP_MAX_LAUNCH_USD Most one call may spend, in US dollars. Default 25
CNX_API_URL Only for testing against another ComputeNexa API

Develop

uv sync
uv run pytest
uv run ruff check src tests

Built on the ComputeNexa Python SDK and the official MCP Python SDK.

Questions: support@computenexa.com · Security issues: see SECURITY.md.

Metadata

Release files for computenexa-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for computenexa-mcp 0.1.0
File Size Uploaded Provenance Actions
computenexa_mcp-0.1.0.tar.gz 104.7 kB With provenance Details for computenexa_mcp-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for computenexa-mcp 0.1.0
File Interpreter ABI Platform Actions
computenexa_mcp-0.1.0-py3-none-any.whl Python 3 none any Details for computenexa_mcp-0.1.0-py3-none-any.whl

Total release size: 125.2 kB

Release files / computenexa_mcp-0.1.0.tar.gz

Download URL computenexa_mcp-0.1.0.tar.gz
Size 104.7 kB
Tags Source
SHA-256 checksum
How to use checksums
f6cfebbe5bb24e3ab5c0315bcf6e65121a337453c2f9147c23ab6dbfa2039629
BLAKE2b-256 checksum
How to use checksums
cc523ec293a3af52379ee3d35528f6208b33e07276c670bf25b3ea745ee3a85b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Release files / computenexa_mcp-0.1.0-py3-none-any.whl

Download URL computenexa_mcp-0.1.0-py3-none-any.whl
Size 20.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ba2fc2cf2ff3b834ffb584297c22604db4e98027e94792f109596456fd5bb45e
BLAKE2b-256 checksum
How to use checksums
ea456411b5ee589fdc5808132c8cafb15d714c02ed4309d01114cbe862e35d1f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Security for computenexa-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for computenexa_mcp-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page