Planview MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OKTA_USERNAME | Yes | Your email address for Okta authentication | |
| PLANVIEW_BASE_URL | Yes | Your company's Planview URL | |
| PLANVIEW_STORAGE_STATE | No | Path to store authentication state (default: planview-auth.json) | planview-auth.json |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| planview_get_work_itemsA | Get a list of work items from Planview with optional filters |
| planview_get_work_itemA | Get details of a specific work item by ID |
| planview_update_work_itemC | Update a work item with new data |
| planview_get_projectsC | Get a list of projects from Planview with optional filters |
| planview_get_projectA | Get details of a specific project by ID |
| planview_execute_requestB | Execute a custom API request to Planview. Useful for advanced operations not covered by other tools. |
| planview_get_current_userA | Get information about the currently authenticated user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Planview Dashboard | Current user dashboard data and metrics |
| My Work Items | Work items assigned to the current user |
TDQS
Scored across 7 tools
Each tool targets a distinct resource or action: work items, projects, current user, and a catch-all custom request tool that is explicitly positioned for operations not otherwise covered. There is no meaningful overlap between the specific get/update tools.
All tools follow a consistent planview_ prefix and use clear verb_noun naming: get_work_items, get_work_item, update_work_item, get_projects, get_project, execute_request, get_current_user. The pattern is predictable and easy to navigate.
Seven tools is a well-scoped size for a project management server. Each tool serves a clear purpose, and the set is neither bloated nor too thin.
The server covers listing, reading, and updating work items, plus reading projects, but lacks direct create/delete operations for common resources. The custom execute_request tool can fill some gaps, but the dedicated surface is incomplete for full lifecycle management.