Give your AI agent real browsers
Supervisor Autotune is an MCP server. Connect your agent and it can run load tests, monitors and accessibility checks on your website, then show whether each change it made helped.
Three steps, and you get 5 free credits when you register, enough for a load test with 50 users. Don't want to use an agent? Use the web app instead.
Connect your agent
Claude, ChatGPT and Claude Code connect by signing in. Other MCP clients use an access token.
Add Supervisor as a connector
Paste the address into your agent's connector settings.
Sign in and choose your organization
You can disconnect an agent at any time in the app.
Verify your domain
With a DNS TXT record or a file on the site. Load tests send real traffic, so we need to know the site is yours.
Connector address
https://api.supervisor.com/mcpClaude Code
claude mcp add --transport http supervisor https://api.supervisor.com/mcpOther MCP clients, for example Cursor, Codex and Replit Agent, can use an organization access token with the scope autotune, created on the Agents page in the app.
One change at a time, measured
Supervisor measures. Your agent, which already has your logs and configuration, does the fixing. Autotune was built first for shops and apps that have never been load tested.
Run a baseline
An automatic test starts with 4 users and adds more every 10 seconds, until the target holds or the average page load passes 3 seconds.
Your agent reads its own logs
Supervisor never touches your server. The agent looks for the cause where it already has access.
Make exactly one change
You approve it, and the agent records it with the run using
report_change.Run again and compare
The answer is one number: how many users the site handled, before and after the change.
Keep or revert, then repeat
Keep the change if it helped and revert it if it did not. Repeat until the site handles the load you need.
What a session looks like
An example with the fictional shop acme-shop.example. The tool names are calls your agent makes. The cards are what Supervisor sends back.
- You
How many users can acme-shop.example handle?
- Agent called
start_load_testReal browsers ramp up to 100 users Passed: 98 of 100 users handled
Average page load 0.54 s. 95% of pages within 1.33 s.
AverageSlowest pageLimitUsers handled
- Agent
The target was reached, but static files stall under load. I can put a CDN in front of them. Shall I change that one thing and run again?
- You
Yes.
- Agent called
report_changeCDN in front of static files - Agent called
compare_runsSecond run against the first Passed: Improved
Both runs reached the target; page loads faster.
What your agent can ask for
Autotune gives your agent these tools, in six groups. Tools that start or stop load are marked so the agent asks you first.
Sites
list_sitesyour sites and what they run onverify_sitecheck the DNS record or file
Load tests
start_load_teststart an automatic testget_run_statushow far a run has gotget_run_resultusers handled, load times, slowest pagesstop_load_teststop a runreport_changerecord the one change made before the next runcompare_runssay whether the change helpedget_slow_requestsslowest requests seen by the browsersget_site_historypast runs and the trendcontrol_load_testadd users, pause and resume a controlled runinspect_userswhat each browser is doing, with screenshots
Schedules
schedule_load_testset up a scheduled load testlist_schedulessee the scheduled testsupdate_schedulechange an existing scheduled testdelete_scheduleremove one of the scheduled tests
Monitors
create_monitorset up a new monitorlist_monitorssee the monitors you haveget_monitorresults, charts and historyupdate_monitorchange the settings of a monitordelete_monitorremove a monitor you no longer need
Journeys
create_journeya Playwright script with named stepsupdate_journeychange the script of an existing journeyget_journeyread one journey and its stepslist_journeyssee the journeys you have saveddelete_journeyremove a journey you no longer usedry_run_journeyone browser, free, returns each step's result and a screenshotset_test_accountslogins for the test users, stored encryptedlist_test_accountssee which test accounts are storeddelete_test_accountsremove the stored test accounts
Accessibility
start_accessibility_start an automated accessibility checkcheck get_accessibility_read the result of a checkcheck list_accessibility_see the issues found so farissues update_accessibility_change a tracked accessibility issueissue add_accessibility_record a manual findingissue get_accessibility_read the current accessibility statementstatement publish_accessibility_only if the owner has allowed agents to publishversion set_accessibility_set the accessibility policy in usepolicy schedule_accessibility_set up a scheduled accessibility checkcheck
Automated checks find only part of the problems.
What keeps it safe
Load tests send real traffic to a live site. These rules apply to every connected agent.
- The domain must be verified first, with a DNS TXT record or a file on the site.
- Credits are checked before a run starts.
- Only one automatic run per site at a time.
- Tools that start or stop load are marked so the agent asks you first.
- Test traffic carries an
X-Supervisor-Runheader. - Google Analytics is blocked in the test browsers by default.
- Supervisor never touches your server. Your agent makes the changes, with your approval.
- You can disconnect a connected agent at any time in the app.
See what your site handles before you connect anything
Three steps, and you get 5 free credits when you register, enough for a load test with 50 users. Don't want to use an agent? Use the web app instead.