Connect your AI agent to quantum hardware
The MCP server links Claude, Cursor or assistants to Kipu's Quantum Hub. Describe the problem in plain language; get an answer, not a circuit.
Claude Code. Connects over OAuth, no tokens in config. Other clients
Connecting another client?
Point any MCP client at https://api.hub.kipu-quantum.com/mcp.
{
"mcpServers": {
"qhub-mcp": { "url": "https://api.hub.kipu-quantum.com/mcp" }
}
}MCP server connection settings
Hosted at https://api.hub.kipu-quantum.com/mcp. Authentication is over OAuth in the browser on first connect; no credentials are stored in configuration files. Claude Code: run claude mcp add --transport http qhub-mcp https://api.hub.kipu-quantum.com/mcp.
Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"qhub-mcp": { "url": "https://api.hub.kipu-quantum.com/mcp" }
}
}VS Code (settings.json)
{
"mcp": {
"servers": {
"qhub-mcp": { "type": "http", "url": "https://api.hub.kipu-quantum.com/mcp" }
}
}
}Claude Desktop (Settings → Connectors)
Add custom connector URL: https://api.hub.kipu-quantum.com/mcp
Organisation authentication for teams
On a commercial Plus plan, your agent authenticates into your organisation’s context. The whole team runs on shared backend credentials, with role-based access.
Organisation access on the commercial Plus plan and up. How it works
Shared credentials
An owner sets provider tokens once. Every member's agent runs on those backends.
Role-based access
Viewer, Maintainer and Owner roles bound what each agent can see or change.
Clean context
The account-context selector keeps personal and organisation work separate.
Shared billing
Usage rolls up to one organisation balance, with per-member budgets.
From a sentence to a solution
You describe it
plain language
MCP routes it
api.hub.kipu-quantum.com/mcp
Runs on hardware
IBM · IonQ · Rigetti
Answer, not a circuit
results + cost
hub_*
services, data pools, organisations, billing
quantum_*
jobs, sessions, backends
You don't pick from 200+ tools by hand. A recipe like the new-notebook skill expands one goal into the right sequence of tool calls. This and more skills are available from the qhub-agent-toolkit.
Questions, answered
What is the Kipu Quantum Hub MCP server?
It is a Model Context Protocol server that connects your AI assistant to the Kipu Quantum Hub. Once added, your agent can list quantum backends, run production-grade solvers on real hardware, store inputs and results in data pools, and deploy a solver as a live REST API, all from plain-language instructions.
Which AI assistants can connect?
Any MCP-capable client. Setup is documented for Claude Code, Claude Desktop, Cursor and VS Code, and the same hosted endpoint works with any assistant that speaks the Model Context Protocol.
How does authentication work?
Over OAuth, with no credentials stored in configuration files. The first time your client connects, it opens a browser window where you sign in to the Kipu Quantum Hub and authorize access. The endpoint is https://api.hub.kipu-quantum.com/mcp.
What does organisation authentication add on the Plus plan?
On a commercial Plus plan your agent operates inside your organisation's context rather than a personal account. An organisation owner or maintainer configures provider access tokens once, and every member's agent runs jobs on those shared backend credentials. Role-based access (Viewer, Maintainer, Owner) governs what each member can create, edit or delete, and the account-context selector keeps personal and organisation work separate.
What can my agent actually run?
Kipu Quantum's production solvers across all major backends, including IBM, IonQ, Rigetti and IQM, plus simulators. Typical tasks are combinatorial optimization, quantum feature extraction for machine learning, and sampling. The agent matches your problem to a service, executes it on hardware, and returns an answer rather than a circuit.
Do I need to know quantum computing?
No. You describe the problem in plain language and the agent handles service matching, encoding, hardware selection and post-processing. Pre- and post-processing are managed by the Hub, so you provide the problem and read the result.