mcp

Run a Model Context Protocol (MCP) server over stdio.

entire mcp

entire mcp is hidden from entire --help, but it is a normal command and runs wherever the CLI is installed. Configure an MCP host to launch entire mcp as a stdio server. It exposes Entire’s agent_help and entire_status as MCP tools, so an agent without a hook or context-injection channel can still discover and use Entire. The server is read-only and speaks newline-delimited JSON-RPC 2.0.

This does not replace lifecycle hooks. An MCP host learns what Entire can do and what the repository’s state is, but session capture still comes from the hooks that entire enable installs. See Agents for the integration paths.

Tools

Tool	Description
`agent_help`	The command map for the installed CLI, the same content as `entire agent-help --json`. Takes an optional `command` argument naming a subcommand path, space-separated, such as `checkpoint` or `repo mirror add`, to drill into one command.
`entire_status`	The current repository’s Entire status, byte-identical to `entire status --json`. It returns JSON, not the human-readable table.

Configure a Host

Most hosts take a command and arguments. Point yours at the entire binary with the mcp subcommand:

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

The exact file and schema depend on the host. Use an absolute path to entire if the host does not inherit your shell’s PATH.

Commands

Tools

Configure a Host

Continue With

Agents

agent-help

​Tools

​Configure a Host

​Continue With

Agents

agent-help

Tools

Configure a Host

Continue With