Skip to main content
Glama
iPraBhu

mcp-perforce-server

by iPraBhu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-perforce-server

No user-submitted related servers found.

    Related Servers

    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

    C2.7/5.0

    Scored across 59 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources