by steadybit
Enables LLM tools like Claude to interact with the Steadybit platform, providing programmatic access to experiment designs, executions, actions, environments, teams, schedules, and templates via a set of defined tools.
Enables LLM agents to query and manipulate Steadybit experiment data. It exposes a collection of tools—such as listing experiment designs, fetching executions, creating experiments from templates, and enumerating actions, environments, teams, and schedules—through the Model Context Protocol (MCP). This makes it possible for AI assistants to drive chaos engineering workflows without manual API calls.
Installation
docker build -t steadybit/mcp -f Dockerfile .
then run with docker run -i --rm -e API_TOKEN -e API_URL steadybit/mcp
.mvn clean install
) and execute the generated JAR (java -jar target/mcp-*.jar
).mvn -Pnative native:compile
and execute the produced binary.Configuration
API_TOKEN
(required) and optionally API_URL
(default https://platform.steadybit.com/api
).CAPABILITIES_ENABLED_0
, e.g. CREATE_EXPERIMENT_FROM_TEMPLATE
.Running with Claude Desktop Add a server entry in Claude’s developer settings, for example:
{
"mcpServers": {
"steadybit": {
"command": "docker",
"args": ["run","-i","--rm","-e","API_TOKEN","-e","API_URL","steadybit/mcp"],
"env": {"API_TOKEN": "<your-token>", "API_URL": "https://platform.steadybit.com/api"}
}
}
}
The MCP client will then communicate via STDIO with the server.
steadybit-mcp.log
.CAPABILITIES_ENABLED_0=CREATE_EXPERIMENT_FROM_TEMPLATE
before starting the server.pageSize
defaults to 50 and caps at 100.MCP Server for Steadybit, enabling LLM tools like Claude to interact with the Steadybit platform.
list-experiment-designs
team
(string): The team key to list experiment designs forget_experiment_design
experimentKey
(string): The experiment key to getlist_experiment_executions
experiment
(list of string): Filter by one or more experiment keysenvironment
(list of string): Filter by one or more environment namesteam
(list of string): Filter by one or more team keysstate
(list of string): Filter by one or more result states, possible values
are [CREATED, PREPARED, RUNNING, FAILED, CANCELED, COMPLETED, ERRORED]from
(string, ISO8601 date): Filter by creation date fromto
(string, ISO8601 date): Filter by creation date topage
(number): Number of the requested page, default is 0pageSize
(number): Results per page, defaults to 50, maximum 100 is allowedget_experiment_execution
executionId
(number): The execution id to getlist_actions
page
(number): Number of the requested page, default is 0pageSize
(number): Results per page, defaults to 50, maximum 100 is allowedlist_environments
list_teams
list_experiment_schedules
experiment
(list of string): Filter by one or more experiment keysteam
(list of string): Filter by one or more team keyslist_experiment_templates
get_experiment_template
templateId
(string): The id of the template to create an experiment fromcreate_experiment_from_template
CAPABILITIES_ENABLED_0=CREATE_EXPERIMENT_FROM_TEMPLATE
templateId
(string): The id of the template to create an experiment fromenvironment
(string): The environment to use for the experimentteam
(string): The team to use for the experimentplaceholders
(object): A map of placeholder keys and their values.externalId
(string): An optional external id that can be used to update existing experiment designs.You need to have a Steadybit account and an API token. You can create an API token in the Steadybit platform under
"Settings" → "API Access Tokens". Both token types, Admin
or Team
are supported.
If you want to create experiments, you need a team token for the team you want to create experiments in.
API_TOKEN
: The API token to use for authentication. This is required.API_URL
: The URL of the Steadybit API. Default is https://platform.steadybit.com/api
.CAPABILITIES_ENABLED_0
,CAPABILITIES_ENABLED_1
,...: A comma-separated list of additional capabilities to enable.
The capabilities are:
CREATE_EXPERIMENT_FROM_TEMPLATE
: Enables the create_experiment_from_template
tool.<your-api-token>
with your actual API token.:
{
"mcpServers": {
"steadybit": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"API_TOKEN",
"ghcr.io/steadybit/mcp:latest"
],
"env": {
"API_TOKEN": "<your-api-token>"
}
}
}
}
Please note that there will be no logging to the console when running the MCP Server. The server uses STDIO transport
to communicate with the MCP Clients. Have a look at the steadybit-mcp.log
file to see the output of the server.
Build the project:
mvn clean install
Test with the MCP inspector:
npx @modelcontextprotocol/inspector java -jar target/mcp-1.0.0-SNAPSHOT.jara -e API_URL=https://platform.steadybit.com/api -e API_TOKEN=123456
steadybit-mcp.log
located in the folder where you started the inspector.Use in Claude Desktop
{
"mcpServers": {
"steadybit": {
"command": "/Users/danielreuter/.sdkman/candidates/java/current/bin/java",
"args": [
"-jar",
"/Users/danielreuter/.m2/repository/com/steadybit/mcp/1.0.0-SNAPSHOT/mcp-1.0.0-SNAPSHOT.jar"
],
"env": {
"API_URL": "https://platform.steadybit.com/api",
"API_TOKEN": "123456",
"LOGGING_FILE_NAME": "/Users/danielreuter/Library/Logs/Claude/steadybit-mcp-server.log"
}
}
}
}
~/Library/Logs/Claude/mcp-server-steadybit.log
~/Library/Logs/Claude/steadybit-mcp.log
, depending on the LOGGING_FILE_NAME
you set in the env
section.Build the image:
docker build -t steadybit/mcp -f Dockerfile .
Create a file config.json
with the following content:
{
"mcpServers": {
"steadybit": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"API_TOKEN",
"-e",
"API_URL",
"steadybit/mcp"
],
"env": {
"API_TOKEN": "123456",
"API_URL":"https://platform.steadybit.com/api"
}
}
}
}
Run the inspector:
npx @modelcontextprotocol/inspector --config config.json --server steadybit
Install GraalVM 24.0.1 with the following command using sdkman:
sdk install java 24.0.1-graalce
Use the GraalVM version:
sdk use java 24.0.1-graalce
Build the native image:
mvn -Pnative native:compile
You can find some example prompts here.
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Please log in to share your review and rating for this MCP.
Discover more MCP servers with similar functionality and use cases
by Skyvern-AI
Skyvern automates browser-based workflows using LLMs and computer vision, offering a robust solution for repetitive online tasks.
by PipedreamHQ
Connect APIs quickly, run event‑driven automations, and execute custom code in Node.js, Python, Go, or Bash on a hosted platform.
by czlonkowski
Provides AI assistants with structured access to n8n node documentation, properties, and operations, enabling automated workflow creation, validation, and management.
by executeautomation
mcp-playwright is a Model Context Protocol (MCP) server that enables large language models (LLMs) to perform browser automation and web scraping tasks using Playwright.
by browserbase
Provides cloud browser automation capabilities for LLMs, enabling web navigation, interaction, screenshot capture, and data extraction through Browserbase and Stagehand.
by haris-musa
excel-mcp-server is a Python-based Model Context Protocol (MCP) server that enables AI agents to programmatically create, read, and modify Excel files without requiring Microsoft Excel to be installed.
by mobile-next
Mobile-mcp is a Model Context Protocol (MCP) server designed for scalable mobile automation, app scraping, and development across iOS and Android devices, including physical devices, simulators, and emulators.
by anaisbetts
mcp-installer is an MCP server designed to automate the installation of other MCP servers, simplifying the process for users.
by leonardsellem
An MCP server that enables AI assistants to interact with n8n workflows through natural language.