Skip to main content
Glama
perforce

Perforce P4 MCP Server

Official
by perforce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Perforce P4 MCP Server

No user-submitted related servers found.

    Related Servers

    • dpr-mcp

      Charan-Sharan
      A
      license
      B
      quality
      C
      maintenance
      Provides a Model Context Protocol interface for secure, multi-agent collaboration on Git repositories, offering isolated workspaces, change requests, reviews, and approval workflows with Git as the source of truth.
      32
      MIT

    • AMEVA MCP Toolkit

      uno-km
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server integrating developer tools including Git control, document conversion, remote SSH execution, database operations, and utilities for automation and development productivity.
      1
      -

    • Conduit

      cortex-app
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that integrates with Phabricator and Phorge APIs, enabling developers to automate and interact with task management systems through both synchronous and asynchronous clients.
      9
      MIT

    • Endevor-MCP

      gglessner
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server providing 43 tools for Broadcom Endevor SCM interaction, enabling inventory browsing, element lifecycle management, and package workflows. It is designed for AI-driven mainframe operations and surgical, source-informed penetration testing of CICS applications.
      1
      GPL 3.0

    • MCP Jenkins Server

      WinJayX
      F
      license
      Not graded
      quality
      D
      maintenance
      An integration tool that allows interaction with Jenkins CI/CD servers through a Model Context Protocol interface, enabling users to view server info, manage jobs, inspect builds, and trigger builds with parameters.
      1
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 15 tools

    Disambiguation5/5

    The query_/modify_ split cleanly separates read from write, and each tool targets a distinct Perforce resource (files, changelists, workspaces, shelves, jobs, reviews, streams, server). Although individual tools bundle many sub-operations, the resource boundaries are unambiguous.

    Naming Consistency5/5

    Every tool follows a strict verb_noun convention with only two verbs (query_ for reads, modify_ for writes) across all 15 tools. The pattern is fully predictable and self-documenting.

    Tool Count5/5

    15 tools for a full Perforce client covering 8 resource domains is well-scoped. Each resource earns its place with a paired read/write tool, none feels redundant.

    Completeness4/5

    The surface gives read/write coverage across files, changelists, workspaces, shelves, jobs, reviews, streams, and server info, covering most core workflows. Admin-oriented areas like depots, labels, users/groups, and triggers are absent, but typical developer operations are fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources