Quantum Simulator

Created By
YuChenSSRa year ago
Overview

What is Quantum Simulator?

Quantum Simulator is a Docker-based quantum circuit simulator that implements the Model Context Protocol (MCP), allowing integration with MCP clients like Claude for Desktop.

How to use Quantum Simulator?

To use Quantum Simulator, pull the Docker image and run the container with the specified command. You can also integrate it with Claude for Desktop by configuring the MCP settings.

Key features of Quantum Simulator?

  • Supports OpenQASM 2.0 quantum circuits
  • Simulates quantum circuits using Qiskit
  • Offers various noise models (depolarizing, thermal relaxation, readout error)
  • Provides multiple result types including counts, statevector, and visualized histograms
  • Includes pre-configured example circuits
  • Seamless integration with MCP clients

Use cases of Quantum Simulator?

  1. Running quantum circuits with specified noise models
  2. Analyzing quantum circuits and retrieving statistics
  3. Generating test histograms for verification

FAQ from Quantum Simulator?

  • Can Quantum Simulator run on Windows?

The image has not been tested on Windows systems yet, but it should work with proper Docker Desktop configuration.

  • How do I troubleshoot if the container exits immediately?

Ensure to use the -i flag to keep stdin open, which is required for the MCP STDIO transport.

  • What should I do if Claude cannot access the histogram files?

Check the volume mapping and ensure the HOST_OUTPUT_DIR environment variable matches the host path.

Server Config

{
  "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"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
YuChenSSR
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago