Skip to main content

Standalone MCP Server (any MCP client)

The DeployGate Agent Plugin ships its tools as a Model Context Protocol (MCP) server. Beyond the Claude Code and Codex plugins, the same server is published to npm as @deploygate/mcp and can be added to any MCP-compatible client via npx — no global install or build step required.

Use this when your client is not Claude Code or Codex — for example Claude Desktop, Cursor, Cline, or VS Code (GitHub Copilot) — or whenever you prefer to wire up the MCP server manually.

note

The standalone server exposes the same MCP tools as the plugin (upload, distribution pages, members, and so on), but not the deploygate:* slash commands (/deploygate:setup, /deploygate:deploy, …). Those guided flows are a Claude Code / Codex plugin feature. If you want the slash commands, install the plugin instead — see Getting Started.

Prerequisites​

  • An MCP-compatible client (Claude Desktop, Cursor, Cline, VS Code with GitHub Copilot, and others)
  • Node.js 20 or newer on your PATH — npx ships with Node.js and runs the server. (The Claude Code / Codex plugin installs do not need this; the standalone npx flow does.)
  • A DeployGate account is not required up front — you can sign up during the in-browser login.

Configuration​

Most MCP clients share the same mcpServers configuration shape. Add the following entry to your client's MCP settings:

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

-y lets npx download and run the latest published @deploygate/mcp without an interactive prompt. The first launch fetches the package (a few seconds); subsequent launches reuse the npm cache.

After saving the configuration, restart (or reload) your client so it spawns the server. The DeployGate tools then appear in your client's tool list.

Where the configuration lives​

The exact location of the mcpServers block depends on your client. A few common ones:

ClientWhere to add it
Claude DesktopSettings → Developer → Edit Config (claude_desktop_config.json)
Cursor~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project)
ClineThe MCP Servers panel → Configure MCP Servers
VS Code (GitHub Copilot).vscode/mcp.json in your workspace, or the user settings.json

Refer to your client's own documentation for the precise menu path — the JSON entry above is the same in each case.

Pinning a version​

By default npx -y @deploygate/mcp follows the latest release. To pin a specific version, append it to the package name:

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

Authentication​

Authentication is identical to the plugin — a browser-based device authorization code flow, with no API token to paste. Ask your agent to set up or log in to DeployGate; under the hood it calls the login_start tool, which returns a short URL and code. Open the URL in a browser where you are signed in to DeployGate, approve, and the agent finishes the login via login_wait.

The issued token is stored on your machine and shared with the plugin installs — if you have already logged in through the Claude Code / Codex plugin, the standalone server reuses the same token.

PlatformToken path
macOS / Linux~/.config/deploygate/token (or $XDG_CONFIG_HOME/deploygate/token)
Windows%APPDATA%\deploygate\token

See the MCP Tools Reference for the full login flow, error cases, and the logout tool.

What you can do​

Once connected, the full set of DeployGate MCP tools is available — uploading builds, managing distribution pages, onboarding members, managing workspaces, and more. See the MCP Tools Reference for the complete tool list and parameters.

Source​

@deploygate/mcp is open source. See the GitHub repository for source code, issue tracking, and release notes.

Last updated on