Perforce P4 MCP Server
by adamtyurin
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, individual P4 environment variables are not required. | |
| P4PASSWD | No | P4 password or ticket content for authentication (alternative to mounting a tickets file). | |
| P4DAM_API_KEY | No | API key for P4 DAM integration. | |
| P4MCP_LOG_DIR | No | Directory for log files. Default: logs/ in the server executable's directory. | |
| P4MCP_CA_BUNDLE | No | Path to a custom CA bundle. Used when P4MCP_TLS_CA_MODE=certifi. | |
| 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. | |
| P4MCP_TLS_CA_MODE | No | TLS certificate source mode. 'system' (default) uses OS trust store; 'certifi' enables custom CA bundle support. | |
| P4MCP_MAX_SCAN_ROWS | No | Cap on the number of rows the P4 server scans per command (p4.maxscanrows). Unset by default. |
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