thaloco/pyro-mcp
1
Fork 0
Code Pull requests Releases Packages Activity Actions
pyro-mcp/examples/mcp_client_config.md
Thales Maciel c00c699a9f Make workspace-core the default MCP profile 
Flip bare pyro mcp serve, create_server(), and Pyro.create_server() to default to workspace-core in 4.0.0 while keeping workspace-full as the explicit advanced opt-in surface.

Rewrite the MCP-facing docs and host-specific examples around the bare default command, update package and catalog compatibility to 4.x, and move the public-contract wording from 3.x compatibility guidance to the new stable default.

Adjust the server, API, and contract tests so bare server creation now asserts the workspace-core tool set, while explicit workspace-full coverage continues to prove shells, services, snapshots, and disk tools remain available.

Validation: uv lock; .venv/bin/pytest --no-cov tests/test_cli.py tests/test_api.py tests/test_server.py tests/test_public_contract.py; UV_CACHE_DIR=.uv-cache make check; UV_CACHE_DIR=.uv-cache make dist-check; real guest-backed smoke for bare Pyro.create_server() plus explicit profile="workspace-full".
2026-03-13 14:14:15 -03:00

1.4 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"]
    }
  }
}

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: