MCP server

ShipEasy ships an MCP (Model Context Protocol) server: @shipeasy/mcp. Plug it into your AI coding assistant and the agent gains a typed toolkit for inspecting and changing your ShipEasy project — plus prompts that walk it through complete onboarding flows.

The MCP server is the same surface as the CLI, exposed as JSON-Schema-typed tools instead of argv. That distinction matters: a typed tool is much harder for an LLM to misuse than a free-form CLI invocation.

Install

The CLI patches the right config file for whichever assistants you use:

After install, restart your assistant. The new MCP server appears under its tool list as shipeasy.

Manual config

If your client isn't auto-detected, or you prefer to write the config yourself:

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

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

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

For any other MCP-compatible client, write the same block to whatever config file it reads.

Why typed tools beat free-form

A CLI is great for a human — short flags, terse output, easy to chain. For an LLM, a CLI is a parsing hazard. The agent has to remember the flag spelling, escape JSON correctly, and interpret the textual response.

A typed MCP tool flips that. Each tool is a named function with a JSON-Schema parameter object. The agent sees the schema, fills it, and gets a structured response back. Misuse — wrong types, missing required fields, unsupported flags — is caught at the protocol layer, not by the CLI's argv parser.

That's why the MCP server is the recommended surface for any AI-driven setup. The CLI is for humans and CI.

Tool inventory

The MCP server exposes ~30 tools, grouped by area. The agent sees them as mcp__shipeasy__<name>.

Auth & project

Inspection

Flags & experiments

i18n (Polylang)

Onboarding prompts

The MCP server bundles long-form prompts you can invoke with /mcp:shipeasy:<prompt>:

Practical example

Open Claude Code in a fresh React project and say:

Use the ShipEasy MCP to onboard this project to translations. Use en as the source locale.

The agent will:

The whole flow takes a few minutes and the only thing you click is the browser confirmation during login. For the canonical step-by-step the agent follows, see LLM Guides → String Manager.

Auth model

The MCP server is launched as a subprocess of your AI assistant. It reads ~/.shipeasy/credentials on every tool call — the same file the CLI writes. There are three implications worth knowing:

1. One login covers everything. Run shipeasy login once on your machine, and every MCP tool in every assistant is authenticated.
2. Refresh happens transparently. If the access token has expired, the MCP server refreshes it before the tool call — same behaviour as the CLI.
3. Tokens never appear in MCP config. Your mcp.json only contains the launcher command. Stealing the config gives an attacker nothing.

Troubleshooting