Shipeasy MCP Server

What the code does

We read the source, 23 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

      1. Delete the artifacts: \`rm -rf ${rm.join(" ")}\`

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 });

  console.log(`CLI:     ${opts.skipCli ? "skipped" : `update via ${resolvePm(opts)}`}`);

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.

          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.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

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

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

[mcp_servers.mcp]
command = "npx"
args = ["-y", "@shipeasy/mcp"]

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

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