PI API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-filterable-attributesB | Get the list of attributes that can be used for filtering by examining a sample entity |
| check-connectionA | Check if the current API URL and authentication are valid |
| set-api-urlA | Set the API base URL for all requests |
| authenticateC | Guide for authenticating with the PI API |
| keep-session-aliveC | Verify and refresh the current authentication token (also used for token-based authentication) |
| authenticate-with-credentialsA | Authenticate with the PI API using username and password (last resort option) |
| logoutA | Invalidate the current token and end the session |
| set-organizationA | Set the organization ID for subsequent requests |
| list-categoriesC | List all categories with filtering support |
| get-categoryB | Get a category by ID |
| create-categoryC | Create a new category |
| update-categoryB | Update an existing category |
| delete-categoryC | Delete a category |
| list-category-objectsB | List all objects for a specific category |
| list-chartsC | List all charts with filtering support |
| get-chartA | Get a chart by ID |
| delete-chartB | Delete a chart |
| export-chartC | Export a chart in various formats |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-categories | Analyze categories in the dashboard |
| analyze-charts | Analyze charts in the dashboard |
| compare-charts | Compare data between two charts |
| category-usage-analysis | Analyze how categories are being used in charts |
| use-filters | Shows how to use filters effectively with this API |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| auth-status | |
| categories-list | |
| charts-list |
TDQS
Scored across 18 tools
All 18 tools have clearly distinct purposes. Authentication tools (authenticate, authenticate-with-credentials, check-connection, keep-session-alive, logout) each serve a unique role, and the CRUD tools for categories and charts are well-separated. There is no ambiguity between any pair.
All tool names follow a consistent lowercase-with-hyphens pattern, with verb-noun structure (e.g., create-category, list-charts). Minor exceptions like 'authenticate' (single verb) still fit the pattern, and there is no mixing of conventions.
18 tools is a well-scoped number for a PI API server covering authentication, configuration, category management, and chart operations. It is neither too sparse nor overwhelming, providing a focused yet comprehensive surface.
The tool set includes full CRUD for categories (create, read, update, delete) but only read, delete, and export for charts, missing create and update. This is a notable gap that could hinder agent workflows involving chart lifecycle management.