quantum-vibecoding-mcp
Model Context Protocol servers that let Claude run real quantum experiments on real hardware through natural language.
Three servers ship in one package:
| Command | What it does | Backend |
|---|---|---|
qvc-qi |
Submit cQASM 3.0 circuits, poll jobs, fetch histograms | Quantum Inspire (Tuna-9, emulator) |
qvc-ibm |
Run circuits on IBM Quantum processors | IBM Quantum (Heron, Eagle, etc.) |
qvc-qrng |
Generate true quantum random numbers | QI Tuna-9 + ANU fallback |
Install
The recommended path uses uvx — no manual install needed.
Claude Code (CLI / Desktop)
Add to your .mcp.json (project-level) or ~/.claude.json (global):
{
"mcpServers": {
"qi-circuits": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "quantum-vibecoding-mcp[qi]", "qvc-qi"]
}
}
}
For all three servers:
{
"mcpServers": {
"qi-circuits": {
"command": "uvx",
"args": ["--from", "quantum-vibecoding-mcp[qi]", "qvc-qi"]
},
"ibm-quantum": {
"command": "uvx",
"args": ["--from", "quantum-vibecoding-mcp[ibm]", "qvc-ibm"]
},
"qrng": {
"command": "uvx",
"args": ["--from", "quantum-vibecoding-mcp[qi]", "qvc-qrng"]
}
}
}
Manual install
pip install "quantum-vibecoding-mcp[all]"
qvc-qi # then point claude at this binary
Authentication
| Backend | How |
|---|---|
| Quantum Inspire | Run qi login once — opens a browser, stores creds in ~/.quantuminspire/config.json |
| IBM Quantum | Set IBM_QUANTUM_TOKEN env var (get one at quantum.ibm.com) |
Hello world
After config, prompt Claude:
Submit a Bell-state circuit to QI's local emulator with 1024 shots and show me the histogram.
Claude calls qi_run_local, you see {"00": ~512, "11": ~512}.
Tools
qvc-qi exposes: qi_list_backends, qi_submit_circuit, qi_check_job, qi_get_results, qi_run_local.
qvc-ibm exposes: ibm_list_backends, ibm_submit_circuit, ibm_check_job, ibm_get_results.
qvc-qrng exposes: quantum_random_int, quantum_coin_flip, quantum_random_hex, quantum_dice_roll, and friends.
Hardware notes
Tuna-9 (Quantum Inspire) native gate set: CZ, Ry, Rz, X. Pass compile_stage="routing" to let QI's compiler decompose for you.
Bitstrings are MSB-first across the board — qubit 0 is the leftmost character. See the Quantum Vibecoding paper §3.4 for the conventions and silent-bug list.
Development
git clone https://github.com/JDerekLomas/quantuminspire.git
cd quantuminspire/mcp-servers
pip install -e ".[all]"
License
MIT.
Metadata
Release files for quantum-vibecoding-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)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| quantum_vibecoding_mcp-0.1.0.tar.gz | 10.9 kB | Without provenance | Details for quantum_vibecoding_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| quantum_vibecoding_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for quantum_vibecoding_mcp-0.1.0-py3-none-any.whl |
Total release size: 24.7 kB
Release files / quantum_vibecoding_mcp-0.1.0.tar.gz
| Download URL | quantum_vibecoding_mcp-0.1.0.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67f9a6be90998f40c63ee0eb1ffaf9ed9a384c99a144007cf8f20134ddc7bd4c
|
|
BLAKE2b-256 checksum How to use checksums |
130730d8a9ca4cd7bd707a11ef9023c3f445127358b2258726f1d88c73b26455
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Release files / quantum_vibecoding_mcp-0.1.0-py3-none-any.whl
| Download URL | quantum_vibecoding_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c51812ff43ff8f300320dd557bf5bb8ff4fd8817f4c771e8838aeb83125b6cc9
|
|
BLAKE2b-256 checksum How to use checksums |
28e135ef5eda07e2f5ff4f42749c50a2f997fe2dec1529cba2f7d13450792214
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Security for quantum-vibecoding-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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.