Quantum OpenQASM MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 60 installs a week from npm. Last commit 26 Jun 2026.
IBM Quantum OpenQASM 2.0 MCP — list backends, submit QASM, poll jobs, get histograms.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node dist/postinstall.js
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add quantum-openqasm-mcp -e 'IBM_API_KEY=<IBM_API_KEY>' -e 'IBM_SERVICE_CRN=<IBM_SERVICE_CRN>' -- npx -y @markusvankempen/quantum-openqasm-mcp{
"mcpServers": {
"quantum-openqasm-mcp": {
"command": "npx",
"args": [
"-y",
"@markusvankempen/quantum-openqasm-mcp"
],
"env": {
"IBM_API_KEY": "<IBM_API_KEY>",
"IBM_SERVICE_CRN": "<IBM_SERVICE_CRN>"
}
}
}
}[mcp_servers.quantum-openqasm-mcp]
command = "npx"
args = ["-y", "@markusvankempen/quantum-openqasm-mcp"]
env = { IBM_API_KEY = "<IBM_API_KEY>", IBM_SERVICE_CRN = "<IBM_SERVICE_CRN>" }{
"mcpServers": {
"quantum-openqasm-mcp": {
"command": "npx",
"args": [
"-y",
"@markusvankempen/quantum-openqasm-mcp"
],
"env": {
"IBM_API_KEY": "<IBM_API_KEY>",
"IBM_SERVICE_CRN": "<IBM_SERVICE_CRN>"
}
}
}
}{
"servers": {
"quantum-openqasm-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@markusvankempen/quantum-openqasm-mcp"
],
"env": {
"IBM_API_KEY": "<IBM_API_KEY>",
"IBM_SERVICE_CRN": "<IBM_SERVICE_CRN>"
}
}
}
}Put your own values in place of
<IBM_API_KEY> (IBM Cloud API key for IBM Quantum Platform), <IBM_SERVICE_CRN> (IBM Quantum service instance CRN from quantum.ibm.com).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
IBM_QUANTUM_ENDPOINT (IBM Quantum API endpoint (default: us-east)), IBM_QUANTUM_BACKEND (Default backend name, e.g. ibm_fez).
Alternatives to Quantum OpenQASM MCP
same job, measured the same wayOpenQASM 3 programs run, checked against their intent and signed on this machine.
UpRes MCP: list models, credits, submit 4K image and video upscale jobs.
Open jobs from 20,000+ company career sites: search, list a company's roles, read full job ads
Corduroy Labs studio updates over MCP: list_updates and get_update, backed by the site's JSON Feed.
Compacting proxy for OpenAI-compatible backends, with MCP tools to search the archived history.
MCP server for AI Transpiler IBM Quantum services
MCP server for subscription tracker ai. Features add subscription, get total spend, list
OQMD (Open Quantum Materials Database) MCP.
Quantum OpenQASM MCP — questions
Answers built from our own checks of this server.