Perforce P4 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| P4PORT | No | P4 Server address. Examples: ssl:perforce.example.com:1666, localhost:1666 | |
| P4USER | No | Your P4 username | |
| P4CLIENT | No | Your current P4 workspace. Optional, but recommended | |
| P4CONFIG | No | Path to a P4CONFIG file. If set, you do not need to set any environment variables in the env block; the server will use the configuration from the specified P4CONFIG file instead. | |
| P4PASSWD | No | Your P4 password or ticket content, used for password-based authentication (alternative to mounting a P4 tickets file). | |
| P4DAM_API_KEY | No | API key for the P4 DAM integration, used to access P4 DAM assets and metadata. | |
| P4MCP_LOG_DIR | No | Directory for log files. Default: logs/ in the server executable's directory. | logs/ |
| P4MCP_CA_BUNDLE | No | Path to a custom CA bundle. Ignored when P4MCP_TLS_CA_MODE is system; set P4MCP_TLS_CA_MODE=certifi to use a custom CA bundle. | |
| P4MCP_MAX_RESULTS | No | Cap on the number of rows the P4 server returns per command (p4.maxresults). Default: 10000. Set to 0 to disable the limit (server default in effect). When a command would exceed this limit the server aborts it with an error rather than truncating results, so keep the value generous. Must be a non-negative integer; an invalid value fails fast at startup before any P4 connection is attempted. | 10000 |
| P4MCP_TLS_CA_MODE | No | TLS certificate source mode. system (default): use OS trust store via truststore. Note: in this mode truststore overrides the verify= parameter, so custom CA bundles set via P4MCP_CA_BUNDLE are ignored. certifi: disable truststore and use certifi. | system |
| P4MCP_MAX_SCAN_ROWS | No | Cap on the number of rows the P4 server scans per command (p4.maxscanrows). Unset by default, so admin/group policy governs scan limits. Must be a non-negative integer when supplied. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessNo issues