Perforce P4 MCP Server

Name: Perforce P4 MCP Server
Author: perforce

by perforceversion 2026.4.3126709i★ –iRuns on your computer

Registry nameio.github.perforce/p4mcp-server

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: P4PORT, P4USER, P4CLIENT, P4PASSWD, P4DAM_API_KEY

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "p4mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "P4PORT",
        "-e",
        "P4USER",
        "-e",
        "P4CLIENT",
        "-e",
        "P4PASSWD",
        "-e",
        "P4DAM_API_KEY",
        "ghcr.io/perforce/p4mcp-server:2026.4.3126709"
      ],
      "env": {
        "P4PORT": "your-value",
        "P4USER": "your-value",
        "P4CLIENT": "your-value",
        "P4PASSWD": "your-value",
        "P4DAM_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add p4mcp --env P4PORT=your-value --env P4USER=your-value --env P4CLIENT=your-value --env P4PASSWD=your-value --env P4DAM_API_KEY=your-value -- docker run -i --rm -e P4PORT -e P4USER -e P4CLIENT -e P4PASSWD -e P4DAM_API_KEY ghcr.io/perforce/p4mcp-server:2026.4.3126709

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "p4mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "P4PORT",
        "-e",
        "P4USER",
        "-e",
        "P4CLIENT",
        "-e",
        "P4PASSWD",
        "-e",
        "P4DAM_API_KEY",
        "ghcr.io/perforce/p4mcp-server:2026.4.3126709"
      ],
      "env": {
        "P4PORT": "your-value",
        "P4USER": "your-value",
        "P4CLIENT": "your-value",
        "P4PASSWD": "your-value",
        "P4DAM_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "p4mcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "P4PORT",
        "-e",
        "P4USER",
        "-e",
        "P4CLIENT",
        "-e",
        "P4PASSWD",
        "-e",
        "P4DAM_API_KEY",
        "ghcr.io/perforce/p4mcp-server:2026.4.3126709"
      ],
      "env": {
        "P4PORT": "your-value",
        "P4USER": "your-value",
        "P4CLIENT": "your-value",
        "P4PASSWD": "your-value",
        "P4DAM_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account perforce, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32464 servers in this category
Published to the registry more recently than 89% of the other 32464 servers in this category
Basic checks equal to or better than 100% of the other 32464 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Perforce P4 MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2026.4.3126709) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, yontu

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

yontu

by senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Perforce P4 MCP Server

Perforce P4 MCP Server is a Model Context Protocol (MCP) server that integrates with the Perforce P4 version control system. It is built on FastMCP with direct P4 Python bindings to expose safe, structured read/write tools for changelists, files, shelves, workspaces, jobs, reviews, and server metadata. It also integrates with P4 DAM through its REST API to manage resources .

Features · Prerequisites · System Requirements · Install · Deployment · Client Configurations · P4 Configurations · Tools

Logging · Troubleshoot · Support · Contributions · License

Features

Comprehensive P4 integration: Read/write tools across files, changelists, shelves, workspaces, jobs, reviews, streams, and server information.
Code review workflows: P4 Code Review support for review discovery, voting, state transitions, commenting, and participant management.
P4 DAM integration: Access P4 DAM assets and metadata through MCP-compatible AI assistants. Search for assets, retrieve metadata, manage reviews, create asset bundles, update asset tags, and browse projects. To learn more, see Configure P4 DAM access for P4 MCP Server in the P4 DAM documentation.
Safety first: Read-only mode by default, ownership checks, interactive MCP elicitation (PROCEED/CANCEL) for destructive delete and obliterate operations.
Flexible toolsets: Configure which tool categories to enable: server, files, changelists, shelves, workspaces, jobs, reviews, streams, and p4dam.
Robust logging: Application and session logging to the logs/ directory.
Optional telemetry: Consent-gated usage statistics. Disabled by default.
Cross platform: Supported on macOS, Linux and Windows with pre-built binaries.

Prerequisites

P4 Server access: Connection to a P4 Server with proper credentials
Authentication: Valid P4 login (ticket-based or password)

System Requirements

Component	Supported Versions

Local P4 MCP Server Installation

uvx (easiest, no install required)

If you have uv installed, you can run P4 MCP Server directly without any manual installation:

# Run the server

uvx p4mcp-server

Check version

uvx p4mcp-server --version

Run with arguments

uvx p4mcp-server --readonly --allow-usage

This automatically fetches and runs the latest version from PyPI. No Python virtual environment setup or dependency management needed.

Requirements:

uv installed on your system
Python 3.11+ (uv will handle this automatically)

Pre-built binaries (recommended for offline/air-gapped)

Download the appropriate binary for your operating system:

Extract and use the executable directly. No Python installation is required.

# macOS / Linux

unzip p4-mcp-server-mac.zip # or p4-mcp-server-linux.zip ./p4-mcp-server --help

# Windows

Expand-Archive p4-mcp-server-win.zip -DestinationPath . .\p4-mcp-server.exe --help

Build from source

Requirements:

Python 3.11+ (with Tkinter)

Build:

macOS: chmod +x build.sh && ./build.sh package
Linux: chmod +x build.sh && ./build.sh package
Windows: build.bat package

Output:

macOS & Linux: p4-mcp-server-<version>.tgz
Windows: p4-mcp-server-<version>.zip

Deployment

STDIO-based deployment

Local

Run the P4 MCP Server directly on your machine using the default STDIO transport.

Add the following to your mcp.json:

"mcpServers": { "perforce-p4-mcp": { "command": "/absolute/path/to/p4-mcp-server", "env": { "P4PORT": "ssl:perforce.example.com:1666", "P4USER": "your_username", "P4CLIENT": "your_workspace", "P4DAM_API_KEY": "your_api_key" }, "args": [ "--readonly", "--allow-usage" ] } } }

Note: This example shows explicit env values. If P4CONFIG is set, you can omit them and use the generic configuration example in the MCP client configuration section instead.

Docker

Run the P4 MCP Server from a Docker container with STDIO transport, allowing MCP clients to manage the container lifecycle.

Note: Docker-based execution is currently supported on macOS and Linux only.

Prerequisites

Docker installed and running
Valid P4 credentials and access to a P4 server

Pull the Docker image

docker pull ghcr.io/perforce/p4mcp-server:latest

Build from source instead

cd /path/to/p4mcp-server

docker build -t ghcr.io/perforce/p4mcp-server .

Configure MCP Client

Add the following to your mcp.json:

"servers": { "perforce-p4mcp-docker": { "command": "docker", "args": [ "run", "-i", "--rm", "--hostname", "your-hostname", "-e", "P4PORT=ssl:perforce.example.com:1666", "-e", "P4USER=your_username", "-e", "P4CLIENT=your_workspace", "-e", "P4DAM_API_KEY=your_api_key", "-v", "/Users/your_username/.p4tickets:/home/mcpuser/.p4tickets:ro", "ghcr.io/perforce/p4mcp-server:latest" ] } } }

Configuration Options

Flag	Description
`-i`	Interactive mode (required for STDIO)
`--rm`	Remove container when stopped
`--hostname`	Match workspace host restriction
`-e P4PORT`	P4 server address
`-e P4USER`	P4 username
`-e P4CLIENT`	Workspace name
`-v`	Mount P4 tickets file

Authentication

Using P4 tickets:

# macOS/Linux

-v /Users/your_username/.p4tickets:/home/mcpuser/.p4tickets:ro

Note: Use the full path to your tickets file (not ~). After running p4 login, restart the MCP server to pick up the new ticket.

Note: By default the container starts as root, copies the bind-mounted tickets file to a location readable by the non-root mcpuser, then drops privileges (via gosu) so the server runs as mcpuser. This auto-copy lets an owner-only (0600) tickets file owned by a foreign uid work on runtimes that preserve host ownership (native Linux Docker/podman). A :ro bind mount of the ticket is supported — the file is copied, not modified in place (this is distinct from a read-only container root filesystem; see below). Note the auto-copy runs only when the container starts as root (the default); forcing a non-root uid or a read-only root filesystem changes this behavior, as described below.

Kubernetes / restricted (non-root-enforced) profiles: the image intentionally starts as root and drops to mcpuser (uid 1000) via gosu, so the server always runs non-root — both paths are supported. For runAsNonRoot / restricted PodSecurity / OpenShift restricted SCC, set securityContext.runAsUser: 1000 (and fsGroup: 1000 when mounting the ticket). In that mode the entrypoint's root-only ticket copy is skipped, so the mounted ticket must already be readable by uid 1000 (owner-matched mount, -e P4PASSWD="your_ticket_content", or podman -v :/home/mcpuser/.p4tickets:U).

Read-only root filesystem (`--read-only` / `readOnlyRootFilesystem`): provide a writable/tmpfs /home/mcpuser (e.g. --tmpfs /home/mcpuser) so the ticket copy can be written; otherwise the ticket copy fails and P4 will report a normal auth error.

Using a password:

-e P4PASSWD="your_password"

Workspace Host Restrictions

⚠️ Important: Docker containers have their own hostname, which differs from your local machine. If your P4 workspace is restricted to a specific host, operations like sync will fail.

To resolve this, set the container hostname to match your workspace's host restriction:

--hostname your-hostname

To find your workspace host name:

# macOS/Linux

p4 client -o your_workspace | grep "^Host:"

Mounting Client Root for Write Operations

⚠️ Important: By default, the Docker container cannot access your local workspace files. For write operations like sync, submit, or reconcile, you must mount your client root directory into the container at the same path.

Add a volume mount for your client root:

-v /path/to/your/client/root:/path/to/your/client/root

Example configuration with client root mounted:

"servers": { "perforce-p4mcp-docker": { "command": "docker", "args": [ "run", "-i", "--rm", "--hostname", "your-hostname", "-e", "P4PORT=ssl:perforce.example.com:1666", "-e", "P4USER=your_username", "-e", "P4CLIENT=your_workspace", "-e", "P4DAM_API_KEY=your_api_key", "-v", "/Users/your_username/.p4tickets:/home/mcpuser/.p4tickets", "-v", "/path/to/client/root:/path/to/client/root", "ghcr.io/perforce/p4mcp-server:latest" ] } } }

To find your client root:

p4 client -o your_workspace | grep "^Root:"

Note: The mount path inside the container must match the client root path exactly, as P4 tracks files by their absolute paths.

HTTP-based deployment

Security: HTTP binds to 127.0.0.1 (local only) by default. Use --host 0.0.0.0 for remote clients. HTTP has no authentication, so expose it only on trusted networks.

Run the MCP server on a VM using the HTTP transport, allowing clients to connect over the network.

Start the server on the VM:

P4PORT=ssl:perforce.example.com:1666 P4USER=your_username P4PASSWD=YOUR_TICKET ./p4-mcp-server --readonly --transport http --host 0.0.0.0 --port 8000

Configure the MCP client:

Add the following to your mcp.json:

"servers": { "perforce-p4-mcp": { "type": "http",

Only the beginning is shown; read the rest in the repo

Perforce P4 MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

yontu

README from the maker

Features

Prerequisites

System Requirements

Local P4 MCP Server Installation

Check version

Run with arguments

Deployment

STDIO-based deployment

HTTP-based deployment