MCP Tools DirectoryAbout this integration
MCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 2026.2.1
- Package
- @perforce/p4plan-mcp
- Last compatibility test
- Not independently tested
Connect your agent
@perforce/p4plan-mcpPublisher documentation reviewed offline; the package and P4 Plan endpoint were not executed. The bearer credential is an expiring P4 Plan JWT obtained through an API login, which does not fit the native authentication taxonomy. A reachable compatible P4 Plan API is required.
Capabilities: Project and task queries, Task and sprint management, Comments and attachments, Workflow and custom-field operations
Connected profiles
Additional details
io.github.perforce/p4plan-mcp
Source ↗ · Checked 2026-09-172026.2.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17P4PLAN_API_AUTH_TOKEN
Source ↗ · Checked 2026-09-17@perforce/p4plan-mcp
Source ↗ · Checked 2026-09-192026.2.1
Source ↗ · Checked 2026-09-19The publisher documents a stateless child process spawned by the MCP client and operated over stdio.
Source ↗ · Checked 2026-09-19Requires an expiring P4 Plan JWT in P4PLAN_API_AUTH_TOKEN, obtained through the P4 Plan login API using a password or personal access token.
Source ↗ · Checked 2026-09-19Configure the client to spawn npx -y @perforce/p4plan-mcp over stdio; P4PLAN_API_URL selects the GraphQL service.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19