Quantum OpenQASM MCP

Name: Quantum OpenQASM MCP
Author: markusvankempen

by markusvankempenversion 1.7.3i★ –iRuns on your computer

Registry nameio.github.markusvankempen/quantum-openqasm-mcp

Install

Overview

Description from the maker (original English)

IBM Quantum OpenQASM 2.0 MCP — list backends, submit QASM, poll jobs, get histograms.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: IBM_API_KEY, IBM_SERVICE_CRN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: IBM_API_KEY, IBM_SERVICE_CRN, IBM_QUANTUM_ENDPOINT, IBM_QUANTUM_BACKEND

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "quantum-openqasm": {
      "command": "npx",
      "args": [
        "-y",
        "@markusvankempen/quantum-openqasm-mcp"
      ],
      "env": {
        "IBM_API_KEY": "your-value",
        "IBM_SERVICE_CRN": "your-value",
        "IBM_QUANTUM_ENDPOINT": "your-value",
        "IBM_QUANTUM_BACKEND": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add quantum-openqasm --env IBM_API_KEY=your-value --env IBM_SERVICE_CRN=your-value --env IBM_QUANTUM_ENDPOINT=your-value --env IBM_QUANTUM_BACKEND=your-value -- npx -y @markusvankempen/quantum-openqasm-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "quantum-openqasm": {
      "command": "npx",
      "args": [
        "-y",
        "@markusvankempen/quantum-openqasm-mcp"
      ],
      "env": {
        "IBM_API_KEY": "your-value",
        "IBM_SERVICE_CRN": "your-value",
        "IBM_QUANTUM_ENDPOINT": "your-value",
        "IBM_QUANTUM_BACKEND": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "quantum-openqasm": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@markusvankempen/quantum-openqasm-mcp"
      ],
      "env": {
        "IBM_API_KEY": "your-value",
        "IBM_SERVICE_CRN": "your-value",
        "IBM_QUANTUM_ENDPOINT": "your-value",
        "IBM_QUANTUM_BACKEND": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

IBM_API_KEY secret required env
IBM Cloud API key for IBM Quantum Platform
IBM_SERVICE_CRN required env
IBM Quantum service instance CRN from quantum.ibm.com
IBM_QUANTUM_ENDPOINT env
IBM Quantum API endpoint (default: us-east)
IBM_QUANTUM_BACKEND env
Default backend name, e.g. ibm_fez

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account markusvankempen, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32744 servers in this category
Published to the registry more recently than 12% of the other 32744 servers in this category
Basic checks equal to or better than 100% of the other 32744 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Quantum OpenQASM MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: IBM_API_KEY, IBM_SERVICE_CRN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.7.3) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Date Math

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Date Math

by JowenDelaPena

Exact date/time math for agents: business days, holidays, time zones, cron, RRULE, SLA. x402 paid.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Quantum OpenQASM Assistant

Quantum OpenQASM Assistant is a VS Code extension and Model Context Protocol (MCP) server for IBM Quantum — submit OpenQASM 2.0 circuits to real quantum hardware and simulators from Cursor, VS Code, IBM Bob, and Google Antigravity. Includes Quantum Lab (interactive circuit editor), live job polling, measurement histograms, Bell state / GHZ examples, SamplerV2 REST integration, and one-click MCP setup for AI coding assistants.

Search terms: quantum computing · openqasm · qasm · ibm quantum · qiskit · quantum circuit · quantum hardware · mcp server · model context protocol · cursor mcp · vscode quantum · ai quantum assistant · quantum programming · qubit · bell state

Author: Markus van Kempen Email: markus.van.kempen@gmail.com · mvk@ca.ibm.com Website: markusvankempen.github.io *No bug too small, no syntax too weird.*

Overview

Quantum OpenQASM Assistant connects AI agents and developers to IBM Quantum through a pure TypeScript MCP server and VS Code extension. Submit OpenQASM 2.0 ISA circuits, poll job status, and view measurement histograms — locally via stdio or remotely via SSE on IBM Code Engine.

Product	Identifier	Version
VS Code Extension	`markusvankempen.quantum-openqasm-assistant`	1.9.2
NPM MCP Server	`@markusvankempen/quantum-openqasm-mcp`	1.9.2
MCP Registry	`io.github.markusvankempen/quantum-openqasm-mcp`	1.9.2
Public repo	quantum-openqasm-assistant	tag `v1.9.2` — docs & deployment guides only

Source code is maintained in the private dev repo quantum-openqasm-assistant-dev. Install the product via VS Code Marketplace or npm MCP — not by cloning this repo for extension source.

graph TB

subgraph clients [MCP Clients] Cursor[Cursor / VS Code] Bob[IBM Bob] AG[Antigravity] Lab[Quantum Lab Extension] end

subgraph mcp [MCP Server] Local["server.ts stdio"] Remote["server-sse.ts SSE"] end

IBM["IBM Quantum REST API SamplerV2 · OpenQASM 2.0"]

sequenceDiagram

participant User participant Ext as VS Code Extension participant MCP as MCP Server participant IBM as IBM Quantum API

User->>Ext: Submit .qasm circuit Ext->>MCP: submit_qasm_job MCP->>IBM: POST /jobs (SamplerV2) IBM-->>MCP: job id MCP-->>Ext: job id loop Poll every 15s Ext->>MCP: get_job_status MCP->>IBM: GET /jobs/{id} IBM-->>Ext: Queued → Running → Completed end Ext->>MCP: get_job_results MCP->>IBM: GET /jobs/{id}/results IBM-->>Ext: measurement histogram

📖 [Documentation hub → docs/README.md](./docs/README.md) · [Project structure → docs/PROJECT-STRUCTURE.md](./docs/PROJECT-STRUCTURE.md) · [OpenQASM Primer → docs/OPENQASM-PRIMER.md](./docs/OPENQASM-PRIMER.md) · [Tips & Tricks → docs/TIPS-AND-TRICKS.md](./docs/TIPS-AND-TRICKS.md) · [Architecture → docs/ARCHITECTURE.md](./docs/ARCHITECTURE.md) · [Local MCP setup → docs/ide/LOCAL-MCP-SETUP.md](./docs/ide/LOCAL-MCP-SETUP.md) · [Qiskit Developer Pack → docs/ide/QISKIT-DEVELOPER-PACK.md](./docs/ide/QISKIT-DEVELOPER-PACK.md) · [Deployment → docs/deployments/DEPLOYMENT-SCENARIOS.md](./docs/deployments/DEPLOYMENT-SCENARIOS.md) · [Extension → extension/README.md](./extension/README.md) · [Contributing → CONTRIBUTING.md](./CONTRIBUTING.md)

Repository policy: This public GitHub repo publishes overview and setup documentation. Extension source code, scripts, and examples live in the private dev repo (use .gitignore.private when setting it up).

Features

Feature	Description
Quantum Lab	Interactive OpenQASM panel with example circuits and histogram results
Qiskit Lab	Dedicated Qiskit Python panel — 12 templates, Aer sim, export to OpenQASM
AI Transpilation	`qiskit-ibm-transpiler` integration for hardware-native circuit optimization
OpenQASM 2.0	IBM hardware ISA format (`rz`, `sx`, `cz` native gates)
MCP tools	`list_backends`, `submit_qasm_job`, `get_job_status`, `get_job_results`, and more
Multi-IDE MCP	One-click setup for Cursor, VS Code, Bob, Antigravity & Claude Desktop
Qiskit Developer Pack	Bundle Qiskit MCP servers + quantum-openqasm-mcp from Diagnostics
Local / remote	stdio MCP locally or SSE via IBM Code Engine
Diagnostics	Test IAM auth, list backends, save credentials from the UI

MCP tools

Tool	Description
`list_backends`	Available IBM Quantum backends, status, queue
`get_backend`	Details for a specific backend
`submit_qasm_job`	Submit OpenQASM 2.0 circuit
`get_job_status`	Poll job state
`get_job_results`	Measurement counts / histogram data
`cancel_job`	Cancel a running job

Quick start

Prerequisites

Node.js 18+ (mise recommended — see mise.toml)
IBM Cloud API key + Quantum Service CRN — cloud.ibm.com/iam/apikeys

Build (private dev repo)

mise run install

mise run build

Configure

cp .env.example .env

IBM_API_KEY, IBM_SERVICE_CRN, IBM_QUANTUM_ENDPOINT, IBM_QUANTUM_BACKEND

Or use Quantum → Settings & Diagnostics in the extension.

Test

mise run test-e2e

or: Press F5 in VS Code → Quantum Lab → Run on Hardware

Install extension

mise run package

code --install-extension extension/quantum-openqasm-assistant-*.vsix

Architecture at a glance

quantum-openqasm-assistant/

├── extension/ # VS Code extension + bundled MCP server │ ├── src/extension.ts # Extension entry, MCP client │ ├── src/server.ts # Local stdio MCP server │ ├── src/server-sse.ts # Remote SSE MCP server │ └── out/ # esbuild output ├── packages/ │ └── quantum-openqasm-mcp/ # Standalone npm MCP package ├── scripts/ # MCP launcher, e2e tests, examples ├── docs/ # Published documentation │ └── QISKIT-INTEGRATION.md # Qiskit → OpenQASM → IBM Quantum ├── examples/ # Qiskit export script (public) ├── deployments/ # Client modes + infrastructure │ ├── README.md # Hub: 5 client modes + 6 infra scenarios │ ├── extension-only/ # Mode 1 │ ├── extension-mcp-local/# Mode 2 │ ├── mcp-npm/ # Mode 3 │ ├── extension-remote-mcp/# Mode 4 │ ├── mcp-remote-sse/ # Mode 5 │ ├── code-engine/ # IBM Code Engine │ ├── local-bridge/ # Dev gateway │ ├── docker-sse/ # Self-hosted │ ├── secured-remote/ # Auth tiers │ ├── wxo-orchestrate/ # Orchestrate agents │ └── ci-cd/ # Pipeline smoke tests └── Internal/ # Branding, publishing, status (gitignored)

See [docs/PROJECT-STRUCTURE.md](./docs/PROJECT-STRUCTURE.md) for the complete file map.

Documentation

Guide	Description
Documentation hub	Index of all published guides
Architecture	System design, MCP, IBM API flow
OpenQASM Primer	Learn OpenQASM 2.0 in plain English
Qiskit integration	Qiskit → export QASM → IBM hardware via MCP / Lab
Tips & Tricks	Backend selection, MCP workflows
Project structure	Complete repo layout
Extension README	VS Code extension features, commands
Local MCP setup	Cursor, VS Code, Bob, Antigravity
Deployment hub	5 client modes + infra (CE, Docker, WxO, CI)
Deployment scenarios	Local, Code Engine, Docker, hybrid

Qiskit Integration

Design circuits in Qiskit (or the built-in Qiskit Lab panel), export to OpenQASM 2.0, transpile with AI-powered `qiskit-ibm-transpiler`, and run on IBM Quantum hardware:

from qiskit import QuantumCircuit, qasm2

qc = QuantumCircuit(2, 2) qc.h(0) qc.cx(0, 1) qc.measure([0, 1], [0, 1])

print(qasm2.dumps(qc)) # → submit via MCP or paste into Quantum Lab

OPENQASM 2.0;

include "qelib1.inc"; qreg q[2]; creg c[2]; h q[0]; cx q[0],q[1]; measure q[0] -> c[0]; measure q[1] -> c[1];

No Qiskit dependency at runtime — the MCP server speaks OpenQASM + IBM Quantum REST directly.

v1.9.2 Qiskit features:

Qiskit Lab — 12 templates (Bell, GHZ, Grover, teleportation, VQE ansatz, QAOA, …), local Aer sim, one-click export
AI transpilation — qiskit-ibm-transpiler MCP integration for hardware-native optimization
`quantum-assistant` MCP — streamlined MCP key for AI IDE setup

Full guide: docs/QISKIT-INTEGRATION.md
Qiskit Developer Pack (Qiskit MCP + AI transpiler + OpenQASM): [docs/ide/QISKIT-

Only the beginning is shown; read the rest in the repo

Quantum OpenQASM MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Date Math

README from the maker

Quantum OpenQASM Assistant

Overview

Features

MCP tools

Quick start

Prerequisites

Build (private dev repo)

Configure

IBM_API_KEY, IBM_SERVICE_CRN, IBM_QUANTUM_ENDPOINT, IBM_QUANTUM_BACKEND

Test

or: Press F5 in VS Code → Quantum Lab → Run on Hardware

Install extension

Architecture at a glance

Documentation

Qiskit Integration