Mcp Qiskit
Orchestrate Qiskit 2.3.1 circuits, transpilation, and simulation steps from your agent while learning or prototyping quantum workflows in Python.
Overview
mcp-qiskit is a MCP server for the Build phase that exposes Qiskit 2.3.1 quantum computing APIs to AI agents via stdio.
What is this MCP server?
- MCP server targeting Qiskit 2.3.1 quantum computing APIs
- PyPI package mcp-qiskit version 0.1.1 with stdio transport
- Repository: github.com/daedalus/mcp-qiskit
- Helps agents assemble circuits, backends, and simulation calls without guessing Qiskit 2.x APIs
- Niche advanced tooling for research-style automation pipelines
- Targets Qiskit 2.3.1
- Server package version 0.1.1
- PyPI identifier mcp-qiskit
What problem does it solve?
Agents routinely suggest wrong or deprecated Qiskit patterns, wasting time when you are prototyping circuits and simulations.
Who is it for?
Indie researchers or developers automating Qiskit 2.x experiments with Claude Code or Cursor.
Skip if: Builders with no quantum background who need a no-code quantum SaaS or guaranteed hardware access out of the box.
What do I get? / Deliverables
Tool calls route through Qiskit 2.3.1 so generated workflows match the library version you actually run locally.
- MCP-registered access to Qiskit-oriented tool operations
- Agent-assisted circuit and simulation code aligned to Qiskit 2.3.1
- Repeatable quantum prototyping scripts with fewer API mismatches
Recommended MCP Servers
Journey fit
Quantum prototyping is implementation work in Build—even when research-flavored—because the MCP server executes library-backed integration tasks in code. integrations reflects exposing Qiskit’s programmatic API to agents rather than publishing a end-user SaaS quantum product by itself.
How it compares
MCP wrapper for Qiskit libraries, not a quantum cloud console skill or a general linear-algebra tutor.
Common Questions / FAQ
Who is mcp-qiskit for?
Python developers and researchers already using Qiskit who want agent-assisted circuit and simulation coding through MCP.
When should I use mcp-qiskit?
Use it during Build when iterating on Qiskit 2.3.1 scripts, notebooks, or automation—after you know which backend or simulator you target.
How do I add mcp-qiskit to my agent?
Install mcp-qiskit from PyPI into a Qiskit-compatible Python env, add the stdio MCP entry in your client, and keep Qiskit 2.3.1 aligned with the server description.