Quantum OpenQASM MCP Server

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

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.

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 -- npx -y @markusvankempen/quantum-openqasm-mcp

{
  "mcpServers": {
    "quantum-openqasm-mcp": {
      "args": [
        "-y",
        "@markusvankempen/quantum-openqasm-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.quantum-openqasm-mcp]
command = "npx"
args = ["-y", "@markusvankempen/quantum-openqasm-mcp"]

{
  "mcpServers": {
    "quantum-openqasm-mcp": {
      "args": [
        "-y",
        "@markusvankempen/quantum-openqasm-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "quantum-openqasm-mcp": {
      "args": [
        "-y",
        "@markusvankempen/quantum-openqasm-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: IBM_API_KEY (IBM Cloud API key for IBM Quantum Platform), IBM_SERVICE_CRN (IBM Quantum service instance CRN from quantum.ibm.com), IBM_QUANTUM_ENDPOINT (IBM Quantum API endpoint (default: us-east)), IBM_QUANTUM_BACKEND (Default backend name, e.g. ibm_fez). The author declared them in the registry entry; get the values from the project itself.