mcpField
C
cuopt-server-common

cuopt-server-common

github.com/promptingcompanyDevelopment039 installsUpdated 17w ago
Repository

About cuopt-server-common

A domain reference skill for cuOpt Server's REST API. It explains supported optimization problem types, the request-and-poll workflow, and the key questions to clarify for deployment and use.

Key features

  1. 01Routing, LP, and MILP support overview
  2. 02QP REST limitation
  3. 03Request ID and polling flow
  4. 04Conceptual endpoint reference
  5. 05Deployment and usage scoping questions

Use cases

  1. 01Checking whether an optimization type is supported
  2. 02Understanding request submission and solution polling
  3. 03Clarifying deployment and client requirements

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/promptingcompany/nv-skills --skill cuopt-server-common

After installing, type/cuopt-server-commonin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

BENCHMARK.md
skill-card.md
skill.oms.sig
evals/
evals.json

Details

From the project README

cuOpt Server (common)

Domain concepts for the cuOpt REST server. No deploy commands or client code here.

What the server does

  • Accepts optimization requests (routing, LP, MILP) over HTTP.
  • Returns a request ID; solution is obtained by polling with that ID.
  • Does not support QP via REST.

Problem types supported

Problem typeSupported
Routing✓
LP✓
MILP✓
QP✗

Request flow (conceptual)

  1. Client sends problem data in the required schema (matrices, tasks, fleet, solver config).
  2. Server returns a reqId.
  3. Client polls the solution endpoint with reqId until the job completes.
  4. Response contains status and, on success, solution (routes, objective, primal values, etc.).

Required questions (deployment and usage)

Ask these if not already clear:

  1. Problem type — Routing or LP/MILP? (QP not available.)
  2. Deployment — Local, Docker, Kubernetes, or cloud?
  3. Client — Which language or tool will call the API (e.g. Python, curl, another service)?

Key endpoints (conceptual)

  • Health check.
  • Submit request (POST).
  • Get solution by request ID (GET).
  • OpenAPI spec (e.g. for payload format).

Comments

Markdown supported