A
licenseNot graded
qualityD
maintenanceProvides remote project access via MCP, enabling file operations, code search, git commands, and background Claude CLI execution.
6 npm
MIT
MCP Perforce Server
by Cocoon-AI
Related Servers
Alternatives to MCP Perforce Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityFmaintenanceProvides sophisticated context management for Claude, enabling persistent context across sessions, project-specific organization, and conversation continuity.415-
- AlicenseAqualityBmaintenanceBridges Claude AI with the local filesystem for direct file and project management, enabling incremental saves and automatic work logs to overcome token limits.222MIT
- AlicenseNot gradedqualityAmaintenanceProvides AI clients with safe, structured access to local filesystem, Git repositories, and project contexts, featuring file operations, git status/diff, project management, and built-in code review/bug analysis prompts.1,140 npmMIT
- FlicenseBqualityBmaintenanceWraps Maven and Spring Boot operations for Claude Code, providing structured JSON output instead of raw build logs to save tokens and focus on code fixes.20-
- AlicenseAqualityAmaintenanceEnables Claude Code to read, create, update, and delete Claude Cowork/claude.ai projects and their knowledge documents, including syncing local folders to projects, with safety features like backups and overwrite protection.17MIT
TDQS
B3.2/5.0
Scored across 25 tools
Disambiguation5/5
Each tool targets a distinct resource and action: file operations (add/edit/delete/revert/sync/diff) are clearly separate from changelist, client, and stream operations. Even similar-sounding tools like p4_info and p4_status have distinct purposes (config vs workspace status).
Naming Consistency4/5
The dominant pattern is p4_<resource>_<action> (e.g., p4_stream_list, p4_client_create) or p4_<verb> for file ops (p4_add, p4_edit). The only outlier is mcp_perforce_version, which uses a different prefix and breaks the p4_ convention.
Tool Count4/5
At 25 tools, the set is large but each tool serves a specific need for Perforce workflows. The count is at the boundary of 'heavy' but is justified by the breadth of Perforce features (files, changelists, clients, streams).
Completeness4/5
The core CRUD and lifecycle operations for files, changelists, clients, and streams are well covered. Minor gaps exist, such as no stream_delete or changelist_edit, but these can be worked around with p4_raw_command.
Maintenance
ActivityInactive
ResponsivenessNo issues