mcp-perforce-server
Related Servers
Alternatives to mcp-perforce-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceExposes safe, structured read/write tools over MCP for Perforce P4 version control and P4 DAM resources, covering changelists, files, shelves, workspaces, jobs, reviews, streams, and server metadata with read-only mode by default.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to interact with Perforce P4 version control and P4 DAM, with safe read/write tools for files, changelists, shelves, workspaces, jobs, reviews, streams, and server metadata. Supports code review workflows, configurable toolsets, and read-only safety by default.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to perform safe, structured read/write operations against Perforce P4 version control, covering files, changelists, shelves, workspaces, jobs, code reviews, streams, and server metadata, plus P4 DAM asset and metadata management through its REST API. It runs read-only by default, with ownership checks and interactive confirmation for destructive delete and obliterate operations.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to read and modify version control data — files, changelists, shelves, workspaces, jobs, reviews, streams, and server metadata — through safe, structured tools that are read-only by default, along with DAM asset search, metadata, tagging, and bundle management via its REST API.-
- FlicenseNot gradedqualityAmaintenanceIntegrates with Perforce P4 version control and P4 DAM to expose safe, structured read/write tools for changelists, files, shelves, workspaces, jobs, reviews, streams, server metadata, and DAM assets. This enables MCP-compatible AI assistants to manage version-control and DAM workflows.-
- FlicenseNot gradedqualityAmaintenanceIntegrates with Perforce P4 version control to expose safe, structured read/write tools for changelists, files, shelves, workspaces, jobs, reviews, and server metadata, with optional P4 DAM asset management.-
TDQS
Scored across 59 tools
Several tools have ambiguous boundaries: p4_annotate is an alias of p4_blame, p4_submit and p4_changelist_submit overlap, and p4_review/p4_reviews/p4_review_prepare/p4_review_bundle are easy to mix up. The singular/plural pairs and composite inspect helpers also require careful reading to select correctly.
The p4_ prefix creates an apparent uniform convention, but the suffixes mix raw verbs, plural nouns, reversed noun_verb forms like changelist_create, and composite names like workspace_snapshot. There is no single predictable pattern beyond the prefix.
At 59 tools, the server exposes a very large surface for an MCP agent. While Perforce is complex, many calls could be consolidated or omitted without hurting typical workflows, making the count clearly exceed a manageable scope.
Core Perforce workflows are thoroughly covered: file lifecycle, changelists, sync, shelving, resolving, integrating, labeling, streaming, job tracking, and review tooling. Minor gaps like branch-spec management and some administrative commands keep this from being perfect.