Skip to content

docs: pippy as the landing spot for CLI dispatch and MCP install - #12

Open
ShahriarAhnaf wants to merge 2 commits into
mainfrom
agent/mcp-dispatch-docs-9f2a
Open

docs: pippy as the landing spot for CLI dispatch and MCP install#12
ShahriarAhnaf wants to merge 2 commits into
mainfrom
agent/mcp-dispatch-docs-9f2a

Conversation

@ShahriarAhnaf

Copy link
Copy Markdown
Contributor

Summary

  • Records that pippy (the simantic PyPI package) is the intended landing
    spot for two not-yet-built extensions of its existing role: the Sim
    backend dispatch growing into the CLI, and the client-side install point
    for a future unified MCP server (mirroring how it already installs the
    simulation engines).
  • Links the new docs/unified-surface.md from README.md's backend section
    and docs/session-api.md's "Why not MCP" section.

No code changes — this documents direction discussed with the maintainer
before any implementation starts.

Test plan

  • Docs-only change; nothing to run.

Both the Sim backend dispatch and an eventual unified MCP server's
client-side install belong in this package, for the same reason it
already installs the engines instead of asking a user to find them.
Writing the direction down before the code exists.
…ing the other

Renode and pyrite have genuinely different capabilities — the gdb_* control
plane and multi-machine/CAN/radio scenarios don't exist on the Rust side —
so the unified surface is a Sim(backend=...)-shaped front door, with each
engine keeping its own tool implementation behind it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant