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.
      7
      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
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 15 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action, with clear separation between query_ (read) and modify_ (write) operations. There is no overlap or ambiguity between tools.

    Naming Consistency5/5

    Tools follow a consistent 'verb_resource' pattern: 'query_' for reads and 'modify_' for writes, applied across all resource types. This pattern is predictable and intuitive.

    Tool Count5/5

    With 15 tools, the server is well-scoped for a version control system. Each tool covers a distinct operation area (streams, workspaces, files, changelists, shelves, jobs, reviews, server info), without excess or deficiency.

    Completeness4/5

    The tool set provides comprehensive CRUD-like operations for core Perforce resources. Minor gaps exist (e.g., no admin or label operations), but the essential workflows for typical usage are well-covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources