Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@customplanview MCP server search portfolios for digital transformation"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Read-only Model Context Protocol access to Planview Portfolios Enterprise, targeting the August 2026 API version (2026-08).
The server runs over stdio and is suitable for VS Code, Claude Desktop, and the MCP Inspector.
List portfolios with pagination and an optional status filter
Get a portfolio by ID
Search portfolios by text
Forward the configured API version with every request
Keep the tool surface read-only
Related MCP server: baihua-mcp-server
Install or obtain the following before starting:
Node.js 20 or newer
Access to a Planview Portfolios Enterprise tenant
A bearer token with permission to read portfolio data
The portfolio API route used by your tenant or API gateway
Check your installations:
node --version
npm --versionFrom the project directory, run:
npm installCopy the example file:
Copy-Item .env.example .envOpen .env and set the required values:
PLANVIEW_BASE_URL=https://your-planview-tenant.example.com
PLANVIEW_API_TOKEN=replace-with-your-bearer-token
PLANVIEW_API_VERSION=2026-08
PLANVIEW_PORTFOLIOS_PATH=/api/portfoliosOptional scopes can be supplied as a comma-separated list:
PLANVIEW_SCOPES=portfolio.read,portfolio.listVariable | Required | Description |
| Yes | Base URL for your Planview tenant or API gateway. |
| Yes | Bearer token used for read-only API requests. |
| No | API version. Defaults to |
| No | Portfolio route. Defaults to |
| No | Comma-separated scopes sent to the API. |
The default portfolio path is a placeholder convention. Confirm the exact route and authentication requirements in your tenant's Planview August 2026 API documentation before connecting.
Run the TypeScript check and build the server:
npm run check
npm run buildBoth commands should complete without errors. The compiled server is written to dist/.
Run the compiled server:
npm startOr run directly from TypeScript during development:
npm run devThis is a stdio server. It does not open a web port, and stdout must remain reserved for MCP protocol messages.
The repository includes .vscode/mcp.json.
Make sure .env contains your tenant URL and token.
Open the project in VS Code.
Open the MCP view or chat tools panel.
Start planview-portfolios-enterprise.
Ask your MCP client to list, search, or retrieve portfolios.
VS Code starts the server with npm run dev and loads variables from the workspace .env file.
Tool | Inputs | Purpose |
|
| Return a page of portfolios. |
|
| Return one portfolio by identifier. |
|
| Search portfolios using the tenant's query behavior. |
All tools make GET requests. No create, update, or delete operations are exposed.
PLANVIEW_BASE_URL is requiredMake sure .env exists and contains a valid PLANVIEW_BASE_URL value.
PLANVIEW_API_TOKEN is requiredAdd a valid bearer token to .env. Do not commit or share this file.
Planview request failed (404 ...)Your tenant likely uses a different route. Update PLANVIEW_PORTFOLIOS_PATH after confirming the correct August 2026 API path.
Planview request failed (401 ...) or (403 ...)Verify that the token is active, is intended for the configured tenant, and has the required read permissions or scopes.
Run npm run build, confirm that Node.js is version 20 or newer, and restart the MCP client. For protocol-level inspection, run the server through MCP Inspector.
.env is excluded from Git by .gitignore.
Use a short-lived, least-privilege read token where possible.
Never place tokens in source code, prompts, issues, or logs.
Review tenant response shapes and pagination behavior before extending the server.
Keep new capabilities read-only unless a separate write capability is explicitly reviewed.
src/server.ts MCP server and Planview HTTP client
.vscode/mcp.json VS Code MCP launch configuration
.env.example Environment template
.github/copilot-instructions.md Project-specific development guidancenpm install # Install dependencies
npm run check # Type-check without emitting files
npm run build # Compile to dist/
npm run dev # Run TypeScript directly
npm start # Run the compiled serverPrivate application code. Add the license required by your organization before publishing.
Get one portfolio by its Planview identifier.
Inputs: portfolioId (required).
List portfolios from Planview Portfolios Enterprise.
Inputs: limit, offset, status.
Search portfolios by a tenant-supported text query.
Inputs: query (required), limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Ovanek MCP: Model Context Protocol server for Ovanek platform tools; writes are dry-run by default.
Query SEC EDGAR filings, XBRL financials, and company data via MCP. STDIO or Streamable HTTP.
The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.
Model Context Protocol server for todo.vu task management and time tracking.
