Inspect
Give the agent context.
Read applications, services, runtime state and recent logs from your installation. Keep the diagnosis tied to the workload you selected.
AGENT CONTROL / SELF-HOSTED ALPHA
Your cloud,
managed by your agents.
Connect an MCP client to your self-hosted Hakopod installation. Inspect services, read recent logs, and deploy a reviewed plan with the access you grant.
Available in the self-hosted development release. Hakopod Cloud remains in development.
From a question to a checked result.
Review
See the change first.
Prepare a canonical application plan. Review its target, configuration and resolved images before authorizing deployment.
Deploy
Follow the result.
Enable deployment access when the job needs it. Follow the operation and inspect the service state after it finishes.
YOU CHOOSE THE ACCESS
Start with observation.
Allow changes when needed.
A connection selects one project and environment. Deployment needs both a write permission and an explicit option in the MCP server. Hakopod checks the request through the same Go API that serves its other interfaces.
Your agent receives application context. It does not receive Kubernetes credentials.
One useful first task.
Example request
Inspect my development API. Show its current state and recent errors before proposing changes.
Then review the proposed plan, authorize a deployment if appropriate, and check the final result. An accepted request alone does not prove the application is healthy.
Follow the workflowWhat you can use today.
Released self-hosted MCP
Application and service inspection, runtime state, domains, deployment status, recent logs, framework detection, and reviewed deployment plans. Deployment can be enabled for authorized credentials.
Read the releasesIn development
Broader API coverage, pod commands, managed SQL queries and installation administration. These additions are being tested before release.
Follow agent-control development