Schema | Perforce P4 MCP Server

Perforce P4 MCP Server

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 uses the configuration from this file instead of the individual P4 environment variables.
`P4PASSWD`	No	Your P4 password or ticket. Alternative to mounting a P4 tickets file.
`P4DAM_API_KEY`	No	API key for P4 DAM integration. Required for P4 DAM features.
`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 file for TLS. Only 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. Must be a non-negative integer.	10000
`P4MCP_TLS_CA_MODE`	No	TLS certificate source mode. 'system' (default) uses the OS trust store; 'certifi' enables custom CA bundles via P4MCP_CA_BUNDLE.	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.

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.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityMaintained

ResponsivenessNo issues