MCP server for the Marqov quantum orchestration platform
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"marqov-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# marqov-mcp An MCP server for the [Marqov](https://app.marqov.ai) quantum orchestration platform, so Claude Code — or any MCP client, or your own agent — can discover backends, price runs, execute on a free simulator, and inspect jobs directly. > **Preview.** Tool contract version `1`. The tools are stable enough to build > against. Browser authorization and stored credentials are supported (see *Authentication*). > > **You need a Marqov account.** The platform is in an invite-only beta. Without an > account, `list_backends` and `check_backend_availability` still work; every other > tool needs a key from a Marqov team. Full guide: > [AI Assistants (MCP Server)](https://docs.marqov.ai/docs/platform-guide/mcp-server). ## What it is, and what it is not This wraps the Marqov **control plane**: backends, cost estimates, jobs, traces, budget, playground. It is **not** a Qiskit MCP. A model writes Qiskit competently from its own weights, and wrapping circuit construction in a tool call spends context to buy nothing. What a model *cannot* know from its weights is your live fleet, your prices, your job IDs and your team's budget — which is exactly where tools earn their place. ## Authentication You supply your own Marqov API key. The server holds no user model, no session store and no state; it forwards your key and the platform decides, per request. Authorise this machine in a browser: ```bash marqov-mcp login # shows a code, opens the consent page, stores the key it is granted marqov-mcp status --check # confirms the platform accepts it ``` You get a short code, a team owner or admin approves it on the Marqov site, and the key is issued to this machine — scoped, capped and revocable. The approver can grant *less* than was asked for, so check what `login` reports at the end. `--level` asks for a permission level (default `simulate`, the lowest that can run simulations), `--spend-limit` asks for a daily cap in USD, and `--client-name` sets the name show…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.