The problem
I use Pi as one of my primary coding agents and want to connect it to Executor, but Pi does not have native MCP support.
Executor's "Connect an agent" flow works well for MCP clients like Codex, Claude Code, and Cursor, but there is no first-party path for Pi. The current workaround is to install a third-party pi-executor extension, which means trusting an unofficial adapter for something that handles access to potentially sensitive Executor integrations.
I'd like to be able to install an Executor-maintained Pi integration and get the same low-context tool discovery/execute workflow that other agents receive.
Concrete example:
- I have Executor running locally with Chrome, Computer Use, GitHub, etc.
- I use Pi as my coding agent.
- I want one supported command to connect Pi to Executor.
- Pi should expose Executor's small execute/search/resume surface rather than loading every underlying tool schema.
Proposed shape
Provide an official Pi adapter maintained by UsefulSoftwareCo.
Ideally the Integrations / "Connect an agent" screen would include Pi alongside the other supported agents and show a command such as:
pi install npm:@usefulsoftwareco/pi-executor
(or whatever package/name fits the project).
The extension should:
- Connect to the local/remote Executor instance.
- Expose a minimal tool surface such as execute/search/resume.
- Preserve Executor's lazy tool discovery so Pi's context stays small.
- Support Executor authentication/configuration without embedding secrets in the package config.
- Work with Pi's normal extension/package system.
- Be documented and versioned alongside Executor.
If a dedicated extension is not desirable, an officially documented and supported Pi integration path would still be useful.
The main thing I'm asking for is a first-party, trusted way to use Executor from Pi without depending on an unofficial community adapter.
Alternatives
No response
Where it belongs
Not sure
Before you submit
The problem
I use Pi as one of my primary coding agents and want to connect it to Executor, but Pi does not have native MCP support.
Executor's "Connect an agent" flow works well for MCP clients like Codex, Claude Code, and Cursor, but there is no first-party path for Pi. The current workaround is to install a third-party
pi-executorextension, which means trusting an unofficial adapter for something that handles access to potentially sensitive Executor integrations.I'd like to be able to install an Executor-maintained Pi integration and get the same low-context tool discovery/execute workflow that other agents receive.
Concrete example:
Proposed shape
Provide an official Pi adapter maintained by UsefulSoftwareCo.
Ideally the Integrations / "Connect an agent" screen would include Pi alongside the other supported agents and show a command such as:
(or whatever package/name fits the project).
The extension should:
If a dedicated extension is not desirable, an officially documented and supported Pi integration path would still be useful.
The main thing I'm asking for is a first-party, trusted way to use Executor from Pi without depending on an unofficial community adapter.
Alternatives
No response
Where it belongs
Not sure
Before you submit