Shipeasy is answering right now. Last checked 3 min ago. 784 installs a week from npm. Last commit 1 Nov 2026.
Feature flags, A/B experiments, kill switches, dynamic config & i18n — Shipeasy MCP server.
We read the source, 1 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(cmd!, args, { stdio: "ignore", detached: true });
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
1. Delete the artifacts: \`rm -rf ${rm.join(" ")}\`
console.log(`CLI: ${opts.skipCli ? "skipped" : `update via ${resolvePm(opts)}`}`);
for f in "$NPM_CONFIG_USERCONFIG" "$HOME/.npmrc"; do
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
claude mcp add mcp --transport http https://mcp.shipeasy.ai/mcp
https://mcp.shipeasy.ai/mcp
[mcp_servers.mcp]
url = "https://mcp.shipeasy.ai/mcp"
{
"mcpServers": {
"mcp": {
"url": "https://mcp.shipeasy.ai/mcp"
}
}
}
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.shipeasy.ai/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.shipeasy.ai/mcp | streamable-http | sign-in | 383 ms | 3 min ago |
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
MCP server for Statsig API - interact with Statsig's feature flags, experiments, and analytics
Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
Feature flags and kill switches. Turn a shipped feature off in production without a deploy.
MCP server for managing Unleash feature flags
Connect AI agents to CloudBees Unify: feature flags, CI/CD, release orchestration, and security
DevCycle MCP server for feature flag management
Enables AI agents to interact with ConfigCat, a feature flag service for teams.
Answers built from our own checks of this server.