CortexCloud-mcp
Pay-per-call QUBO/Ising optimization for AI agents — estimate free, solve per run via x402 (USDC on Base).
What it can do
- Cortex Estimate Optimization: Analyze an optimization problem for free — returns a decision block: recommended mode/backend, estimated provider cost, USDC price, benchmark evidence. Always call this b
- Cortex Optimize: Solve a QUBO/Ising optimization problem (x402-paid, USDC on Base). Returns a job_id to poll with cortex_get_job. Prices per run: classical $0.05, hybrid $0.10, quantum $0.85 (charged
- Cortex Get Job: Poll an optimization job by id. Free — returns status, solution, objective, error.
What data it sees
Do you need an account
No: the server works without sign-in
Pay-per-call QUBO/Ising optimization for AI agents — estimate free, solve per run via x402 (USDC on Base). No API keys.
How to connect
How to connect CortexCloud-mcp to Claude
The server address to paste into Claude settings:
https://cortexcloud-mcp--ampwerajonathan50.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect CortexCloud-mcp to ChatGPT
The server address to paste into ChatGPT settings:
https://cortexcloud-mcp--ampwerajonathan50.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect CortexCloud-mcp to Cursor
The server address to paste into Cursor settings:
https://cortexcloud-mcp--ampwerajonathan50.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (4)
Raw names from tools/list. Only developers need these.
| cortex_estimate_optimization | Analyze an optimization problem for free — returns a decision block: recommended mode/backend, estimated provider cost, USDC price, benchmark evidence. Always call this before paying for cortex_optimize. |
| cortex_optimize | Solve a QUBO/Ising optimization problem (x402-paid, USDC on Base). Returns a job_id to poll with cortex_get_job. Prices per run: classical $0.05, hybrid $0.10, quantum $0.85 (charged = max(list, provider cost x 2.0)). Use mode=auto unless you specifically need quantum. |
| cortex_get_job | Poll an optimization job by id. Free — returns status, solution, objective, error. |
| cortex_list_backends | List solver backends (classical/hybrid/quantum) with availability, per-backend estimated provider cost, effective price, and sellable flag. Free — check this before choosing a quantum backend. |