Hosts
Hosts
The four hosts one tool definition reaches. What each adapter gives its host and which peer it needs
| Failure | |||
|---|---|---|---|
| MCP servermcp | createMcpServer | @modelcontextprotocol/server >=2.2.0 <3 | isError: true |
| Pi extensionpi | registerPiTools | @earendil-works/pi-coding-agent >=0.84.2 <1 | thrown |
| OMP extensionomp | registerOmpTools | @oh-my-pi/pi-coding-agent >=18.0.0 <19 | isError, bad input thrown |
| AI SDK toolai | toAiTool | ai >=7.0.0 <8 | thrown, tool error |
Four hosts, four adapters, one list of tools. Every peer is optional, so a package that only ships an MCP server never installs the AI SDK. Each row links to what that host really receives, registered in your browser from the same definition the landing uses.
Which ones do I need?
All of them, if you're an agntn package. That's the deal: every package serves the same tools to MCP, Pi, OMP and the AI SDK.
For your own project, the ones your users run. An MCP server reaches Claude Code, Cursor and every other MCP client. Pi and OMP are coding agents with their own extension systems, and a native extension beats going through MCP there: prompt snippets, approval tiers, status lines. The AI SDK is for when you're the one building the agent.