AI agents (MCP) | homeport

Serve homeport's commands as Model Context Protocol tools so an AI agent can deploy, roll back, read logs, and manage secrets.

homeport mcp runs homeport as an MCP server over stdio, exposing its everyday commands as tools an AI agent can call — so an assistant can deploy, roll back, read logs, and manage secrets for you.

homeport mcp

It’s project-scoped: every tool operates on the app defined by the homeport.yaml in the working directory the server is started from — the same model as the CLI. Deploys build locally and ship over your SSH access, exactly as if you ran the command yourself.

Tools

Tool	What it does
`status`	app state (systemd), domain/path, port, live + available releases
`apps`	fleet view — every app on this project’s server, with state and exposure
`deploy`	build → upload → health-checked activate (auto-reverts on failure)
`rollback`	instantly activate the previous release (or a specific one)
`logs`	recent app logs from journald
`stats`	live resource usage — app memory/cpu/tasks, releases disk, host headroom
`secrets_list`	list env keys + value lengths (values never leave the server)
`secrets_set`	set/update env values (merges; restarts a running app)
`secrets_rm`	remove env keys (restarts a running app)

Wiring it into a client

Start the server from your project directory so it picks up the right homeport.yaml.

Claude Code:

claude mcp add homeport -- homeport mcp

Generic MCP client (config JSON):

{
  "mcpServers": {
    "homeport": {
      "command": "homeport",
      "args": ["mcp"]
    }
  }
}