MCP server

v0.0.4

MCP scope and saved evidence

A standalone MCP client starts   plous mcp serve   as a subprocess. There is no listening port or permanent background server.

Captured access

By default, the server reads kubeconfig before every call. A change made with   kubectl config use-context   takes effect on the next call. The cluster and namespace stay fixed during that call. Use   kubernetes_context_read   to see the current target and its connection IDs. IDs from another context cannot be reused. An explicit   --context   pins the named context for the session. The standalone server follows kubeconfig independently of selection in the Plous UI.

Kubernetes, Helm, Argo CD, and Flux tools use the same cluster. Reads can use any namespace allowed by your credentials. Diagnostic operations stay in the configured default namespace.

The client manages its model, authentication, context, and spending. Plous limits individual operations but does not impose a session-wide deadline or tool-call cap.

Saved evidence

Each process saves its tool results in a separate profile under   ~/.plous/mcp/session-*  , or the supplied   --data-dir  . Its startup message on stderr shows the path.

Results survive process exit. History tools see that process’s saved evidence for the current context. Earlier standalone sessions are not imported or searched automatically.

Logs and command output may contain application secrets and can be sent to the client's model provider. Kubeconfig credentials stay with Plous. See Data and privacy.

Close or reconnect

Closing the client connection stops local work and attempts cleanup of temporary diagnostic Jobs. It cannot guarantee that an exec command stopped inside an application container.

If a command times out or its result cannot be saved, check its outcome before retrying. It may already have changed application state.

A fatal tool failure disables further calls for that process. Fix the reported problem before reconnecting. Saved evidence remains after exit.

Inside Plous, native sessions save evidence in the Plous profile. Hiding the panel leaves them running.

View source

On this page

Plous · Open source · Early development

Search Plous docs

Search the documentation.

Documentation versions