thaloco/pyro-mcp
1
Fork 0
Code Pull requests Releases Packages Activity Actions
pyro-mcp/examples/mcp_client_config.md
Thales Maciel 535efc6919 Add project-aware chat startup defaults 
Make repo-root chat startup native by letting MCP servers carry a default project source for workspace creation. When a chat host starts from a Git checkout, workspace_create can now omit seed_path and inherit the server startup source; explicit --project-path and clean-clone --repo-url/--repo-ref paths are supported as fallbacks.

Add project startup resolution and materialization, surface origin_kind/origin_ref in workspace_seed, update chat-host docs and the repro/fix smoke to use project-aware workspace creation, and switch dist-check to uv run pyro so verification stays stable after uv reinstalls.

Validated with uv lock, focused startup/server/CLI pytest coverage, UV_CACHE_DIR=.uv-cache make check, UV_CACHE_DIR=.uv-cache make dist-check, and real guest-backed smokes for both explicit project_path and bare repo-root auto-detection.
2026-03-13 15:51:47 -03:00

1.7 KiB
Raw Blame History

MCP Client Config Example

Default for most chat hosts in 4.x: workspace-core.

Use the host-specific examples first when they apply:

Use this generic config only when the host expects a plain mcpServers JSON shape.

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

Generic stdio MCP configuration using uvx:

{
  "mcpServers": {
    "pyro": {
      "command": "uvx",
      "args": ["--from", "pyro-mcp", "pyro", "mcp", "serve"]
    }
  }
}

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

{
  "mcpServers": {
    "pyro": {
      "command": "pyro",
      "args": ["mcp", "serve"]
    }
  }
}

If the host does not preserve the server working directory and you want the first workspace_create to start from a specific checkout, add "--project-path", "/abs/path/to/repo" after "serve" in the same args list.

Profile progression:

  • workspace-core: the default and recommended first persistent chat profile
  • vm-run: expose only vm_run
  • workspace-full: explicit advanced opt-in for 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.

Other generic-client examples: