InnerVault

p4plan-mcp

Stale Official MCP Registry, io.github.perforce

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

Open the source (opens github.com) https://github.com/perforce/p4plan-mcp

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: P4PLAN_API_AUTH_TOKEN. Use a key with the least access you can.

What it is

MCP servers from io.github.perforce.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

npm package (stdio)

@perforce/p4plan-mcp@2026.3.2

From the server's entry in the official MCP Registry

oci package (stdio)

docker.io/perforce/p4plan-mcp:2026.3.2

From the server's entry in the official MCP Registry

Settings it asks for

  • P4PLAN_API_AUTH_TOKEN secret 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.
  • 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).
  • P4PLAN_API_AUTH_TOKEN secret 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.
  • 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).

Related

  1. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  2. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  3. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  4. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  5. Anthropic's guide to adding MCP servers to Claude Code, with examples of local and remote servers.

    Hand-checked InnerVault (hand-checked), Anthropic Anthropic documentation

  6. Playwright MCP

    MCP servers

    Lets an agent drive a real browser: open pages, click, fill in forms and read what's on screen.

    Hand-checked InnerVault (hand-checked), Microsoft Apache-2.0

    claude mcp add playwright npx @playwright/mcp@latest