Skip to content

Connect AI tools (MCP setup)

MaxoPerf runs a Model Context Protocol (MCP) server so AI agents can create tests, launch runs, and read results on your behalf — the same actions you’d take in the console, but driven by natural language.

You need a MaxoPerf API key. See Get an API key — read that page first, it covers the full-account access an API key grants and how to use it safely.

Open Settings → Connect AI tools (/settings/connect-ai-tools) in the console. The page shows your account’s MCP endpoint URL and ready-to-copy config snippets for each supported client. Your MCP endpoint URL is:

https://app.maxoperf.com/mcp

If the page shows “MCP endpoint not configured for this environment,” ask an administrator to configure the MCP server origin for your deployment.

  1. Claude Code — run from your terminal:

    Terminal window
    claude mcp add --transport http maxoperf https://app.maxoperf.com/mcp \
    --header "Authorization: Bearer mpak_your_api_key_here"
  2. Cursor — add to .cursor/mcp.json (project or global):

    {
    "mcpServers": {
    "maxoperf": {
    "url": "https://app.maxoperf.com/mcp",
    "headers": {
    "Authorization": "Bearer mpak_your_api_key_here"
    }
    }
    }
    }
  3. Claude Desktop / claude.ai — go to Settings → Connectors → Add custom connector, paste the endpoint URL, then paste the API key when prompted.

  4. ChatGPT — go to Settings → Connectors → Create, paste the endpoint URL, and set the Authorization header to Bearer mpak_your_api_key_here.

Copy the exact snippet for your client from the console page — it’s pre-filled with your account’s real MCP endpoint, so you only need to swap in the API key.

Once connected, the agent can call MaxoPerf’s MCP tools to create tests, start runs, poll status, and read KPIs/results — anything the API key is authorized to do. Because the key grants full-account access, review your tool’s call log before approving destructive actions (delete run, cancel test, revoke key).

Before you point an agent at a real workload, skim Choosing an executor — it explains when MaxoPerf runs an API-style load test (JMeter, k6, Taurus, …) versus a full browser test (Playwright, Selenium), which changes what the agent should generate.