MCP server
MCP server
Give Codex or Claude Code access to Plous's cluster tools through Model Context Protocol (MCP). Agents can read Kubernetes, Helm, Argo CD, and Flux data and revisit saved tool results.
Reads work by default. Container commands and temporary tests require explicit setup.
Connect your client
Setup: connect an MCP client.
Tools and permissions: tool names and supported operations.
Active diagnostics: enable commands and temporary tests.
Scope and saved evidence: cluster access, storage, and reconnection.
Troubleshooting: fix connection and tool errors.
Choose the connection mode
Mode
Connection
Tools
Standalone
Your client starts plous mcp serve over stdin/stdout
Cluster reads, saved evidence, and enabled diagnostics
Inside Plous
Plous configures a private connection for its assistant panel
The same tools, plus actions that open Plous views
The built-in Plous agent uses these tools directly and needs no MCP setup.
For debugging instructions as well as tools, install plous-debug. Other MCP clients must support the implemented protocol and need separate compatibility checks.