Steadybit

Design, run and analyse Steadybit chaos experiments from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Steadybit connector does

The Steadybit MCP server connects Claude to your Steadybit tenant for chaos engineering. Its 31 tools explore your environments, services and targets, draft and save experiments, and start or cancel runs. A run injects real faults into your infrastructure. Every tool acts as you, limited to your team permissions, environment allowances and Steadybit license.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Steadybit tools (31)

  • analyze_execution
  • cancel_execution
  • create_experiment
  • create_experiment_from_template
  • draft_experiment
  • get_action
  • get_execution
  • get_execution_artifact
  • get_execution_log
  • get_execution_metric
  • get_execution_report
  • get_experiment
  • get_reliability_advice
  • get_service
  • get_service_risk_report
  • get_target
  • get_target_stats
  • get_template
  • list_environments
  • list_execution_metrics
  • list_metric_label_values
  • list_teams
  • list_templates
  • run_experiment
  • search_actions
  • search_executions
  • search_experiments
  • search_services
  • search_targets
  • suggest_experiments
  • update_experiment

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Licensed feature. No MCP access unless your tenant's license includes it; AI tools need the AI feature as well.
  • The directory URL is tenant-specific. If demo is not your tenant, use the plain endpoint or your own tenant address as a custom connector.
  • Organisation-wide Claude connectors need an internet-reachable platform. A platform reachable only inside your network works with Claude Code but not as an organisation-wide connector.
  • Okta self-hosting needs extra setup. Steadybit says Okta cannot register MCP clients automatically, so each client needs a pre-registered app's client ID.
  • We did not read the tools. Our anonymous request returned a 401 with an OAuth challenge, so schemas and annotations are not on this page. The setup tool Steadybit describes for multi-tenant users is not in the directory's list.
  • No rate limits are documented on Steadybit's MCP page.

Frequently asked questions

Why does the Steadybit connector reject my requests?

Usually because MCP is not enabled for your tenant. Steadybit documents the MCP server as a licensed feature and says that if the endpoints reject your requests, your Steadybit administrator should confirm MCP is enabled and that the license includes it. The AI-assisted tools, which draft experiments, suggest them and analyse runs, also need the separate Steadybit AI feature.

Why does the connector only show a setup tool?

Because you belong to more than one Steadybit tenant and connected to the plain endpoint. With OAuth, Steadybit says the plain /mcp address cannot tell which tenant you mean, so it offers only a setup tool that lists your tenant keys. Connect to the tenant-specific address instead, and add it as a custom connector in Claude, since the directory connector's URL cannot be changed.

Can I use the Steadybit connector without a Steadybit account?

Yes, through a trial. Steadybit says you can choose Sign up on the sign-in page, confirm your email or use a social login, and, if your account has no tenant, start a free 30-day trial with sample data to explore. Choosing Cancel instead stops the flow, and the client reports that access was denied. Existing users connect with their current membership.

Which MCP clients can sign in to Steadybit with OAuth?

Claude Code, Claude Desktop and web, and VS Code including GitHub Copilot. Steadybit has registered those with its identity provider. Clients that need Dynamic Client Registration, such as Cursor, Windsurf, the Codex CLI and the GitHub Copilot CLI, are not supported on the OAuth path today. Steadybit's advice is to create an API access token and send it as a Bearer header instead.

Sources

Use it in an agent

Put Steadybit to work.

Connect Steadybit once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.