Publisher · GitHub account
MCP servers published by perforce
3 servers in the official MCP Registry are published under the namespace io.github.perforce/ and have a page in this directory: all run locally from a package. First published 2026-09-21; latest update 2026-09-25.
What this publisher publishes
Names under io.github.perforce/ can only be published by someone who signs in to the MCP Registry as the GitHub user perforce, or as a member of the GitHub organisation of that name. The name shows which GitHub account published the entry; it does not show that the account belongs to the company whose product a server works with.
- Namespace
io.github.perforce- Servers with a page
- 3
- Categories
- developer (2), productivity (1)
- Transports
- stdio (local process) (3)
- Package registries
- OCI image (Docker) (2), npm (1), PyPI (1)
- Packages declaring environment variables
- 2 of 3
- First published
- 2026-09-21
- Latest update
- 2026-09-25
Source repositories
The 3 repositories these servers state, with how many servers name each.
All 3 servers, A to Z
| Server | Runs |
|---|---|
| P4plan MCPMCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API. | Local · stdio |
| Perforce Agentic GatewayLocal MCP gateway that proxies AI clients to many MCP servers with a token-efficient code mode. | Local · stdio |
| Perforce P4 MCP ServerPerforce P4 MCP server for version control and P4 DAM digital asset management. | Local · stdio |
Grouped by registry namespace, as the MCP Registry states it. A page here is not an endorsement and nobody pays to be listed: editorial policy · Before you connect a server