Perforce P4 MCP Server

Perforce P4 MCP server for version control and P4 DAM digital asset management.

Local serverstdio

What is the Perforce P4 MCP Server?

Perforce P4 MCP Server is an MCP integration. Perforce P4 MCP server for version control and P4 DAM digital asset management.

Packages and local setup

The published oci package is ghcr.io/perforce/p4mcp-server:2026.4.3078076. Its declared MCP transport is stdio.

The package declares P4PORT: Perforce server address (e.g. ssl:perforce.example.com:1666); P4USER: Perforce username; P4CLIENT: Perforce workspace/client name; P4PASSWD: Perforce password or ticket; P4DAM_API_KEY: P4 DAM API key (account_key). When unset, P4 DAM tools are not registered..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 2026.4.3078076 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
P4PORTPerforce server address (e.g. ssl:perforce.example.com:1666)Optional
P4USERPerforce usernameOptional
P4CLIENTPerforce workspace/client nameOptional
P4PASSWDPerforce password or ticketOptional
P4DAM_API_KEYP4 DAM API key (account_key). When unset, P4 DAM tools are not registered.Optional