Each tool carries the READ permission marker and dispatches on an action, so who changed this file and what the review said is two calls rather than a p4 session plus a browser. The stream tools reach past file history into parent and child graphs, integration status and interchanges — the answers that decide whether a merge is safe to start.
Eight read-only query tools over a Perforce server, each dispatching on an action parameter: server, workspaces, files, changelists, shelves, jobs, reviews and streams.
- File work: content, history, info, a diff between two revisions, annotations, search by name and grep by content
- Changelists listed and read in detail, filtered by user, workspace, depot path or status
- Shelved work listed, with its diff and its file list
- Workspaces listed and checked for type and status, plus server and current-user information
- Jobs read from a changelist or fetched by job ID
- Reviews listed and read, filtered by state, project, keywords, version range and up-voters, with transitions included on request
- Streams queried for spec, parent, children and graph, integration status, interchanges, resolve state and file validation
A Perforce server and workspace you can reach — P4PORT, P4USER and P4CLIENT — plus uv on your PATH, which resolves the Python runtime through UV_PYTHON. Every tool is marked READ permission.
One command plus a key — uvx p4mcp-server --readonly --allow-usage, then supply credentials