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, the server will use the configuration from the specified P4CONFIG file instead of setting any of the P4 environment variables | |
| P4PASSWD | No | Your P4 password or ticket for authentication (ticket-based or password login) | |
| P4DAM_API_KEY | No | API key for P4 DAM access | |
| P4MCP_LOG_DIR | No | Directory for log files. Default: logs/ in the server executable's directory. Can be overridden by the --log-dir CLI argument. | logs/ |
| P4MCP_CA_BUNDLE | No | Path to a custom CA bundle. Only honored when P4MCP_TLS_CA_MODE=certifi (in 'system' mode truststore overrides the verify parameter and this is ignored). | |
| P4MCP_MAX_RESULTS | No | Cap on the number of rows the P4 server returns per command (p4.maxresults). Set to 0 to disable the limit. Must be a non-negative integer. Can be overridden by the --max-results CLI argument. | 10000 |
| P4MCP_TLS_CA_MODE | No | TLS certificate source mode. 'system' (default) uses the OS trust store via truststore; in this mode truststore overrides the verify parameter, so custom CA bundles set via P4MCP_CA_BUNDLE or --ca-bundle are ignored. 'certifi' disables truststore so that a custom CA bundle can be used. | system |
| P4MCP_MAX_SCAN_ROWS | No | Cap on the number of rows the P4 server scans per command (p4.maxscanrows). Unset by default. Must be a non-negative integer when supplied. Can be overridden by the --max-scan-rows CLI argument. |
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