Problem: no example exists showing flux-rest-server used as the
foundation for an MCP server -- something an agent (LLM-based
tools, automation) could use directly to submit and manage jobs.
Existing Flux MCP servers require the real flux Python module
installed locally and direct access to a broker:
Both mean the MCP server has to run co-located with (or with direct
binding/socket access to) a Flux install. flux-rest-server is
designed specifically to avoid this: an MCP server built on it only
needs network access to an HTTP endpoint, so it can run anywhere --
a laptop, a different network entirely -- without Flux's own
bindings installed at all.
Proposal: use flux-rest-server as the foundation for a small example
MCP server, exposing submit/state/cancel as tools purely over HTTP.
See #12 (draft) for an initial WIP implementation.
Problem: no example exists showing
flux-rest-serverused as thefoundation for an MCP server -- something an agent (LLM-based
tools, automation) could use directly to submit and manage jobs.
Existing Flux MCP servers require the real flux Python module
installed locally and direct access to a broker:
converged-computing/flux-mcp(https://github.com/converged-computing/flux-mcp)mada-mcp-flux, part ofllnl/mada-tools(https://github.com/llnl/mada-tools, see src/mada_tools/scheduler/flux/)
Both mean the MCP server has to run co-located with (or with direct
binding/socket access to) a Flux install.
flux-rest-serverisdesigned specifically to avoid this: an MCP server built on it only
needs network access to an HTTP endpoint, so it can run anywhere --
a laptop, a different network entirely -- without Flux's own
bindings installed at all.
Proposal: use
flux-rest-serveras the foundation for a small exampleMCP server, exposing submit/state/cancel as tools purely over HTTP.
See #12 (draft) for an initial WIP implementation.