Pi MCP Server

Pi MCP server exists for a simple reason — assistants are far more useful when they can act on Pi directly instead of describing what you should do. Pi extension that delegates prompts to agents on a self-hosted Trinity agent platform (https://github.com/Abilityai/trinity) via its MCP endpoint (HTTP+SSE Streamable transport). Config-less auth via env vars. Surfaces a curated subset of.

What you get

Trinity is an open-source platform for deploying, orchestrating, and governing fleets of autonomous AI agents on your own hardware. It exposes a MCP (Model Context Protocol) endpoint at https://<your-trinity-host>/mcp that lists dozens of tools for agent CRUD, scheduled loops, fleet health, event subscriptions, file sharing, voice calling, and more.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Pi is connected, these are the calls the assistant has available:

• trinity_chat — chat_with_agent — send a prompt to any agent
• trinity_agents_list — list_agents — list all deployed agents
• trinity_get_agent — get_agent — detailed info on one agent
• trinity_fleet_health — get_fleet_health — fleet-wide health rollup
• trinity_get_agent_health — get_agent_health — deep health for one agent
• trinity_get_agent_logs — get_agent_logs — tail container logs

Configuration and credentials

You will need 2 environment variables: TRINITY_URL, TRINITY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the pi mcp server does with a few real requests.

Choosing this one

Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pi's toolset — trinity_chat, trinity_agents_list, trinity_get_agent and 3 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.