Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for Qiskit quantum computing with circuit serialization utilities
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"qiskit": {
"command": "uvx",
"args": [
"qiskit-mcp-server"
]
}
}
}Run this in your terminal
claude mcp add qiskit -- uvx qiskit-mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"qiskit": {
"command": "uvx",
"args": [
"qiskit-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"qiskit": {
"type": "stdio",
"command": "uvx",
"args": [
"qiskit-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account Qiskit, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.3.2) reached the registry 29 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Recta
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol (MCP) server that provides quantum circuit transpilation capabilities using Qiskit's pass managers. This server enables AI assistants to optimize quantum circuits for various hardware targets.
pip install qiskit-mcp-server
# Clone the repository
git clone https://github.com/Qiskit/mcp-servers.git cd mcp-servers/qiskit-mcp-server
uv sync
pip install -e .
# With uv
uv run qiskit-mcp-server
qiskit-mcp-server
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": { "qiskit": { "command": "uv", "args": [ "--directory", "/path/to/qiskit-mcp-servers/qiskit-mcp-server", "run", "qiskit-mcp-server" ] } } }
from qiskit_mcp_server.transpiler import transpile_circuit
qasm = """OPENQASM 2.0; include "qelib1.inc"; qreg q[2]; creg c[2]; h q[0]; cx q[0], q[1]; measure q -> c; """
result = await transpile_circuit(qasm)
result = await transpile_circuit( qasm, optimization_level=3, basis_gates="ibm_heron", coupling_map="linear" )
from qiskit import QuantumCircuit
from qiskit_mcp_server import dump_qpy_circuit from qiskit_mcp_server.transpiler import transpile_circuit
qc = QuantumCircuit(2, 2) qc.h(0) qc.cx(0, 1) qc.measure([0, 1], [0, 1])
qpy_circuit = dump_qpy_circuit(qc)
result = await transpile_circuit(qpy_circuit, circuit_format="qpy")
transpiled_qpy = result"transpiled_circuit"
result2 = await transpile_circuit(transpiled_qpy, circuit_format="qpy", optimization_level=3)
from qiskit_mcp_server.transpiler import transpile_circuit, analyze_circuit
result = transpile_circuit.sync(qasm, optimization_level=2)
analysis = analyze_circuit.sync(qasm) print(f"Circuit depth: {analysis'circuit_info'}") print(f"Two-qubit gates: {analysis'gate_categories'}")
from qiskit_mcp_server.transpiler import compare_optimization_levels
comparison = compare_optimization_levels.sync(qasm)
for level in range(4): result = comparison'optimization_results' print(f"Level {level}: depth={result['depth']}, size={result['size']}")
LangChain Integration Example:
Note: To run LangChain examples you will need to install the dependencies:
`bash
pip install langchain langchain-mcp-adapters langchain-openai python-dotenv
`
import asyncio
import os from langchain.agents import create_agent from langchain_mcp_adapters.client import MultiServerMCPClient from langchain_mcp_adapters.tools import load_mcp_tools from langchain_openai import ChatOpenAI from dotenv import load_dotenv
load_dotenv()
SAMPLE_BELL = """ OPENQASM 3.0; include "stdgates.inc"; qubit[2] q; h q[0]; cx q[0], q[1]; """
async def main():
mcp_client = MultiServerMCPClient({ "qiskit": { "transport": "stdio", "command": "qiskit-mcp-server", "args": [], "env": {}, } })
async with mcp_client.session("qiskit") as session: tools = await load_mcp_tools(session)
llm = ChatOpenAI(model="gpt-5.2", temperature=0) agent = create_agent(llm, tools)
response = await agent.ainvoke(f"Transpile this circuit for IBM Heron: {SAMPLE_BELL}") print(response)
asyncio.run(main())
For more LLM providers (Anthropic, Google, Ollama, Watsonx) and detailed examples including Jupyter notebooks, see the examples/ directory.
| Tool | Description |
|---|---|
transpile_circuit_tool | Transpile a circuit with configurable optimization |
analyze_circuit_tool | Analyze circuit structure without transpiling |
compare_optimization_levels_tool | Compare all optimization levels (0-3) |
load_circuit_from_qasm_tool | Load a circuit from OpenQASM 2.0 or 3.0 string, returning QPY and metadata |
export_circuit_to_qasm_tool | Export a QPY circuit to OpenQASM 2.0 or 3.0 format |
convert_qpy_to_qasm3_tool | Convert a base64-encoded QPY circuit to QASM3 |
convert_qasm3_to_qpy_tool | Convert a QASM3 (or QASM2) circuit to base64-encoded QPY |
| Resource URI | Description |
|---|---|
qiskit://transpiler/info | Transpiler capabilities and documentation |
qiskit://transpiler/basis-gates | Available basis gate presets |
qiskit://transpiler/topologies | Available coupling map topologies |
transpile_circuit(circuit, optimization_level=2, basis_gates=None, coupling_map=None, initial_layout=None, seed_transpiler=None, circuit_format="qasm3")Transpile a quantum circuit using Qiskit's preset pass managers.
Parameters:
circuit: Quantum circuit as QASM3 string, base64-encoded QPY, or QASM2 string (max 100 qubits, 10,000 gates)optimization_level: 0-3 (default: 2)basis_gates: List of gate names or preset ("ibm_default", "ibm_heron", etc.)coupling_map: List of edges or topology name ("linear", "ring", "grid", "full")initial_layout: List of physical qubit indices (length must match circuit qubits)seed_transpiler: Random seed for reproducibilitycircuit_format: Format of the input circuit ("qasm3" or "qpy"). Defaults to "qasm3". When "qasm3" is specified, QASM2 is also accepted as a fallback.Returns: Dictionary with original/transpiled circuit info and optimization metrics
Note: Level 3 optimization can be very slow for circuits with >20 qubits or >500 gates. Use level 2 for faster results with good quality.
analyze_circuit(circuit, circuit_format="qasm3")Analyze circuit structure and complexity.
Returns: Dictionary with gate counts, depth, and categorization (single/two/multi-qubit gates)
compare_optimization_levels(circuit, circuit_format="qasm3")Compare transpilation results across all optimization levels.
Returns: Dictionary comparing depth, size, and gates for levels 0-3
The server supports two circuit formats for input:
| Format | Description |
|---|---|
qasm3 | OpenQASM 3.0 string (with QASM2 fallback). Human-readable text format. |
qpy | Base64-encoded QPY binary format. Preserves exact parameters and metadata. |
QPY output: All tools return circuits in QPY format (base64-encoded) for precision when chaining tools/servers.
When to use each format:
To view a QPY circuit output in human-readable format, use the qpy_to_qasm3 utility:
from qiskit_mcp_server import qpy_to_qasm3
from qiskit_mcp_server.transpiler import transpile_circuit
result = transpile_circuit.sync(qasm_circuit, optimization_level=2) qpy_output = result"transpiled_circuit"
conversion = qpy_to_qasm3(qpy_output) if conversion["status"] == "success": print(conversion["qasm3"])
To convert a QASM circuit to QPY format (for full fidelity when chaining tools), use qasm3_to_qpy:
from qiskit_mcp_server import qasm3_to_qpy
qasm_circuit = ''' OPENQASM 3.0; include "stdgates.inc"; qubit[2] q; h q[0]; cx q[0], q[1]; '''
result = qasm3_to_qpy(qasm_circuit) if result["status"] == "success": qpy_string = result["circuit_qpy"]
| Preset | Gates | Description |
|---|---|---|
ibm_eagle | id, rz, sx, x, ecr, reset | IBM Eagle r3 (127 qubits, uses ECR) |
ibm_heron | id, rz, sx, x, cz, reset | IBM Heron (133-156 qubits, uses CZ) |
ibm_legacy | id, rz, sx, x, cx, reset | Older IBM systems (uses CX) |
You can also provide a custom list of gate names for other hardware targets.
| Topology | Description |
|---|---|
linear | Chain connectivity (qubit i ↔ i+1) |
ring | Linear with wraparound |
grid | 2D grid connectivity |
heavy_hex | IBM heavy-hex topology (Eagle/Heron architecture) |
full | All-to-all connectivity |
To ensure reliable performance, the server enforces the following limits:
| Limit | Default | Environment Variable |
|---|---|---|
| Maximum qubits | 100 | QISKIT_MCP_MAX_QUBITS |
| Maximum gates | 10,000 | QISKIT_MCP_MAX_GATES |
Circuits exceeding these limits will return an error with a descriptive message.
You can override these limits via environment variables:
# Allow up to 200 qubits and 50,000 gates
export QISKIT_MCP_MAX_QUBITS=200 export QISKIT_MCP_MAX_GATES=50000
| Optimization Level | Use Case | Performance |
|---|---|---|
| 0 | Quick iterations, debugging | Fastest |
| 1 | Development, prototyping | Fast |
| 2 | Production use (recommended) | Balanced |
| 3 | Critical applications, small circuits | Slowest |
Tips:
Only the beginning is shown; read the rest in the repo