P4 Plan MCP Server
Rank #15,099io.github.perforce/p4plan-mcp
MCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API.
What you can do with P4 Plan MCP Server
P4 Plan MCP Server is a Model Context Protocol (MCP) server published by perforce. It ranks #15,099 of 144,396 active servers on MCP Toplist, and its repository has 4 GitHub stars. P4 Plan MCP Server is listed across 3 registries — Official MCP, Glama and PulseMCP, with 2 tracked versions. It was first listed on Mar 27, 2026 and most recently updated on Sep 24, 2026.
Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. The repository README is the authority on what it does.
What P4 Plan MCP Server can and cannot do
Not verifiedMCP Toplist has not catalogued this server's tools or limitations. The repository README lists them.
What you need before using P4 Plan MCP Server
The registry listing declares required configuration before first use — typically an API key, token or connection string set via environment variables.
Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.
- P4PLAN_API_AUTH_TOKEN · required
- P4PLAN_API_URL · optional
- P4PLAN_ALLOW_SELF_SIGNED_CERTS · optional
Connect P4 Plan MCP Server and confirm it works
claude mcp add p4plan-mcp -e "P4PLAN_API_AUTH_TOKEN=<your P4PLAN_API_AUTH_TOKEN>" -e "P4PLAN_API_URL=<your P4PLAN_API_URL>" -e "P4PLAN_ALLOW_SELF_SIGNED_CERTS=<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>" -- npx -y @perforce/p4plan-mcpReplace each placeholder with your own value before saving.
claude mcp add p4plan-mcp -e "P4PLAN_API_AUTH_TOKEN=<your P4PLAN_API_AUTH_TOKEN>" -e "P4PLAN_API_URL=<your P4PLAN_API_URL>" -e "P4PLAN_ALLOW_SELF_SIGNED_CERTS=<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>" -- docker run -i --rm docker.io/perforce/p4plan-mcp:2026.3.1Replace each placeholder with your own value before saving.
[mcp_servers.p4plan-mcp]
command = "npx"
args = ["-y", "@perforce/p4plan-mcp"]
[mcp_servers.p4plan-mcp.env]
P4PLAN_API_AUTH_TOKEN = "<your P4PLAN_API_AUTH_TOKEN>"
P4PLAN_API_URL = "<your P4PLAN_API_URL>"
P4PLAN_ALLOW_SELF_SIGNED_CERTS = "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.
[mcp_servers.p4plan-mcp]
command = "docker"
args = ["run", "-i", "--rm", "docker.io/perforce/p4plan-mcp:2026.3.1"]
[mcp_servers.p4plan-mcp.env]
P4PLAN_API_AUTH_TOKEN = "<your P4PLAN_API_AUTH_TOKEN>"
P4PLAN_API_URL = "<your P4PLAN_API_URL>"
P4PLAN_ALLOW_SELF_SIGNED_CERTS = "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"p4plan-mcp": {
"command": "npx",
"args": [
"-y",
"@perforce/p4plan-mcp"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.
{
"mcpServers": {
"p4plan-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/perforce/p4plan-mcp:2026.3.1"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.
{
"mcpServers": {
"p4plan-mcp": {
"command": "npx",
"args": [
"-y",
"@perforce/p4plan-mcp"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.
{
"mcpServers": {
"p4plan-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/perforce/p4plan-mcp:2026.3.1"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.
{
"servers": {
"p4plan-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@perforce/p4plan-mcp"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.
{
"servers": {
"p4plan-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/perforce/p4plan-mcp:2026.3.1"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"p4plan-mcp": {
"command": "npx",
"args": [
"-y",
"@perforce/p4plan-mcp"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"p4plan-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/perforce/p4plan-mcp:2026.3.1"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"p4plan-mcp": {
"command": "npx",
"args": [
"-y",
"@perforce/p4plan-mcp"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Replace each placeholder with your own value before saving.
{
"mcpServers": {
"p4plan-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/perforce/p4plan-mcp:2026.3.1"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "<your P4PLAN_API_AUTH_TOKEN>",
"P4PLAN_API_URL": "<your P4PLAN_API_URL>",
"P4PLAN_ALLOW_SELF_SIGNED_CERTS": "<your P4PLAN_ALLOW_SELF_SIGNED_CERTS>"
}
}
}
}Replace each placeholder with your own value before saving.
After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.
When to choose another server
No task-specific alternatives are catalogued for P4 Plan MCP Serveryet; the list above is its publisher's other servers.
What changed, and when this was checked
- First listed
- Mar 27, 2026
- Latest version published
- Sep 24, 2026
- Version history
- 2 versions tracked (below)
- Requirements evidence
- Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.
- Profile checked
- Not yet — purpose, capabilities and requirements above come from registry data only
- Ranking data as of
- Oct 16, 2026
- Glama ↗listed since Jun 3, 2026 · still listed
- PulseMCP ↗listed since Jun 4, 2026 · still listed
- Official MCP ↗listed since Jul 24, 2026 · still listed
Do you maintain P4 Plan MCP Server? to correct or enrich this profile.
Available versions (2)
| Version | Published |
|---|---|
| 2026.3.1 | Sep 24, 2026 |
| 2026.2.1 | May 18, 2026 |
Ranks ahead of 129,297 of 144,396 servers on MCP Toplist.
Show your rank
Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.
[](https://mcptoplist.com/server/io.github.perforce%2Fp4plan-mcp)<a href="https://mcptoplist.com/server/io.github.perforce%2Fp4plan-mcp"><img src="https://mcptoplist.com/badge/io.github.perforce%2Fp4plan-mcp.svg" alt="MCP Toplist: Top 25% of 144,396" /></a>Variants: append ?metric=score or ?metric=stars to the image URL.
Frequently asked questions
- Who maintains P4 Plan MCP Server?
- P4 Plan MCP Server is maintained by perforce, which publishes 3 MCP servers (11 total versions) tracked on MCP Toplist.
- Is P4 Plan MCP Server listed on the Official MCP Registry?
- Yes — P4 Plan MCP Server is listed on the Official MCP Registry, alongside Glama and PulseMCP.
- How many versions does P4 Plan MCP Server have?
- MCP Toplist tracks 2 versions of P4 Plan MCP Server, most recently published on Sep 24, 2026.
- Where can I find the source code for P4 Plan MCP Server?
- The source code for P4 Plan MCP Server is hosted at github.com/perforce/p4plan-mcp.git.
Do you run this server?
Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.