pi-kb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PI_KB_BIND | No | Mode B only. Host bind, if you uncomment the `ports` section. Unused by default. | |
| AVEVA_KB_TOKEN | No | Use this bearer token instead of the cached session. Fallback for headless machines and Linux without GTK/WebKit. | |
| PI_KB_MCP_SECRET | No | Mode B only. Shared secret gating the HTTP server; 24 characters minimum. | |
| PI_KB_MCP_COOKIES | No | Mode B only. Where pushed portal cookies are stored. | |
| PI_KB_MCP_SESSION | No | Override the session file location. | |
| PI_KB_MCP_ALOWED_HOSTS | No | Mode B only. Comma-separated hostnames to accept, e.g. `kb.example.com`. Unset disables the SDK's DNS-rebinding check. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pi_kbA | Search AVEVA's Customer Support knowledge base and return matching article numbers, titles, products and excerpts. Use this for support-desk material: specific error messages, known issues, version incompatibilities, workarounds and how-to notes. Prefer product documentation tools for conceptual or reference questions (what a feature is, configuration reference, API syntax); reach here when the user reports something broken or quotes an error. Read-only; no side effects. Scoped to English-language Knowledge Base articles, excluding product documentation, community posts and product news. Requires a signed-in AVEVA support session — with none, it returns an instruction to run |
| get_kb_articleA | Fetch the full text of one AVEVA knowledge base article, including its symptoms, cause and resolution sections. Use after search_pi_kb to read an article whose excerpt looks relevant, or directly whenever the user supplies an article number or a softwaresupportsp.aveva.com link. Search excerpts are truncated and routinely omit the actual fix, so read the article before answering from a search result alone. Read-only; no side effects. Returns a header line with title, products, article type and last-updated date, then the article body converted from HTML to plain text and truncated at max_chars, with a marker when cut. |
| list_kb_productsA | List AVEVA product names accepted by the products argument of search_pi_kb, optionally filtered by a substring. Use when a search returns results spanning unrelated products and you need the exact spelling to narrow it, or when the user names a product informally ('PI AF', 'Data Archive') and you need AVEVA's canonical form. Not needed for a first, unscoped search. Read-only; no side effects. AVEVA publishes over a thousand product names, so with no argument this returns only PI System products; pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: search returns article matches, get_kb_article retrieves full article text, and list_kb_products supplies valid product names for search filtering. There is no overlap in what the tools do, and the descriptions reinforce when each should be used.
All tool names follow a consistent verb_noun pattern using underscores: search_, get_, list_. The shared 'kb' component in each name further ties them together as a cohesive set with no mixed naming conventions.
Three tools is perfectly scoped for this server's purpose: search the knowledge base, read a specific article, and list valid product filters. Every tool fulfills a necessary step in the workflow, and none feel superfluous or missing.
The read-only knowledge base workflow is fully covered: search with optional product filtering, retrieve full article text, and resolve product names. The descriptions also handle edge cases like unsigned sessions and truncated excerpts, leaving no obvious dead ends for the stated domain.