LanderPilot MCP

Universal npm package for connecting agents to the live LanderPilot MCP at:

https://landerpilot.com/api/mcp

The package exposes a local stdio bridge, so agents that support stdio MCP can use the same cloud LanderPilot tools after the user enters a LanderPilot API Key.

One-Command Agent Setup

After publishing to npm:

npx -y landerpilot-mcp --client cursor
npx -y landerpilot-mcp --client codewhale

Or install once, then configure any supported agent:

npm install -g landerpilot-mcp
landerpilot-mcp-setup --client cursor

The setup command prompts for the LanderPilot API Key with hidden input, then writes the selected agent's MCP config. It stores the key in that local MCP config as LANDERPILOT_API_KEY.

Supported --client values:

| Client | Default write target | | --- | --- | | generic | project .mcp.json | | trae | project .trae/mcp.json plus Trae global config | | cursor | ~/.cursor/mcp.json | | claude-code | project .mcp.json | | claude-desktop | Claude Desktop global claude_desktop_config.json | | vscode | project .vscode/mcp.json | | codex | project .codex/config.toml marker block | | codewhale | ~/.codewhale/mcp.json | | opencode | ~/.config/opencode/opencode.json |

Examples:

landerpilot-mcp-setup --client trae
landerpilot-mcp-setup --client cursor --scope project
landerpilot-mcp-setup --client claude-code --project /path/to/project
landerpilot-mcp-setup --client claude-desktop
landerpilot-mcp-setup --client codex --scope global
landerpilot-mcp-setup --client codewhale
landerpilot-mcp-setup --client opencode
landerpilot-mcp-setup --config /path/to/mcp.json

Verify config:

landerpilot-mcp-doctor --client cursor
landerpilot-mcp-doctor --client codewhale

One-shot doctor with npx uses the package name plus the bin name:

npx -y -p landerpilot-mcp landerpilot-mcp-doctor --client codewhale

Then restart the target agent/IDE and ask it to call:

landerpilot_connection_status

Backward-Compatible Trae Commands

The old Trae-specific commands still work:

landerpilot-trae-setup
landerpilot-trae-doctor

They now call the same universal setup/doctor logic with Trae defaults.

Install From GitHub Before npm Publish

If the npm package is not published yet, install from the existing GitHub repo:

npm install -g github:yuanyuanyuan430/landerpilot-trae-mcp
landerpilot-mcp-setup --client cursor

For private GitHub distribution, the user must already have access to the repo.

Manual MCP Config

For any agent that accepts a standard mcpServers JSON file:

{
  "mcpServers": {
    "landerpilot": {
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/landerpilot-mcp/cloud-proxy.mjs"],
      "env": {
        "LANDERPILOT_API_KEY": "paste your LanderPilot API Key",
        "LANDERPILOT_MCP_URL": "https://landerpilot.com/api/mcp"
      }
    }
  }
}

The setup helper generates absolute Node and script paths because many MCP clients do not launch servers through the user's interactive shell.

Local Helper MCP

This package also includes a local helper MCP server:

landerpilot-local-mcp

Local tools:

• list_sites
• inspect_site
• list_template_slots
• prepare_deployment_handoff
• get_cloud_mcp_connection

These local tools do not deploy anything. They inspect/generate local deployment handoff data by wrapping skills/landerpilot/scripts/local-tools.mjs.

Development Verification

npm install
npm run pack:check
npm run verify:distribution
npm run publish:check

verify:distribution packs the npm tarball, installs it into a temporary prefix, smoke-tests both MCP servers, and checks generated configs for generic, Cursor, CodeWhale, OpenCode, Codex, macOS Trae, and Windows Trae targets.

publish:check verifies the official npm registry target, package-name availability, login state, and npm publish --dry-run. If it reports loggedIn: false, run:

npm adduser --registry https://registry.npmjs.org

Then publish:

npm run publish:npm

Source Note

This package was extracted from ganhuo-ai/plugins/builtin/landerpilot. ganhuo-plugin.json is the original Ganhuo plugin manifest for the live cloud MCP.