Shipeasy MCP

Name: Shipeasy MCP
Author: shipeasy-ai

by shipeasy-aiversion 2.16.0i★ –iComputer or cloud

Registry nameai.shipeasy/mcp

Install

Overview

Description from the maker (original English)

Feature flags, A/B experiments, kill switches, dynamic config & i18n — Shipeasy MCP server.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.shipeasy.ai/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "shipeasy": {
      "command": "npx",
      "args": [
        "-y",
        "@shipeasy/mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add --transport http shipeasy https://mcp.shipeasy.ai/mcp

Or run it on your computer

claude mcp add shipeasy -- npx -y @shipeasy/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "shipeasy": {
      "url": "https://mcp.shipeasy.ai/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "shipeasy": {
      "command": "npx",
      "args": [
        "-y",
        "@shipeasy/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "shipeasy": {
      "type": "http",
      "url": "https://mcp.shipeasy.ai/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "shipeasy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@shipeasy/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.shipeasy.ai/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain shipeasy.ai (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 1374 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32568 servers in this category
Published to the registry more recently than 94% of the other 32568 servers in this category
Basic checks equal to or better than 100% of the other 32568 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Shipeasy MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.16.0) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

FlyDocs

by flydocs.ai

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Feature flags · kill switches · dynamic configs · A/B experiments · metrics · i18n — spun up from a single sentence to your AI coding agent.

Get started → · Website · Docs · Command reference

What is Shipeasy?

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.

Why teams use it

🚀 From one sentence to shipped. Describe what you want; the agent creates the gate/config/experiment, instruments the event, and edits the call site.
🎛️ The whole release toolkit. Feature flags, kill switches, dynamic configs, A/B experiments, event metrics and i18n — one SDK, one key per entrypoint, one install.
📊 Statistics that won't lie to you. Sequential testing, SRM detection, auto-ramp guardrails and holdouts come built in — no stats degree required.
⚡ Edge-fast, globally. Built on Cloudflare Workers + KV with infinite-TTL CDN caching and explicit purge — flag reads never touch a database on the hot path.
🤖 Works with your agent, not against it. Native plugins for Claude Code, Codex and Copilot CLI; shared skills + MCP for everything else.
🛟 Closes the loop. An operational inbox turns bug reports, feature requests, production errors and metric alerts into one queue your agent can burn down — even on a schedule, unattended.

Install in 12 seconds

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.

Prefer to wire the agent integration yourself? Per-host install commands

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.)

Tier 1 — one-command plugin install

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`

Tier 2 — skills + MCP (Cursor, Windsurf, Cline, Gemini, OpenCode, Continue, …)

# 1. skills — installs all 17 shipeasy-* skills

npx skills add https://github.com/shipeasy-ai/shipeasy -a

2. MCP — add the shipeasy server to that agent's MCP config:

{ "mcpServers": { "shipeasy": { "command": "npx", "args": ["-y", "@shipeasy/mcp@latest"] } } }

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`](./INSTALL.md) (also published at https://docs.shipeasy.ai/get-started/agents).

Then: "set up shipeasy"

Installing the plugin registers the skills and MCP tools — it does not run any shell commands. To go live:

Run `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.
Turn on the modules you want — shipeasy setup offers them, or enable one directly with shipeasy install :

`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%?

Works with your agent


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: command. Skills and MCP are *referenced, never copied*.

Learn more

📖 [Skill reference](./docs/reference.md) — every skill, its auto-triggers, MCP tool and CLI mapping, plus the headline workflows.
🧩 [`INSTALL.md`](./INSTALL.md) — full per-agent install reference (70+ hosts).
⏰ Trigger install guide — shipeasy ops trigger create --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.
🌐 [shipeasy.ai](https://shipeasy.ai) · [docs.shipeasy.ai](https://docs.shipeasy.ai)

Built on Cloudflare Workers · shipeasy.ai · Free to start.

Shipeasy MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

FlyDocs

README from the maker

What is Shipeasy?

Why teams use it

Install in 12 seconds

Tier 1 — one-command plugin install

Tier 2 — skills + MCP (Cursor, Windsurf, Cline, Gemini, OpenCode, Continue, …)

2. MCP — add the shipeasy server to that agent's MCP config:

{ "mcpServers": { "shipeasy": { "command": "npx", "args": ["-y", "@shipeasy/mcp@latest"] } } }

Then: "set up shipeasy"

Works with your agent

Learn more