P4plan MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add p4plan-mcp -e 'P4PLAN_API_AUTH_TOKEN=<P4PLAN_API_AUTH_TOKEN>' -- npx -y @perforce/p4plan-mcp

{
  "mcpServers": {
    "p4plan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@perforce/p4plan-mcp"
      ],
      "env": {
        "P4PLAN_API_AUTH_TOKEN": "<P4PLAN_API_AUTH_TOKEN>"
      }
    }
  }
}

[mcp_servers.p4plan-mcp]
command = "npx"
args = ["-y", "@perforce/p4plan-mcp"]
env = { P4PLAN_API_AUTH_TOKEN = "<P4PLAN_API_AUTH_TOKEN>" }

{
  "mcpServers": {
    "p4plan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@perforce/p4plan-mcp"
      ],
      "env": {
        "P4PLAN_API_AUTH_TOKEN": "<P4PLAN_API_AUTH_TOKEN>"
      }
    }
  }
}

{
  "servers": {
    "p4plan-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@perforce/p4plan-mcp"
      ],
      "env": {
        "P4PLAN_API_AUTH_TOKEN": "<P4PLAN_API_AUTH_TOKEN>"
      }
    }
  }
}

Put your own value in place of <P4PLAN_API_AUTH_TOKEN> (JWT bearer token for the P4 Plan GraphQL API. Forwarded as Authorization on every tool call). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: 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), P4PLAN_READONLY (Set to 'true' to expose only the tools that read (same as the --readonly argument). Default: false), P4PLAN_UPLOAD_DIRS (Folders upload_attachment may read files from, besides the workspace folders the MCP client shares. Separate several with ':' (';' on Windows)).