pi-mcp-py 0.1.0__tar.gz

pi_mcp_py-0.1.0/.gitignore

@@ -0,0 +1,34 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+dist/
+build/
+!tui/crates/build/
+.pytest_cache/
+.pytest-audit/
+.mypy_cache/
+.ruff_cache/
+.venv/
+.venv-*/
+venv/
+.env
+# Rust TUI workspace (Apache-2.0 fork under tui/)
+tui/target/
+**/*.rs.bk
+
+# Benchmark evaluation cache and trial artifacts
+.cache/
+.pi-eval/
+
+# Temporary files, coverage and logs
+*.log
+*.tmp
+*.bak
+*.swp
+*.orig
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+

pi_mcp_py-0.1.0/PKG-INFO

@@ -0,0 +1,83 @@
+Metadata-Version: 2.5
+Name: pi-mcp-py
+Version: 0.1.0
+Summary: Connects the MCP servers an ACP client passes to the pi-python agent (an extension)
+Project-URL: Homepage, https://github.com/zy1233/pi-python
+Project-URL: Repository, https://github.com/zy1233/pi-python
+Author-email: zy1233 <zy1233@users.noreply.github.com>
+License-Expression: MIT
+Keywords: acp,agent,extension,mcp,pi
+Requires-Python: >=3.11
+Requires-Dist: anyio>=4.5
+Requires-Dist: httpx>=0.27
+Requires-Dist: langchain-mcp-adapters>=0.3.2
+Requires-Dist: mcp<2,>=1.30
+Requires-Dist: pi-agent-core-lc>=0.6.0
+Description-Content-Type: text/markdown
+
+# pi-mcp-py
+
+An extension for [pi-python](https://github.com/zy1233/pi-python). It connects the MCP servers that an
+ACP client (an editor such as Zed) passes to the agent, and gives their tools to the model.
+
+The agent itself has no MCP client. Without this package, the servers that the editor passes are not
+connected, and the agent says so. With it, the agent connects them.
+
+Install it into the environment of the agent:
+
+```bash
+pip install pi-mcp-py
+```
+
+The package is on PyPI from the 0.6.0 release of pi-python. In a checkout of the repository, use
+`pip install -e ./packages/pi-mcp`.
+
+Nothing else to set up. The servers come from the editor (Zed: `context_servers` in the settings).
+It needs `pi-agent-core-lc` 0.6.0 or later: an older core does not hand over the servers of the
+client, and then the package logs a warning and does nothing.
+
+## What it does
+
+- Connects `stdio`, `http` (Streamable HTTP) and `sse` servers. One connection for each server and
+  session. A server that does not start does not stop the session, nor the other servers.
+- Gives each tool to the model as `mcp__<server>__<tool>`. The prefix keeps an MCP tool from replacing a
+  built-in tool of the same name. A name longer than 64 characters is cut and gets a hash at the end.
+- Tells the user when a server fails to start or is slow. It says nothing when all is well.
+- Connects a server again when it has stopped: the next tool call does it, at most 3 times in a row (a
+  call that gets an answer starts the count again). A call that was already sent when the server died
+  is not sent again, because the server may have run it. It fails with the reason.
+- `/mcp` shows the servers, their state and the number of tools. `/mcp reconnect <name>` connects one
+  again, with no limit.
+- Ends every server process when the session ends (Windows and Linux).
+- Limits: a server may take 60 s to start and a call 120 s (see **Settings**). The first turn waits at
+  most 10 s for a server that still starts. A tool result of more than 50 KB of text is cut, and a note
+  says so.
+
+## Things to know
+
+- **Permissions.** A tool call is asked about in the `ask` mode of the CLI, unless the server marks the
+  tool with a hint that says it is harmless (`readOnlyHint`). The hints are taken as the server gives
+  them: you chose the server.
+- **Environment of a stdio server.** It gets the safe list of the MCP SDK, the proxy and certificate
+  variables of the agent (`HTTP_PROXY`, `SSL_CERT_FILE`, ...), and the `env` of the editor. It does not
+  get the other variables of the agent, the LLM keys among them. `${VAR}` in a value is not expanded.
+- **Secrets.** The `env`, `headers`, `args` and `url` of a server are not written to a log, a notice, the
+  `/mcp` output or an error text.
+- **Logs.** The stderr of a stdio server goes to `<PI_HOME>/logs/mcp/<name>.log` (`PI_HOME` is
+  `~/.pi-python` when it is not set). The file is appended to, and started over when it is larger than
+  512 KB. The text of the file is what the server wrote: it may hold what the server was given.
+- **Servers on this machine.** An `http` or `sse` server at `localhost`, `127.0.0.1` or `::1` is
+  reached directly, not through the proxy of the system (`httpx` would send it there).
+- **Not supported:** MCP resources, prompts, sampling, roots, elicitation, OAuth, `tools/list_changed`,
+  websocket servers.
+
+## Settings
+
+Environment variables only:
+
+| Variable | Default | Meaning |
+|----------|---------|---------|
+| `PI_MCP_STARTUP_TIMEOUT` | 60 | Seconds a server may take to start. Then it counts as failed. |
+| `PI_MCP_CALL_TIMEOUT` | 120 | Seconds a tool call may take. |
+
+The design is in `docs/specs/2026-10-23-mcp-extension-design.md` of the repository.

pi_mcp_py-0.1.0/README.md

@@ -0,0 +1,66 @@
+# pi-mcp-py
+
+An extension for [pi-python](https://github.com/zy1233/pi-python). It connects the MCP servers that an
+ACP client (an editor such as Zed) passes to the agent, and gives their tools to the model.
+
+The agent itself has no MCP client. Without this package, the servers that the editor passes are not
+connected, and the agent says so. With it, the agent connects them.
+
+Install it into the environment of the agent:
+
+```bash
+pip install pi-mcp-py
+```
+
+The package is on PyPI from the 0.6.0 release of pi-python. In a checkout of the repository, use
+`pip install -e ./packages/pi-mcp`.
+
+Nothing else to set up. The servers come from the editor (Zed: `context_servers` in the settings).
+It needs `pi-agent-core-lc` 0.6.0 or later: an older core does not hand over the servers of the
+client, and then the package logs a warning and does nothing.
+
+## What it does
+
+- Connects `stdio`, `http` (Streamable HTTP) and `sse` servers. One connection for each server and
+  session. A server that does not start does not stop the session, nor the other servers.
+- Gives each tool to the model as `mcp__<server>__<tool>`. The prefix keeps an MCP tool from replacing a
+  built-in tool of the same name. A name longer than 64 characters is cut and gets a hash at the end.
+- Tells the user when a server fails to start or is slow. It says nothing when all is well.
+- Connects a server again when it has stopped: the next tool call does it, at most 3 times in a row (a
+  call that gets an answer starts the count again). A call that was already sent when the server died
+  is not sent again, because the server may have run it. It fails with the reason.
+- `/mcp` shows the servers, their state and the number of tools. `/mcp reconnect <name>` connects one
+  again, with no limit.
+- Ends every server process when the session ends (Windows and Linux).
+- Limits: a server may take 60 s to start and a call 120 s (see **Settings**). The first turn waits at
+  most 10 s for a server that still starts. A tool result of more than 50 KB of text is cut, and a note
+  says so.
+
+## Things to know
+
+- **Permissions.** A tool call is asked about in the `ask` mode of the CLI, unless the server marks the
+  tool with a hint that says it is harmless (`readOnlyHint`). The hints are taken as the server gives
+  them: you chose the server.
+- **Environment of a stdio server.** It gets the safe list of the MCP SDK, the proxy and certificate
+  variables of the agent (`HTTP_PROXY`, `SSL_CERT_FILE`, ...), and the `env` of the editor. It does not
+  get the other variables of the agent, the LLM keys among them. `${VAR}` in a value is not expanded.
+- **Secrets.** The `env`, `headers`, `args` and `url` of a server are not written to a log, a notice, the
+  `/mcp` output or an error text.
+- **Logs.** The stderr of a stdio server goes to `<PI_HOME>/logs/mcp/<name>.log` (`PI_HOME` is
+  `~/.pi-python` when it is not set). The file is appended to, and started over when it is larger than
+  512 KB. The text of the file is what the server wrote: it may hold what the server was given.
+- **Servers on this machine.** An `http` or `sse` server at `localhost`, `127.0.0.1` or `::1` is
+  reached directly, not through the proxy of the system (`httpx` would send it there).
+- **Not supported:** MCP resources, prompts, sampling, roots, elicitation, OAuth, `tools/list_changed`,
+  websocket servers.
+
+## Settings
+
+Environment variables only:
+
+| Variable | Default | Meaning |
+|----------|---------|---------|
+| `PI_MCP_STARTUP_TIMEOUT` | 60 | Seconds a server may take to start. Then it counts as failed. |
+| `PI_MCP_CALL_TIMEOUT` | 120 | Seconds a tool call may take. |
+
+The design is in `docs/specs/2026-10-23-mcp-extension-design.md` of the repository.

pi_mcp_py-0.1.0/pi_mcp/__init__.py

@@ -0,0 +1,71 @@
+"""pi-mcp: connect the MCP servers that an ACP client passes (design: docs/specs/2026-10-23-mcp-
+extension-design.md).
+
+An editor such as Zed hands the agent its configured MCP servers in ``session/new``,
+``session/load`` and ``session/resume``. The agent has no MCP client of its own. This extension
+connects them: stdio, http and sse servers, one connection per server and session. Their tools
+reach the model as ``mcp__<server>__<tool>``; ``/mcp`` shows the state of the servers.
+
+Install: ``pip install pi-mcp-py`` (or ``pip install -e ./packages/pi-mcp`` from a checkout of the
+repository). Nothing is configured here: the servers come from the editor.
+
+Environment variables:
+  - ``PI_MCP_STARTUP_TIMEOUT`` -- seconds a server may take to start (default 60)
+  - ``PI_MCP_CALL_TIMEOUT``    -- seconds a tool call may take (default 120)
+"""
+
+from __future__ import annotations
+
+import logging
+from typing import TYPE_CHECKING, Any
+
+if TYPE_CHECKING:
+    from pi_agent_core.extensions import ExtensionAPI
+
+__all__ = ["activate"]
+
+logger = logging.getLogger(__name__)
+
+
+def activate(pi: ExtensionAPI) -> None:
+    """Extension entry point: take over the servers the client passed, start them later.
+
+    No I/O happens here (a failing ``activate`` is rolled back, and a started child process
+    would not be). The servers start in the ``session_start`` hook, each in a task of its own.
+    """
+    try:
+        servers = tuple(pi.client_mcp_servers)
+    except AttributeError:
+        logger.warning(
+            "pi-mcp needs a newer pi-agent-core-lc (0.6.0 or later): this one does not hand over "
+            "the MCP servers of the client. pi-mcp does nothing."
+        )
+        return
+    except RuntimeError:  # no harness behind this API (a test, a bare registry)
+        servers = ()
+
+    from pi_mcp.manager import Manager
+    from pi_mcp.settings import Settings
+
+    manager = Manager(pi, servers, settings=Settings.from_env())
+    if servers:
+        pi.claim_client_mcp_servers([server.name for server in servers])
+
+        def on_session_start(_event: Any) -> None:
+            try:
+                manager.start()
+            except Exception:  # a handler that raises would fail the load of every extension
+                logger.warning("pi-mcp could not start the MCP servers", exc_info=True)
+
+        pi.on("session_start", on_session_start)
+        pi.add_turn_barrier(manager.wait_started)
+        pi.register_cleanup(manager.close)
+
+    async def mcp_command(args: str) -> None:
+        pi.send_message(await manager.command(args))
+
+    pi.register_command(
+        "mcp",
+        description="Show the MCP servers of this session (/mcp reconnect <name> to reconnect)",
+        handler=mcp_command,
+    )