Feature flags, A/B experiments, kill switches, dynamic config & i18n — Shipeasy MCP server.
Feature flags · kill switches · dynamic configs · A/B experiments · metrics · i18n — spun up from a single sentence to your AI coding agent.
Shipeasy is the AI-native experimentation platform. Feature flags, kill switches, dynamic configs, A/B tests, metrics and translations — all controllable from where you already work: a sentence to your AI coding agent.
"Ship the new pricing page behind a flag at 5%." "Add a kill switch for checkout in case it breaks." "Run an A/B test on the signup button and tell me which wins."
No dashboards to learn, no SDK boilerplate to hand-write. Shipeasy installs as a plugin into your coding agent and an MCP server, so Claude Code (and 70+ other agents) can create the flag, instrument the metric, wire the SDK call, and roll it out — end to end, from plain English.
This directory is the source-of-truth for that plugin marketplace.
One plugin tree, many hosts — the same shipeasy/skills/ directory and the
same shipeasy MCP server feed every coding agent below. Each host gets a tiny
manifest that points at the shared files; nothing is duplicated.
npm install -g @shipeasy/cli
shipeasy setup
That's it. shipeasy setup detects your coding agent, installs the right
integration for it (native plugin where one exists, shared skills + MCP
everywhere else), authenticates, binds the repo to a project, mints keys and
installs @shipeasy/sdk. One command, every host — then just talk to your agent.
There are two install tiers. Tier 1 hosts have a native plugin system, so
one command bundles skills + MCP. Tier 2 hosts (70+ agents) take the same
shared skills via the
vercel-labs/skills CLI plus a small
MCP config snippet. (shipeasy setup above does the right one for you.)
| Agent | Install |
|---|---|
| Claude Code | claude plugin marketplace add shipeasy-ai/shipeasy → claude plugin install shipeasy@shipeasy |
| Codex | codex plugin marketplace add shipeasy-ai/shipeasy → codex plugin add shipeasy@shipeasy (or, in the TUI, /plugin marketplace add shipeasy-ai/shipeasy → /plugin add shipeasy@shipeasy) |
| GitHub Copilot CLI | copilot plugin marketplace add shipeasy-ai/shipeasy → copilot plugin install shipeasy@shipeasy |
# 1. skills — installs all 17 shipeasy-* skills
npx skills add https://github.com/shipeasy-ai/shipeasy -a <agent>
# 2. MCP — add the shipeasy server to that agent's MCP config:
# { "mcpServers": { "shipeasy": { "command": "npx", "args": ["-y", "@shipeasy/mcp@latest"] } } }
<agent> is e.g. opencode, cursor, windsurf, cline, gemini-cli,
continue, github-copilot. The full per-host list, exact MCP file paths and
formats live in INSTALL.md (also published at
https://docs.shipeasy.ai/get-started/agents).
Installing the plugin registers the skills and MCP tools — it does not run any shell commands. To go live:
shipeasy setup (or say "set up shipeasy") — one command detects
your subprojects, installs @shipeasy/sdk,
authenticates, binds the repo to a project, mints keys, installs the SDK +
feature how-to skills into your agents, offers the modules + devtools overlay,
and emits shipeasy-wiring.md with the remaining code steps.shipeasy setup offers them, or enable one
directly with shipeasy install <group>:
shipeasy install flags — flags + configs + kill switches +
experiments + events (the whole decide-at-runtime platform, one pass).shipeasy install ops — feedback (bugs + feature requests) +
production errors + alerts.shipeasy install i18n — translations.The matching per-area how-to skills (shipeasy-flags, shipeasy-ops,
shipeasy-i18n) are installed alongside. After that, just talk to your agent.
You ▸ Ship a feature gate for the new pricing page, rolled out to 5% of users.
Agent ▸ Created gate `new_pricing_page` (rollout 5%). Add gates.check("new_pricing_page")
at apps/web/app/pricing/page.tsx:12 — done. Want me to bump it to 25%?
| Native plugin (Tier 1) | Claude Code · Codex · GitHub Copilot CLI |
| Skills + MCP (Tier 2) | Cursor · Windsurf · Cline · Gemini CLI · OpenCode · Continue · OpenClaw · 70+ more |
All 11 skills (9 area guides + 2 multi-step workflow skills) and the
shipeasy MCP server port to every agent — the flows trigger from
natural-language phrasing everywhere, and Claude Code additionally exposes each
skill as a /shipeasy:<skill-name> command. Skills and MCP are referenced,
never copied.
INSTALL.md — full per-agent install reference (70+ hosts).shipeasy ops trigger create <provider> --help
(also at https://docs.shipeasy.ai/get-started/triggers) — set up unattended
scheduled triggers that burn down your ops inbox and open one PR per item.Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @shipeasy/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"ai-shipeasy-mcp": {
"command": "npx",
"args": [
"-y",
"@shipeasy/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceai.shipeasy/mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.