thaloco/pyro-mcp
1
Fork 0
Code Pull requests Releases Packages Activity Actions
pyro-mcp/examples/mcp_client_config.md
Thales Maciel 68d8e875e0 Add host-specific MCP onramps for major chat clients 
Ship first-class MCP setup examples for Claude Code, Codex, and OpenCode so new users can copy one exact command or config instead of translating the generic MCP template by hand.

Reposition the docs to surface those host-specific examples before the generic config fallback, keep workspace-core as the recommended profile everywhere user-facing, and retain Claude Desktop/Cursor as secondary fallback examples.

Bump the package and catalog to 3.11.0, mark the roadmap milestone done, and add docs-alignment coverage that pins the new examples to the canonical workspace-core server command and the expected OpenCode config shape.

Validation:
- uv lock
- ./.venv/bin/pytest --no-cov tests/test_cli.py
- UV_CACHE_DIR=.uv-cache make check
- UV_CACHE_DIR=.uv-cache make dist-check
2026-03-13 13:42:45 -03:00

1.5 KiB
Raw Blame History

MCP Client Config Example

Recommended default for most chat hosts: 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", "--profile", "workspace-core"]
    }
  }
}

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

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

Profile progression:

  • workspace-core: the recommended first persistent chat profile
  • vm-run: expose only vm_run
  • workspace-full: advanced 3.x compatibility surface 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: