isingq-mcp
OfficialRelated Servers
Alternatives to isingq-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables AI assistants to interact with the CETC-ICQ quantum cloud platform via the gjq-client Qiskit 2.0 SDK, supporting account management, device listing, circuit submission, and task management.13Apache 2.0
- AlicenseBqualityCmaintenanceMathematical Optimization MCP Server with PuLP and OR-Tools support135MIT
- AlicenseAqualityAmaintenanceEnables AI agents to describe combinatorial optimization problems as JSON and obtain validated, ranked, re-verified solutions through MCP tools.485 PyPIMIT

SpinQit MCP Toolsofficial
FlicenseNot gradedqualityDmaintenanceSpinQit MCP Tools is a Python MCP server that connects AI assistants to SpinQ Cloud, enabling QASM circuit submission, platform discovery, and quantum task result retrieval through the Model Context Protocol.2-- FlicenseAqualityFmaintenanceUnofficial Model Context Protocol (MCP) server that enables LLMs to build and execute quantum circuits using Qiskit.137-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides static validation and documentation lookup for quantum computing libraries, currently supporting PennyLane. It allows users to verify quantum code syntax and method usage against official library documentation to ensure correct implementation.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct stage of the QUBO workflow (setup, knowledge, guide, validate, start, poll, result). The boundary between isingq_solve_poll (queries remote and updates local record) and isingq_solve_result_get (reads local saved results) is somewhat subtle but the descriptions clarify it.
All names share the isingq_ prefix and use consistent snake_case, but verb placement varies: some are noun_verb (knowledge_get, qubo_validate) while others are verb_noun/verb_verb (solve_start, solve_poll, solve_result_get). The pattern is still predictable and readable.
Seven tools is well-scoped for a QUBO-solving service, with each tool earning its place across setup, knowledge, modeling, validation, and solve lifecycle.
The surface covers the full workflow from API key setup through modeling, validation, remote solve start, polling, and result retrieval. Minor gaps exist, such as no task cancellation, list, or batch operations, but core workflows are complete.