perforce-agentic-gateway 2026.3

Local MCP gateway that proxies AI clients to many MCP servers with a token-efficient code mode

Perforce Agentic Gateway (PAG)

PAG is a local MCP gateway with a token-efficient code mode. You configure your AI client once to connect to PAG, and manage every other MCP server through PAG: it runs the server processes, restarts them when they crash, and keeps their credentials in your OS keychain.

Perforce products ship as first-party servers, and PAG proxies any MCP server — add third-party servers from a registry or by manual configuration.

Install

PAG runs via uv; there is no separate install step. Point your AI client at it — for example, Claude Code:

claude mcp add pag -- uvx perforce-agentic-gateway@latest

Any client that uses .mcp.json (Cursor, and others):

{
  "mcpServers": {
    "pag": {
      "command": "uvx",
      "args": ["perforce-agentic-gateway@latest"]
    }
  }
}

Browse the catalog and manage servers in the dashboard with uvx perforce-agentic-gateway@latest view.

Why it stays fast

Rather than forwarding every downstream tool to your client (20 servers can mean a thousand tools), PAG exposes a small, fixed pag__* toolset and keeps the full catalog inside the gateway. Your assistant searches it with pag__explore and runs multi-step workflows — loops, fan-out across servers — through pag__execute in one round trip instead of many.

Documentation

• Connecting AI clients
• Using PAG
• Configuration
• Secrets
• Troubleshooting

License

Use of PAG is governed by the Perforce Agentic Gateway Terms of Use.