Log inSubmit server
P4plan MCP logo

P4plan MCP

Connects AI clients to P4 Plan project data through a stateless stdio server and GraphQL API.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install P4plan MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "p4plan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@perforce/p4plan-mcp"
      ],
      "env": {
        "P4PLAN_API_AUTH_TOKEN": "YOUR_VALUE_HERE",
        "P4PLAN_API_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @perforce/p4plan-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 16d ago.

Overview

The p4plan-mcp MCP server connects MCP clients to P4 Plan through its GraphQL API. It exposes project-management data for tasks, bugs, sprints, releases, comments, and custom fields, with projectId available as a parameter. The server runs as a child process over stdio and forwards a JWT bearer token on each request. Reach for it when an assistant needs to inspect or work with P4 Plan data from Claude Desktop or VS Code.

Use cases

  • Search P4 Plan tasks within a project
  • Review bugs and scheduled work
  • Inspect sprint and release records
  • Work with comments and custom fields

Key features

  • P4 Plan GraphQL API access
  • Stdio MCP transport
  • JWT authentication
  • Project-scoped requests
  • Task search result limits
  • Docker and npx deployment

Tools2

What P4plan MCP lets your agent do. Expand a tool for its parameters.

Self-reported~25 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @perforce/p4plan-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads626Package downloads in the last 30 days.
Last commit22d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed2Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How P4plan MCP works

What p4plan-mcp MCP server does

The p4plan-mcp MCP server gives MCP-compatible assistants access to P4 Plan project-management data. Its supported domain objects include backlog tasks, scheduled tasks, bugs, sprints, releases, and sprint tasks. The listed functionality also covers comments and custom fields, allowing an assistant to work with more than a basic task list.

Operations are backed by the P4 Plan GraphQL API rather than a local database. A projectId parameter is available for scoping requests to a project. The README identifies a search_tasks configuration option, with a default result limit of 400, so task search is part of the exposed tool surface.

How it works

The p4plan-mcp MCP server uses stdio transport. An MCP client starts it as a child process, sends protocol messages through standard input, and receives responses through standard output. It is therefore intended to be launched by a configured client, not used as an interactive command-line application.

The adapter is stateless: it does not maintain sessions between requests. For every tool call, it sends the configured JWT to the P4 Plan GraphQL API as a bearer token. The API must be reachable at a compatible P4 Plan installation; the documented minimum API version is 2026.1.002.

Setup and configuration

The p4plan-mcp MCP server can be started without a local package installation by configuring an MCP client to run npx -y @perforce/p4plan-mcp. The repository also documents building from source with npm ci and npm run build, or running the published Docker image. Node.js 20 or newer and npm 9 or newer are required for a local installation.

Set P4PLAN_API_AUTH_TOKEN to a JWT obtained from the P4 Plan GraphQL login mutation. The token can be based on a password or a personal access token. Set P4PLAN_API_URL to the API's base origin only; the server adds paths such as /graphql itself, so the value should not include a path or trailing slash.

Optional settings include LOG_LEVEL, SEARCH_LIMIT, and P4PLAN_ALLOW_SELF_SIGNED_CERTS. The latter enables connections to HTTPS APIs using self-signed or otherwise untrusted certificates. Docker configurations pass the same settings as environment variables and use host.docker.internal or 172.17.0.1 when the API runs on the host.

Tools and capabilities

The documented resource types are:

  • backlog_task
  • bug
  • scheduled_task
  • sprint
  • release
  • sprint_task

The server supports project-oriented task work, sprint and release data, bug records, comments, and custom fields through the P4 Plan API. Use the projectId parameter where a tool requires project scope. Search result volume can be controlled with SEARCH_LIMIT.

Limitations and notes

This server requires a running P4 Plan GraphQL API and a valid JWT. Because communication uses stdio, the MCP client must manage the process lifecycle.

The project is released under the MIT license and is marked as community supported. The README provides configurations for Claude Desktop and VS Code, but does not document client-specific setup for every MCP application. When using Docker, network addressing differs by operating system, so the API hostname must be adjusted accordingly.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about P4plan MCP

p4plan-mcp is an MCP server that connects AI clients to the P4 Plan GraphQL API. Its main tools work with backlog tasks, scheduled tasks, bugs, sprints, releases, sprint tasks, comments, and custom fields, using projectId for project scope and a JWT for authentication.

Run it through npx or Docker, or build it from the repository. The documented npx command is `npx -y @perforce/p4plan-mcp`; local builds use Node.js 20 or newer, `npm ci`, and `npm run build`.

Set `P4PLAN_API_AUTH_TOKEN` to a JWT from the P4 Plan GraphQL login mutation. Also set `P4PLAN_API_URL` to the API base origin without a path or trailing slash; the server forwards the token on each GraphQL request.

The README provides stdio configurations for Claude Desktop and VS Code, and the server is designed for MCP clients that can spawn a stdio child process.

Related MCP servers

All in Product Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewP4plan MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/p4plan-mcp?style=directory)](https://allmcps.com/mcp/p4plan-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/p4plan-mcp"><img src="https://allmcps.com/api/badge/p4plan-mcp?style=directory" alt="P4plan MCP on AllMCPs" /></a>