Pi Api MCP Server

An MCP server for interacting with the PI Dashboard API

Local serverstdio

What is the Pi Api MCP server?

Connect Pi Api to Claude, Cursor or any other MCP client and it stops being a tab you switch to. An MCP server for interacting with the PI Dashboard API. The pi api mcp server is what makes that connection.

What the server does

A Model Context Protocol (MCP) server that provides standardized tools and resources for interacting with the PI Dashboard API. This implementation enables Claude and other MCP-compatible AI assistants to securely access and manage PI Dashboard resources, including categories and charts.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Authentication — The Authentication tool exposed by this server
  • Categories — The Categories tool exposed by this server
  • Charts — The Charts tool exposed by this server

Installation

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Credentials and setup notes

Configuration is passed through the environment: PI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

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 Api's toolset — Authentication, Categories, Charts — is a fair guide to whether it matches your workflow. It is maintained by mingzilla; worth a glance at recent repository activity before you build anything load-bearing on it.

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

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
AuthenticationThe Authentication tool exposed by this server.
CategoriesThe Categories tool exposed by this server.
ChartsThe Charts tool exposed by this server.

How to install the Pi Api MCP server

{
  "mcpServers": {
    "pi-api": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "PI_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
PI_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Pi Api to Authentication.
  • Use Pi Api to Categories.
  • Use Pi Api to Charts.

Frequently asked questions

It connects Pi Api to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Authentication, Categories, Charts) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Pi Api directly.