This project has been archived by its maintainers, and is no longer receiving any updates.
qiskit-code-assistant-mcp-server
MCP server for Qiskit Code Assistant
Components
Tools
The server implements four tools:
accept_model_disclaimer_tool: Accept the disclaimer for a given modelget_completion_tool: Get completion for a given promptget_rag_completion_tool: Get RAG completion for answering conceptual or descriptive questions about Qiskit or Quantumaccept_completion_tool: Accept a given completion
Prerequisites
- Python 3.10 or higher
- uv package manager (recommended)
- IBM Quantum account and API token
- Access to Qiskit Code Assistant service
Installation
Install from PyPI
The easiest way to install is via pip:
pip install qiskit-code-assistant-mcp-server
Install from Source
This project uses uv for virtual environments and dependencies management. If you don't have uv installed, check out the instructions in https://docs.astral.sh/uv/getting-started/installation/
Setting up the Project with uv
-
Initialize or sync the project:
# This will create a virtual environment and install dependencies uv sync
-
Configure environment variables:
# Copy the example environment file cp .env.example .env # Edit .env and add your IBM Quantum API token # Get your token from: https://cloud.quantum.ibm.com/
Configuration
Environment Variables
The server can be configured using environment variables in your .env file:
QISKIT_IBM_TOKEN- Your IBM Quantum API token (required)QCA_TOOL_API_BASE- Qiskit Code Assistant API base URL (default:https://qiskit-code-assistant.quantum.ibm.com)QCA_TOOL_MODEL_NAME- Default model name (default:mistral-small-3.2-24b-qiskit)QCA_REQUEST_TIMEOUT- Request timeout in seconds (default:30.0)QCA_MCP_DEBUG_LEVEL- Logging level: DEBUG, INFO, WARNING, ERROR, CRITICAL (default:INFO)
Model Selection
The server includes an automatic model availability guardrail that:
- Checks available models from the Qiskit Code Assistant service at startup
- Uses the configured
QCA_TOOL_MODEL_NAMEif available - Automatically falls back to the first available model if the default is unavailable
- Logs warnings when using a fallback model
- Gracefully handles API errors by using the configured default
This ensures the server can start and function even when the default model is temporarily unavailable.
Quick Start
Running the Server
uv run qiskit-code-assistant-mcp-server
The server will start and listen for MCP connections.
Synchronous Usage
For frameworks that don't support async operations, all async functions have a .sync attribute for synchronous execution:
from qiskit_code_assistant_mcp_server.qca import (
get_completion,
get_rag_completion,
list_models
)
# Use .sync for synchronous execution
result = get_completion.sync("Write a quantum circuit for a Bell state")
print(result)
# Works in Jupyter notebooks (handles nested event loops automatically)
rag_result = get_rag_completion.sync("What is quantum entanglement?")
print(rag_result)
# List available models
models = list_models.sync()
print(models)
Available functions (all support .sync):
list_models()- List available modelsget_model(model_id)- Get model infoget_completion(prompt)- Get code completionget_rag_completion(prompt)- Get RAG-based completionaccept_completion(completion_id)- Accept a completionget_service_status()- Get service status
LangChain Integration Example:
Note: To run LangChain examples you will need to install the dependencies:
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 environment variables (QISKIT_IBM_TOKEN, OPENAI_API_KEY, etc.)
load_dotenv()
async def main():
# Configure MCP client
mcp_client = MultiServerMCPClient({
"qiskit-code-assistant": {
"transport": "stdio",
"command": "qiskit-code-assistant-mcp-server",
"args": [],
"env": {
"QISKIT_IBM_TOKEN": os.getenv("QISKIT_IBM_TOKEN", ""),
},
}
})
# Use persistent session for efficient tool calls
async with mcp_client.session("qiskit-code-assistant") as session:
tools = await load_mcp_tools(session)
# Create agent with LLM
llm = ChatOpenAI(model="gpt-5.2", temperature=0)
agent = create_agent(llm, tools)
# Run a query
response = await agent.ainvoke("Write a quantum circuit that creates a Bell state")
print(response)
asyncio.run(main())
For more LLM providers (Anthropic, Google, Ollama, Watsonx) and detailed examples including Jupyter notebooks, see the examples/ directory.
Testing and debugging the server
Note: to launch the MCP inspector you will need to have
nodeandnpm
-
From a terminal, go into the cloned repo directory
-
Switch to the virtual environment
source .venv/bin/activate
-
Run the MCP Inspector:
npx @modelcontextprotocol/inspector uv run qiskit-code-assistant-mcp-server
-
Open your browser to the URL shown in the console message e.g.,
MCP Inspector is up and running at http://localhost:5173
Testing
This project includes comprehensive unit and integration tests.
Running Tests
Quick test run:
./run_tests.sh
Manual test commands:
# Install test dependencies
uv sync --group dev --group test
# Run all tests
uv run pytest
# Run only unit tests
uv run pytest -m "not integration"
# Run only integration tests
uv run pytest -m "integration"
# Run tests with coverage
uv run pytest --cov=src --cov-report=html
# Run specific test file
uv run pytest tests/test_qca.py -v
Test Structure
tests/test_qca.py- Unit tests for QCA functionstests/test_utils.py- Unit tests for utility functionstests/test_constants.py- Unit tests for configurationtests/test_sync.py- Unit tests for synchronous executiontests/test_integration.py- Integration teststests/conftest.py- Test fixtures and configuration
Test Coverage
The test suite covers:
- ✅ All QCA API interactions
- ✅ Model selection and availability guardrail
- ✅ Error handling and validation
- ✅ HTTP client management
- ✅ Synchronous execution (
.syncmethods) - ✅ Configuration validation
- ✅ Integration scenarios
- ✅ Resource and tool handlers
Resources
Metadata
Release files for qiskit-code-assistant-mcp-server 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| qiskit_code_assistant_mcp_server-0.4.0.tar.gz | 122.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qiskit_code_assistant_mcp_server-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 143.8 kB
Release files / qiskit_code_assistant_mcp_server-0.4.0.tar.gz
| Download URL | qiskit_code_assistant_mcp_server-0.4.0.tar.gz |
|---|---|
| Size | 122.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7dbf674084c7917665c9f7d1e7e49e7deebce6470a239ea2d4b10bc53154d01
|
|
BLAKE2b-256 checksum How to use checksums |
d53fa3322e72551b116ca25f5dd20ad1df34090ec315b83d2a9c2c224dbf822d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 20, 2026.
Transparency logRelease files / qiskit_code_assistant_mcp_server-0.4.0-py3-none-any.whl
| Download URL | qiskit_code_assistant_mcp_server-0.4.0-py3-none-any.whl |
|---|---|
| Size | 21.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc635ed786e1bdd514a7c7c773cb5b9c97306983f2ee68f666f1fbcac595c11d
|
|
BLAKE2b-256 checksum How to use checksums |
51cfccd30dca7d4c7a310849b35f9f208981bc263cd991df5b4921f5a53e9cfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 20, 2026.
Transparency log