# MCP Client Config Example

`pyro-mcp` is intended to be exposed to LLM clients through the public `pyro` CLI.

Generic stdio MCP configuration using `uvx`:

```json
{
  "mcpServers": {
    "pyro": {
      "command": "uvx",
      "args": ["--from", "pyro-mcp", "pyro", "mcp", "serve", "--profile", "workspace-core"]
    }
  }
}
```

If `pyro-mcp` is already installed locally, the same server can be configured with:

```json
{
  "mcpServers": {
    "pyro": {
      "command": "pyro",
      "args": ["mcp", "serve", "--profile", "workspace-core"]
    }
  }
}
```

Profile progression:

- `vm-run`: expose only `vm_run`
- `workspace-core`: the default persistent chat profile
- `workspace-full`: shells, services, snapshots, secrets, network policy, and disk tools

Primary profile for most agents:

- `workspace-core`

Use lifecycle tools only when the agent needs persistent VM state across multiple tool calls.

Concrete client-specific examples:

- Claude Desktop: [examples/claude_desktop_mcp_config.json](claude_desktop_mcp_config.json)
- Cursor: [examples/cursor_mcp_config.json](cursor_mcp_config.json)