[EPIC] cuOpt MCP server

[ramakrishnap-nv]

Summary

Tracking epic for cuOpt's MCP (Model Context Protocol) server work.

Goals

• Separate the MCP client and MCP server into independent, decoupled components instead of a single bundled cuopt_mcp package.
• Ship the MCP server as its own pure-Python wheel, not entangled with the main cuopt package's build/deps (see [FEA] Decouple cuopt_mcp from the cuopt package so it ships as a pure-Python wheel #1755).
• Define a clean client/server interface so each can version and release independently.

Related issues

• [FEA] Decouple cuopt_mcp from the cuopt package so it ships as a pure-Python wheel #1755 — Decouple cuopt_mcp from the cuopt package so it ships as a pure-Python wheel

Open questions

• Transport/protocol boundary between client and server
• Versioning/release cadence for the split packages