Shipeasy MCP server
{
"mcpServers": {
"shipeasy-mcp": {
"command": "npx",
"args": [
"-y",
"@shipeasy/mcp@latest"
]
}
}
}{
"mcpServers": {
"shipeasy-mcp": {
"command": "npx",
"args": [
"-y",
"@shipeasy/mcp@latest"
]
}
}
}{
"mcpServers": {
"shipeasy-mcp": {
"command": "npx",
"args": [
"-y",
"@shipeasy/mcp@latest"
]
}
}
}{
"servers": {
"shipeasy-mcp": {
"command": "npx",
"args": [
"-y",
"@shipeasy/mcp@latest"
]
}
}
}{
"mcpServers": {
"shipeasy-mcp": {
"command": "npx",
"args": [
"-y",
"@shipeasy/mcp@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @shipeasy/mcpversion 2.8.0
What it does
The Shipeasy MCP server exposes tools for managing feature flags, kill switches, dynamic configs, A/B experiments, event metrics, and i18n translations through AI coding agents. It is intended for developers who want to create and control release infrastructure by describing their intent in natural language to an agent rather than using a dashboard.
- Create a feature flag with a percentage rollout and have the agent instrument the SDK call in the codebase.
- Set up an A/B experiment on a UI element and track which variant wins based on configured metrics.
- Add a kill switch for a critical code path so it can be disabled instantly without a deployment.
Tools this server exposes
| Tool | Does |
|---|---|
| shipeasy | Provides access to Shipeasy platform operations including flag creation, experiment management, dynamic config, kill switches, metrics, and i18n through a set o |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.