
Qiskit Code Assistant MCP Server
io.github.QiskitPublished by GitHub account Qiskitv0.4.0Updated Oct 24, 2026
MCP server for the Qiskit Code Assistant intelligent code completion
Overview
Local MCP server that connects an assistant to the Qiskit Code Assistant for intelligent code completion, authenticated with an IBM Quantum API token.
- What you can do
- Provides intelligent code completion through the Qiskit Code Assistant, letting the assistant request completions for code it is working on. The API base URL and default completion model can be configured through environment variables. Authentication is handled with an IBM Quantum API token. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Useful when working on Qiskit or quantum code and you want the assistant to draw on the Qiskit Code Assistant's completion service rather than a general model. Best suited to desktop setups where a local stdio process can be launched.
- Requirements
- Runs locally as a stdio process, launched with uvx from the qiskit-code-assistant-mcp-server PyPI package, so a Python/uv runtime is needed. Requires an IBM Quantum API token supplied in the QISKIT_IBM_TOKEN environment variable. Optional settings are QCA_TOOL_API_BASE for the API base URL and QCA_TOOL_MODEL_NAME for the default completion model. Network access to the Qiskit Code Assistant API is required.
Installation
In SourceWeft
- Open Qiskit Code Assistant MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.4.0LatestSep 16, 2026
Score
35% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts