Quantum MCP Server

What the code does

We read the source, 22 h ago · rules 3dff92dd89df

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

            arr = ensure_array(eval(func_str, namespace).astype(dtype), use_gpu=use_gpu)  # noqa: PGH001

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

этот файл ставится пользователю, но в репозитории его нет

            arr = ensure_array(eval(func_str, namespace).astype(dtype), use_gpu=use_gpu)  # noqa: PGH001

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      - name: Update version in pyproject.toml
        run: |
          cd ${{ matrix.package }}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add quantum-mcp -- uvx scicomp-quantum-mcp

{
  "mcpServers": {
    "quantum-mcp": {
      "args": [
        "scicomp-quantum-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.quantum-mcp]
command = "uvx"
args = ["scicomp-quantum-mcp"]

{
  "mcpServers": {
    "quantum-mcp": {
      "args": [
        "scicomp-quantum-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "quantum-mcp": {
      "args": [
        "scicomp-quantum-mcp"
      ],
      "command": "uvx"
    }
  }
}