mcp-perforce

Perforce MCP Server

Perforce file changes, changelists, streams, and workspaces can be managed through Claude with mcp-perforce. It serves developers using P4 who want assistant-driven version control with project-specific configuration and structured command responses.

Server facts

mcp-perforce

Project

Author
Cocoon-AI
License
MIT

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
29
Last commit
Data as of

Overview

Perforce workflows in Claude extend from checking pending work to submitting changelists with mcp-perforce. Developers can inspect workspace status and file differences, open files for editing, add or mark files for deletion, synchronize depot content, and revert changes. Changelist tools let Claude create a described change, move files into it, and submit it. The integration wraps P4 operations to avoid interactive prompts and returns structured results rather than unprocessed command output, with error messages for failed operations.

Stream and workspace management sit alongside those file workflows. Tools can inspect streams, display their hierarchy, create or modify stream specifications, and switch the workspace between streams. Client tools cover listing, inspection, creation, specification changes, deletion, and switching. Project settings come from Perforce’s P4CONFIG mechanism, using .p4config files according to the working directory. Configuration inspection and version reporting support troubleshooting, while a separate raw-command debugging tool returns stdout and stderr. The Node.js server communicates over stdio and is documented for Claude Desktop and Claude Code.

mcp-perforce setup notes

  • mcp-perforce records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers