P4plan-mcp Server

MCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API.

Local serverstdio

What is the P4plan-mcp Server?

P4plan-mcp is an MCP integration. MCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API.

Packages and local setup

The published npm package is @perforce/p4plan-mcp, version 2026.3.1. Its declared MCP transport is stdio.

The package declares P4PLAN_API_AUTH_TOKEN (required): JWT bearer token for the P4 Plan GraphQL API. Forwarded as Authorization on every tool call.; P4PLAN_API_URL: URL of the P4 Plan GraphQL API (default: http://localhost:4000).; P4PLAN_ALLOW_SELF_SIGNED_CERTS: Set to 'true' to accept self-signed TLS certificates from the GraphQL API. Default: false..

The published oci package is docker.io/perforce/p4plan-mcp:2026.3.1. Its declared MCP transport is stdio.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 2026.3.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
P4PLAN_API_AUTH_TOKENJWT bearer token for the P4 Plan GraphQL API. Forwarded as Authorization on every tool call.Yes
P4PLAN_API_URLURL of the P4 Plan GraphQL API (default: http://localhost:4000).Optional
P4PLAN_ALLOW_SELF_SIGNED_CERTSSet to 'true' to accept self-signed TLS certificates from the GraphQL API. Default: false.Optional