Pi MCP Server

Pi MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Typed, sandboxed Code Mode access to configured MCP servers for Pi.

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:

• Agent — written code is type-checked before execution
• preflight — code did not run and no upstream call was made
• runtime — the sandbox or an upstream call failed after execution started
• result — the call graph completed, but the returned value exceeded resultLimitKiB

Configuration and credentials

You will need one environment variable: GRAFANA_MCP_TOKEN. 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

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pi's toolset — Agent, preflight, runtime and 1 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.

This entry was verified against Pi's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.