A Model Context Protocol (MCP) server that provides a clean interface for Perforce (P4) operations in Claude Desktop. This server wraps P4 commands
Connect MCP Perforce to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server that provides a clean interface for Perforce (P4) operations in Claude Desktop. This server wraps P4 commands to make them more reliable and easier for Claude to use, eliminating issues with. The mcp perforce mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Prerequisites — The Prerequisites tool exposed by this serverConfiguration is passed through the environment: P4CONFIG, DEBUG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
.p4config files in your project directories (recommended)Installation goes through your MCP client rather than a global install: point it at @cocoon-ai/mcp-perforce on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Perforce's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by Cocoon-AI; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Perforce's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"perforce": {
"command": "npx",
"args": ["-y", "@cocoon-ai/mcp-perforce"],
"env": {
"P4CONFIG": ".p4config"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
.p4config files in your project directories (recommended)| Variable | Description | Required |
|---|---|---|
| P4CONFIG | Configuration value read at startup. | Optional |
| DEBUG | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.