run_circuitLABSCO SUMMARY
Circuits run and plotted without leaving the conversation.
Qiskit, a noise model and a histogram normally mean a notebook and a kernel. Here the circuit goes in as QASM and the result comes back as counts or an image file, which makes it practical for teaching, quick checks and comparing a clean run against a noisy one.
What it is
A Qiskit-based quantum circuit simulator packaged as a Docker image that speaks MCP, so circuits are submitted and results returned inside the conversation.
What you get
- OpenQASM 2.0 circuits executed against the Qiskit simulator
- Noise applied deliberately: depolarizing, thermal relaxation and readout error models, each listed with its description
- Several result types — measurement counts, statevector, or a visualised histogram written to your mounted output directory
- Circuit statistics without running it, when the question is about depth and gate composition rather than outcomes
- Example circuits shipped as resources: Bell state, 2-qubit Grover, 4-qubit QFT
- A test-histogram tool for confirming the output directory is wired up before a real run
Requirements
Docker. Pull ychen94/quantum-simulator-mcp:latest and run it with a host directory mounted at /data/quantum_simulator_results plus HOST_OUTPUT_DIR pointing at that same host path — that mount is where histogram images land. No account and no key.
Setup effort
Run a container — pull the image and point your client at it
USE CASES
01
Seeing what a circuit actually produces
Submit OpenQASM 2.0 and get measurement counts back, so a hand-written circuit is checked rather than argued about.
02
Finding out how much noise your circuit tolerates
Run the same circuit clean and again under depolarizing, thermal relaxation or readout error, and compare the distributions.
03
Choosing the right output for the question
Counts for statistics, a statevector for the amplitudes, a histogram image for a slide — the available result types are listed rather than guessed.
04
Checking a circuit's cost before running it
Read depth and gate statistics first, which is the cheap way to catch a circuit that is larger than you intended.
05
Teaching from a known-good example
Start from the bundled Bell state, Grover or QFT circuits and modify them, instead of typing QASM from scratch.
06
Confirming images will actually reach your disk
Write a test histogram once to verify the mounted output directory is configured, before a long run produces files nobody can find.
5 tools
Listed in project docs. Your client may show a different list.
list_noise_modelslist_result_typesget_circuit_statscreate_test_histogramBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
docker on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Pull the image and point your client at it.
Server setup
TERMINAL
docker pull ychen94/quantum-simulator-mcp:latestAdd the mcpServers entry below to your MCP client's config — for Claude Desktop that is claude_desktop_config.json — and restart the client
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"quantum-simulator": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-v",
"/tmp:/data/quantum_simulator_results",
"-e",
"HOST_OUTPUT_DIR=/tmp",
"ychen94/quantum-simulator-mcp:latest"
]
}
}
}
