Qnexus-mcp Server

MCP server for Quantinuum Nexus, wrapping the qnexus SDK. Not affiliated with Quantinuum.

Local serverstdio

What is the Qnexus-mcp Server?

Qnexus-mcp is an MCP integration. MCP server for Quantinuum Nexus, wrapping the qnexus SDK. Not affiliated with Quantinuum.

Packages and local setup

The published pypi package is qnexus-mcp, version 0.2.0. Its declared MCP transport is stdio.

The package declares QNEXUS_MCP_TOOLSETS: Comma-separated toolsets: read,execute,manage,destructive (default: read).; QNEXUS_MCP_ALLOW_SPEND: Permit credit-spending (HQC) execution (default: false).; QNEXUS_MCP_ALLOW_HARDWARE: Permit real-QPU targets (default: false).; QNEXUS_MCP_ALLOW_DESTRUCTIVE: Permit delete/cancel/archive tools (default: false).; QNEXUS_MCP_MAX_CREDITS: Hard per-call HQC ceiling; 0 blocks all spend (default: 0).; QNEXUS_MCP_MAX_OUTCOMES: Top-N cap on distinct measurement outcomes returned per result item (default: 100).; QNEXUS_MCP_MAX_SUBMISSIONS_PER_MINUTE: Sliding-window submission cap; each circuit in a batch counts as one (default: 6).; QNEXUS_MCP_PROJECTS: Comma-separated project allowlist, enforced on every mutating tool (default: all projects)..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
QNEXUS_MCP_TOOLSETSComma-separated toolsets: read,execute,manage,destructive (default: read).Optional
QNEXUS_MCP_ALLOW_SPENDPermit credit-spending (HQC) execution (default: false).Optional
QNEXUS_MCP_ALLOW_HARDWAREPermit real-QPU targets (default: false).Optional
QNEXUS_MCP_ALLOW_DESTRUCTIVEPermit delete/cancel/archive tools (default: false).Optional
QNEXUS_MCP_MAX_CREDITSHard per-call HQC ceiling; 0 blocks all spend (default: 0).Optional
QNEXUS_MCP_MAX_OUTCOMESTop-N cap on distinct measurement outcomes returned per result item (default: 100).Optional
QNEXUS_MCP_MAX_SUBMISSIONS_PER_MINUTESliding-window submission cap; each circuit in a batch counts as one (default: 6).Optional
QNEXUS_MCP_PROJECTSComma-separated project allowlist, enforced on every mutating tool (default: all projects).Optional