Qiskit MCP Servers: quantum circuits and IBM Quantum
Qiskit MCP Servers
A set of Qiskit MCP servers: an agent builds quantum circuits, optimizes them, searches the docs and runs jobs on IBM Quantum
- 46 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The Runtime server submits jobs to real quantum hardware under your IBM Quantum token
- The token sits in the client's environment variable
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/qiskit-mcp-serversDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The Runtime server submits jobs to real quantum hardware under your IBM Quantum token
- The token sits in the client's environment variable
This is third-party code. Review the repository files before installing.
What it does
The repository brings together several FastMCP servers that open the Qiskit library and IBM Quantum services to an agent. There are four main servers. Qiskit MCP Server creates and transpiles circuits and serializes them to QASM3 and QPY. Qiskit IBM Runtime gives full access to IBM quantum hardware. Qiskit IBM Transpiler optimizes and routes circuits with AI. Qiskit Docs searches and returns documentation, guides and API references with no authorization. A community server sits apart: Qiskit Gym synthesizes circuits by reinforcement learning for permutations, linear functions and Clifford circuits. There was also a Qiskit Code Assistant MCP Server, removed because IBM Quantum discontinued the service itself. Each server installs from PyPI as a separate package or through the qiskit-mcp-servers meta-package with the extras you need. Examples show a LangChain agent and a multi-agent search for the highest Quantum Volume on IBM Quantum hardware.
Who it is for. Researchers and developers of quantum algorithms who write circuits in Qiskit and want an agent to handle building, transpiling and running on IBM hardware.
Good fit when
- An agent must build a quantum circuit from a description and save it as QASM3
- A circuit needs retranspiling for a specific IBM Quantum backend and a depth comparison
- You want a fast answer about the Qiskit API from the docs right in the agent chat
- A job goes to real hardware through Qiskit IBM Runtime and is tracked
- You need circuit synthesis for permutations or Clifford circuits by reinforcement learning
Not a fit when
- You need quantum computing on another vendor's platform: the servers work only with Qiskit and IBM Quantum
- You have no IBM Quantum account: the Runtime and Transpiler servers will not work without a token
- You want an assistant for writing Qiskit code: Code Assistant was closed together with the service
- You need hardware with no queue: jobs on real devices wait their turn at IBM
Example request
Build a circuit that creates a Bell entangled state, optimize it for an IBM backend and show the gate count before and after.MCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
QISKIT_IBM_TOKENsecret- IBM Quantum token for the Runtime and Transpiler servers
Limitations
You need Python 3.10 or newer, 3.11 is recommended. The Runtime and Transpiler servers need an IBM Quantum token in QISKIT_IBM_TOKEN, while the Qiskit, Docs and Gym servers need none. Runs on hardware consume your IBM Quantum access.
Qiskit Gym is marked as a community server. The Qiskit Code Assistant MCP Server was removed after the service itself was closed. Each server is versioned as a separate package, so check commands against the README of the server you need; the root one may lag.
How to disable. Remove a server with claude mcp remove, for example claude mcp remove qiskit-ibm-runtime. Revoke the IBM Quantum token on quantum.ibm.com if needed.
FAQ
Which servers are in the repository?
Four main ones: Qiskit MCP Server, Qiskit IBM Runtime, Qiskit IBM Transpiler and Qiskit Docs, plus the community Qiskit Gym. Qiskit Code Assistant was removed because IBM Quantum closed the service.
How do I connect the docs server?
With claude mcp add qiskit-docs -- uvx qiskit-docs-mcp-server. No token is needed, and the server searches and returns Qiskit documentation, guides and API references. For other clients put the same uvx call into the MCP config.
Do I need an IBM Quantum account?
For the Runtime and Transpiler servers yes: a token in QISKIT_IBM_TOKEN, obtained at quantum.ibm.com. The Qiskit, Docs and Gym servers work without a token.
How do I install all the servers at once?
With pip install "qiskit-mcp-servers[all]" including the community servers or pip install qiskit-mcp-servers with the core ones only. Individual servers take extras such as [runtime], [transpiler], [docs] and [gym].
Are there usage examples?
Yes. Each server folder has a Jupyter notebook and a LangChain script, and the root has a multi-agent example that searches for the highest Quantum Volume on IBM Quantum hardware.
Discussion
No questions or reviews yet.
Related
MCP serversIBM MCP
ibm-mcp
An IBM catalog of links to MCP servers for IBM and partner products: IBM MQ, App Connect, Decision Intelligence, Process Mining, DataStax Astra DB and more
Firmware references for an agent: registers, Modbus and SCPI with a quote and page number, and a refusal instead of a guess when data is missing
A Rust MCP server: a repository knowledge graph, 43 tools, edit impact analysis and a guard against dangerous changes
Ref's MCP server: documentation search for APIs and libraries that hands the agent only the relevant parts of pages
An MCP server that indexes code with tree-sitter and returns individual functions and classes to the agent instead of whole files
MCP DevTools replaces a dozen MCP servers with one Go binary: search, page fetch, package documentation and GitHub.
README in short
The README lists requirements, installation from PyPI and from source, token setup and connection for Claude Code, IBM Bob and other clients. Then tables of core and community servers, a list of removed ones, LangChain examples, a FastMCP architecture with a server.json manifest for the registry, and development notes.