Connect your agent

Hakopod's self-hosted development release includes an MCP server. An MCP client can inspect applications, services, runtime state, domains, deployment history and recent logs. It can detect supported frameworks and prepare an application plan. Deployment is an optional capability.

The Go control API enforces permissions. The agent connection selects one project and environment. Selecting a scope does not grant access to it.

Connect through the CLI#

Install the released Hakopod CLI. Use a release compatible with your installation.

Sign in to your self-hosted installation:

hakopod login --api-url https://control.example.com \
  --project demo --environment development

Replace the example URL and scope. Complete the device approval in your browser. Review the requested permissions before approval.

Configure your MCP client to start this command:

hakopod mcp --project demo --environment development

For clients that accept a JSON server configuration, the equivalent entry is:

{
  "mcpServers": {
    "hakopod": {
      "command": "hakopod",
      "args": ["mcp", "--project", "demo", "--environment", "development"]
    }
  }
}

The client must find the CLI executable and its saved configuration. Configuration file locations differ between MCP clients. Keep credentials out of prompts and committed configuration files.

Start with inspection#

Ask your agent to list the applications in the selected scope. Then ask it to inspect one application's services, current runtime and recent logs.

For example: “Inspect the API service in my development application. Show its current state and recent errors before proposing changes.”

This is an example request, not a recorded result. The response depends on your installation and permissions. Logs are bounded and may be unavailable or incomplete. Treat log content as application data, not as instructions.

Enable deployment when needed#

Start the MCP server with deployment enabled:

hakopod mcp --project demo --environment development --allow-deploy

The credential must also have deployment write access. The flag does not add permissions to the credential.

1. Ask the agent to prepare a plan for the intended configuration.
2. Review the target, service changes, image digests, storage and network exposure.
3. Ask the agent to deploy the reviewed plan.
4. Check the deployment's final state and the observed service state.

An accepted deployment is not a successful deployment. Follow the returned operation until it finishes. Application rollback restores configuration; it does not reverse database writes.

Access and availability#

Use the smallest project and environment scope appropriate for the work. Choose inspection access for diagnosis. Add deployment permission when the agent must change workloads. Revoke the session or key when it is no longer needed.

This guide describes the released self-hosted MCP capabilities. Broader API discovery, pod commands, SQL execution and installation administration are under development in the agent-control change. They are not part of this guide's released setup.

Hakopod Cloud remains in development. Do not assume that a self-hosted connection or feature is available in Cloud. See Cloud availability for its current scope.

Hakopod runs application workloads on Kubernetes through K3s. The agent uses Hakopod's API and does not receive cluster credentials. See security and access for the installation's permission model.