Quantum Hardware MCP logo

Quantum Hardware MCP

Unclaimed

by Lokesh-2025

Open-source MCP server giving AI assistants live, natural-language control of real quantum hardware across IBM Quantum, IonQ, and AWS Braket

Install

$/absolute/path/to/.venv/bin/python /absolute/path/to/quantum-hardware-mcp/server.py

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
aiclaudegithub-actionsibm-quantummcpmodel-context-protocolpythonquantum

More in AI & ML

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

40 of 40 tools

Documented tools (40)

From project documentation. A server handshake does not verify each tool’s description or behavior.

analyze_molecule

Builds the qubit Hamiltonian from atom positions and reports how far entanglement forging and Pauli grouping cut the problem down — plus the accuracy floor at each truncation rank

best_qubits

Score and rank qubits by calibration quality — actually searches for a connected subset of the requested size, not just the top-n by score (falls back to warn-only if no connected subset of that size exists at all)

build_forged_circuits

Emits the actual OpenQASM circuits for a forged ground-state calculation — each acting on half the qubits the molecule would otherwise need — plus a simulator self-check confirming they reconstruct the right energy

cancel_job

Cancel a queued or running job

check_chip_identity

Detects a silent hardware swap or qubit relabeling — the physical chip behind a device name changed, or its qubit indices got reassigned, neither of which any public API states directly. Built on a real per-qubit/per-pair calibration archive (qubitsnapshots/pairsnapshots), backfilled from IBM's own

check_routing_overhead

Input: qubit interaction pairs → detects degree>3 nodes → predicts SWAP flood and gate inflation before it happens. Learned from Phase 4: degree-4 node caused 263→1,037 gate explosion.

circuit_report

Full dry-run: gate counts, qubit mapping, per-pair CX errors, estimated fidelity

collect_forged_energy

Fetches the finished jobs and reconstructs the molecular energy, compared against the exact classical answer

compare_devices

Rank by CX error, queue depth, qubit count, or combined score — only ranks devices whose real status is "active"; anything else is reported separately in unavailabledevices, never accidentally top-ranked

debug_circuit

Pre-submission check: missing measurements, decoherence violations, qubit mismatches

device_history

Calibration snapshots over the last N days

device_on_date

Exact calibration state on any past date — for paper reproducibility

encode_4way_collision

Takes a value + sieve positions, builds one LNAA rail per k-column, searches all simultaneously in one hardware job

encode_search_problem

Input: Boolean conditions like {"1":1, "4":0} → derives Ising hi and Jij coefficients with full sign derivation and QAOA circuit recipe. The math behind Phase 5's 27.78× result.

equality_oracle_search

Two-register LNAA — amplifies (n1, n2) pairs matching a Lucas mod-2 parity oracle (cross-register RZZ), without being told which rows to look for. Parity match is a weak, ~50%-hit-rate filter, not proof of equality — classical post-processing (comb()) checks every measured pair for true equality. Co

estimate_circuit_error_ceiling

Bounds the error on any observable from one fidelity number, so you can tell before running whether a job can possibly reach chemical accuracy

estimate_expectation

Estimator primitive: computes ⟨ψ\

estimate_hardware_gates

Predicts transpiled gate count from logical gates + max qubit degree. Knows the empirical ~600-gate noise floor on ibmmarrakesh.

estimate_runtime

QPU minutes + queue wait estimate before you submit

find_collision_candidates

Curve intersection search — integer root-finding across column pairs to jump directly to candidate rows

get_alerts

Calibration drift alerts — spikes >20% in CX error, readout error, T1, or T2. The T1/T2 check reads live from the shared Turso database (2026-08-30) when configured, same one quantum-verifier uses, so this reflects real current state regardless of whose laptop last synced — falls back to the local d

get_amplification

Input: job ID + marked bitstrings → amplification factor, per-state shot breakdown, verdict (EXCELLENT/GOOD/WEAK/FAILED).

get_device_details

Per-qubit T1/T2, readout error, gate error, queue depth

job_results

Bit-string measurement counts from a completed job

job_status

QUEUED / RUNNING / DONE / ERROR

list_devices

All accessible IBM backends with live operational status

list_jobs

Recent jobs with status, backend, and timestamps

plan_quantum_chemistry_run

Given a molecule and a budget, works out the most accurate result you can actually buy: Schmidt rank, circuit count, cost, expected error

queue_status

Current queue snapshot across all backends

recommend_error_mitigation

Which mitigation techniques are worth applying for a given circuit and device noise — including the ones measured not to help, so you skip them

repro_score

KL-divergence reproducibility score (0 = identical, 1 = maximally different)

route_job

Credit-aware routing — cheapest backend that meets your error threshold

run_forged_energy

Builds the circuits and submits them to a named device via submitjob, returning ordered job IDs

run_grover

Full Grover's search — builds oracle + diffusion operator, picks least-busy backend, submits

run_vqe

Variational Quantum Eigensolver — H2 ground state to chemical accuracy

sieve_singmaster_space

Classical Lucas theorem sieve — filters 98%+ of Pascal's Triangle search space before touching the QPU

start_repro_experiment

Run the same circuit N times, record variance across runs

submit_job

Transpile and submit OpenQASM 2.0 or 3.0 — returns jobid

verify_stabilizer_circuit

Exact measurement distribution for any Clifford-only circuit (H, S, CX, CZ, ...) via the stabilizer tableau — not simulated, not estimated, exact, and scales to hundreds of qubits (Gottesman-Knill theorem). Confirmed: a 150-qubit Clifford circuit verifies in under a second, where state-vector simula

verify_stabilizer_hardware_result

Verifies real hardware measurement counts against a Clifford circuit's exact stabilizer prediction — a real fidelity lower bound at any qubit count, no simulation required

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Quantum Hardware MCP Server

How do I connect Quantum Hardware MCP Server to Claude?
The listing records `/absolute/path/to/.venv/bin/python /absolute/path/to/quantum-hardware-mcp/server.py` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop as compatible clients.
Is Quantum Hardware MCP Server free?
The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Quantum Hardware MCP Server do?
Quantum Hardware MCP Server documents 40 tools to the agent, including analyze_molecule, best_qubits, build_forged_circuits. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.