customplanview MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLANVIEW_SCOPES | No | Optional comma-separated scopes sent to the API. | |
| PLANVIEW_BASE_URL | Yes | Base URL for your Planview tenant or API gateway. | |
| PLANVIEW_API_TOKEN | Yes | Bearer token used for read-only API requests. | |
| PLANVIEW_API_VERSION | No | API version. Defaults to 2026-08. | 2026-08 |
| PLANVIEW_PORTFOLIOS_PATH | No | Portfolio route. Defaults to /api/portfolios. | /api/portfolios |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| planview_list_portfoliosC | List portfolios from Planview Portfolios Enterprise. |
| planview_get_portfolioB | Get one portfolio by its Planview identifier. |
| planview_search_portfoliosC | Search portfolios by a tenant-supported text query. |
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
The three tools have clearly distinct purposes: list all portfolios, get one by identifier, and search by text query. No two tools could reasonably be confused for the same operation, and the descriptions make the boundaries explicit.
All tools follow the same predictable pattern: the planview_ prefix plus verb_noun (list_portfolios, get_portfolio, search_portfolios). The convention is consistent in both prefix and snake_case style.
Three tools is a minimal but reasonable set for a portfolio-focused read surface. It is slightly under-scoped for a server named customplanview, which might be expected to cover more Planview entities.
The read surface for portfolios is fairly complete with list, get, and search, but there are no create, update, or delete operations. For a portfolio management domain, those missing lifecycle operations are a notable gap.