NVIDIA / NVIDIA/cuopt

[EPIC] cuOpt MCP server

Open
#1,785 0 comments 0 reactions 1 assignee View on GitHub

@Kh4ster is already working on this.

Since Aug 25, 2026.

awaiting response epic
Dominant language
Cuda
Stars
1k
Forks
233
Avg merge
4d 4h
Merged PRs (30d)
95

Description

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 #1755).
  • Define a clean client/server interface so each can version and release independently.

Related issues

  • #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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.