Skip to content

Connect AI tools (MCP setup)

MaxoPerf runs a Model Context Protocol (MCP) server. Through it, AI agents create tests, launch runs, and read results for you. They take the same actions you take in the console, driven by natural language.

Get started with the MaxoPerf MCP server.

You need a MaxoPerf API key. Read Get an API key first. It explains 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
Settings → Connect AI tools shows the endpoint URL and a pre-filled config snippet for each supported client.

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 snippet for your client from the console page. It already contains your account’s MCP endpoint, so you only swap in the API key.

Once connected, the agent calls MaxoPerf’s MCP tools to create tests, start runs, poll status, and read KPIs/results. It can do anything the API key is authorized to do. The key grants full-account access, so review your tool’s call log before you approve 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, …) and when it runs a full browser test (Playwright, Selenium). That choice changes what the agent should generate.