Content
<img src="assets/logo.svg" alt="Perforce Autonomous Testing" width="480" />
# PAT — MCP Setup
Perforce Autonomous Testing (PAT) exposes an MCP (Model Context Protocol) endpoint so AI coding assistants can interact with your test scenarios, suites, environments, and analytics directly from the IDE.
> **Your MCP endpoint URL** follows the pattern `https://<customer-cloud>.autonomous-testing.perforce.com/mcp`.
> Each customer may have one or more clouds; `<customer-cloud>` identifies which one this MCP endpoint connects to. Find it in your browser's address bar when logged in to PAT.
---
## Authentication
Authentication uses an API token via `Authorization: Bearer <token>`:
| Method | Token format | How to obtain |
|--------|-------------|---------------|
| API token | `syg_…` | Generate in PAT UI → **Settings → API Tokens** |
---
## Adding to Claude Code
```bash
claude mcp add --transport http pat https://<customer-cloud>.autonomous-testing.perforce.com/mcp \
--header "Authorization: Bearer syg_<your-token>"
```
To verify it connected:
```bash
claude mcp list
```
To remove:
```bash
claude mcp remove pat
```
---
## Adding to VS Code (Copilot / Continue / Open Code)
**`.vscode/mcp.json`**:
```json
{
"servers": {
"pat": {
"type": "http",
"url": "https://<customer-cloud>.autonomous-testing.perforce.com/mcp",
"headers": {
"Authorization": "Bearer syg_<your-token>"
}
}
}
}
```
**`settings.json`**:
```json
{
"mcp.servers": {
"pat": {
"type": "http",
"url": "https://<customer-cloud>.autonomous-testing.perforce.com/mcp",
"headers": {
"Authorization": "Bearer syg_<your-token>"
}
}
}
}
```
---
## Adding to Cursor
Add to `~/.cursor/mcp.json` (or Cursor's MCP settings UI):
```json
{
"mcpServers": {
"pat": {
"type": "http",
"url": "https://<customer-cloud>.autonomous-testing.perforce.com/mcp",
"headers": {
"Authorization": "Bearer syg_<your-token>"
}
}
}
}
```
---
## What PAT can do
Once connected, your assistant has access to six specialist agents and three direct tools:
| Specialist | What you can ask it |
|------------|-------------------|
| `setup` | Onboard to PAT, switch applications, browse settings |
| `environment` | Create and manage test environments and devices |
| `test_design` | Create scenarios, suites, manage suite composition |
| `policy` | Define and manage test policies and rules |
| `execution` | Run suites, dry-run scenarios, manage schedules |
| `analytics` | View dashboards, browse run history, analyze failures |
Direct tools: `mcp_usage_guide` (self-documenting reference), `get_binary_upload_url` and `list_binary_artifacts` (mobile binary management for Perfecto).
Call `mcp_usage_guide` with no parameters at any time for a full in-session reference.
---
## First steps
After connecting, start here:
> "What applications and test suites do I have in PAT?"
PAT will browse your applications and recent suite runs and return a summary of your workspace. From there, use the `setup` specialist with intent `switch_context` to set your active application before creating or running tests.
---
## License
Use of this software is subject to the [Perforce Autonomous Testing Terms of Use](LICENSE.md).
