Pi MCP Server

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. 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.

Choosing this one

Recorded tools

• 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.

Setup and compatibility

This listing has no verified copy-paste launch configuration. Use the project documentation to confirm the entry point, runtime and authentication before registering it in your MCP client. A package name or repository alone is not a runnable configuration.

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.