quantum-resource-estimator
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@quantum-resource-estimatorEstimate physical qubits for Shor's algorithm on RSA-2048"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Quantum Resource Estimator MCP Server
An MCP (Model Context Protocol) server that makes quantum resource estimation accessible through natural language. Built on Microsoft's QDK resource estimator.
What It Does
Estimates physical quantum resources (qubit count, runtime) needed to run quantum algorithms on fault-tolerant hardware. Helps researchers answer questions like:
"How many qubits does it take to break RSA-2048 with Shor's algorithm?"
"How does a superconducting qubit hardware compare to trapped-ion for this chemistry simulation?"
"What's the tradeoff between qubit count and runtime for my algorithm?"
Tools
Tool | Description |
| Run a single resource estimation with defaults or custom params |
| Side-by-side comparison across hardware architectures |
| Pareto frontier: qubit-count vs. runtime tradeoff |
| Reference data for all 6 predefined qubit models |
| Reference data for QEC schemes (surface_code, floquet_code) |
| Predefined algorithms with logical resource counts |
| Domain-specific guidance (cryptography, chemistry, optimization) |
| Estimation with fully custom qubit parameters |
Installation
Requires uv. The qsharp package bundles its own native runtime — no .NET SDK install needed.
Via PyPI (recommended)
No cloning needed. Configure your MCP client directly (see below) — uvx handles installation automatically on first run.
From source
git clone https://github.com/DeDuckProject/quantum-resource-estimator-mcp
cd quantum-resource-estimator-mcp
uv syncUsage
Configure in Claude Desktop
macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
Windows — %APPDATA%\Claude\claude_desktop_config.json
Linux — ~/.config/Claude/claude_desktop_config.json
{
"mcpServers": {
"quantum-resource-estimator": {
"command": "/path/to/uvx",
"args": [
"--from",
"quantum-resource-estimator-mcp",
"qre-mcp"
]
}
}
}Replace /path/to/uvx with the output of which uvx.
Configure in Claude Code
claude mcp add quantum-resource-estimator -- /path/to/uvx --from quantum-resource-estimator-mcp qre-mcpReplace /path/to/uvx with the output of which uvx.
From source (development)
claude mcp add quantum-resource-estimator -- /path/to/uv run --directory /path/to/quantum-resource-estimator-mcp qre-mcpInspect with MCP dev tools
uv run mcp dev src/qre_mcp/server.pyAlgorithm Input Methods
Template (easiest):
algorithm_template="shor_2048"— uses predefined logical counts from published researchLogical counts:
logical_counts='{"numQubits": 100, "tCount": 200}'— provide your own circuit countsQ# code:
qsharp_code="..."— provide Q# source with a parameterless entry point
Example Queries
Via an LLM with this MCP server connected:
"Estimate the resources to break RSA-2048 on superconducting hardware"
"Compare all qubit technologies for the FeMo-cofactor chemistry simulation"
"Show me the qubit vs runtime tradeoff for Shor's algorithm on trapped-ion hardware"
"I have a circuit with 500 logical qubits and 10 million T gates — how many physical qubits do I need?"
Example Output

Predefined Algorithm Templates
ID | Algorithm | Category |
| Shor's factoring (RSA-2048) | Cryptography |
| Grover search (AES-128) | Cryptography |
| FeMo-cofactor simulation | Chemistry |
| Quantum phase estimation | General |
Note: Templates are provided for demonstration and system exploration only. Logical counts are sourced from published research but may not capture significant details. For research-grade estimates, provide your own
logical_countssourced directly from primary publications. When using a template,estimate_resources()will include atemplate_infofield in the response with the source citation and relevant caveats.
Logs
The server runs over stdio (MCP protocol), so stdout/stderr are not available for human-readable output. Logs are written to a file you can follow in a separate terminal:
tail -F ~/.local/share/qre-mcp/qre-mcp.log-F (capital F) handles log rotation — the file is capped at 5 MB with up to 3 backups.
To use a custom log path, set the QRE_MCP_LOG environment variable before starting the server.
Running Tests
uv run pytestTests cover validators, result formatting, reference data, and parameter building. Integration tests (requiring qsharp) are skipped if the package is not available.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DeDuckProject/quantum-resource-estimator-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server