mcp_perforce_version
Show MCP Perforce server version
LABSCO SUMMARY
The path argument on every tool is the decision worth noticing.
Perforce operations are ambiguous without a workspace context, and here that context is a required argument rather than state the server carries between calls. One session can therefore touch two workspaces without switching, and no call silently inherits a directory something else set. The stream and client coverage goes further than a wrapper around the common commands — create, edit by specification, switch — which is what makes branch work possible from here rather than just file work. p4_raw_command labels itself as being for debugging, and treating it that way rather than as a general route is the right instinct.
What it is
A Perforce server covering file operations, changelists, streams and client workspaces, where the workspace context is an argument rather than hidden state.
What you get
- File operations: add, open for edit, mark for deletion, revert files or an entire changelist, sync from the depot with an optional force, and diff
- Changelists created with a description, files moved between them, and a changelist submitted
- p4_status for the workspace state and pending changes, and p4_info for the Perforce configuration in a directory
- Streams: listed or filtered by pattern, one stream's detail, the workspace switched to another stream, a new stream created with a parent and type, a stream specification edited, and the hierarchy shown as a graph
- Client workspaces: listed per user, one client's detail, created with a root, view and stream, edited by specification, deleted with an optional force, and switched to
- p4_raw_command, marked in its own description as being for debugging, returning stdout and stderr from an arbitrary p4 command
- mcp_perforce_version, reporting the server's own version
Requirements
A Perforce workspace and its configuration, with P4CONFIG naming the config file. Every tool takes a path, so the working directory each call applies to is explicit.
Setup effort
One command — npx -y @cocoon-ai/mcp-perforce
USE CASES
01
Getting a change ready to submit
See what is pending in the workspace, read the diffs, open a changelist with a description, move only the files that belong in it, and submit that changelist rather than everything currently open.
02
Moving your workspace onto another stream
List the streams in the depot or filter them by pattern, read the one you are heading for, switch the workspace across, and sync the files it brings with it.
03
Setting up a workspace on a new machine
Create the client with its root, view and stream, switch to it, confirm the connection the directory resolves to, and pull the files down.
04
Backing out work that went wrong
Check what is currently open, read the diff to be sure of what would be lost, then revert either the named files or the whole changelist.
25 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
p4_add
Add files to Perforce
p4_changelist_create
Create a new changelist with a description
p4_changelist_submit
Submit a changelist
p4_client_create
Create a new client/workspace
p4_client_delete
Delete a client/workspace
p4_client_edit
Edit an existing client/workspace specification
p4_client_info
Get detailed information about a specific client/workspace
p4_client_list
List all clients/workspaces for the current user
p4_client_switch
Switch to a different client/workspace
p4_delete
Mark files for deletion in Perforce
p4_diff
Show differences for files
p4_edit
Open files for edit in Perforce
p4_info
Show Perforce configuration info for current directory
p4_move_to_changelist
Move files to a specific changelist
p4_raw_command
FOR DEBUGGING: Executes a raw p4 command and returns stdout/stderr
p4_revert
Revert files or changelist
p4_status
Get current P4 workspace status and pending changes
p4_stream_create
Create a new stream
p4_stream_edit
Edit stream specification
p4_stream_graph
Show stream hierarchy graph
p4_stream_info
Get detailed information about a specific stream
p4_stream_list
List all streams or streams matching a pattern
p4_stream_switch
Switch workspace to a different stream
p4_sync
Sync files from the depot
BEFORE YOU INSTALL
What to know first
Tools you get
25 tools when we connected.
Requires
- npx on PATH
- Node.js 18+
- P4CONFIG in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 25 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"perforce": {
"command": "npx",
"args": [
"-y",
"@cocoon-ai/mcp-perforce"
],
"env": {
"P4CONFIG": ".p4config"
}
}
}
}npx
TERMINAL
npx -y @cocoon-ai/mcp-perforce
