Use Apployd with MCP Clients

What the MCP package does

The Apployd MCP package exposes deployment operations as MCP tools over stdio. An MCP client starts the package locally, then calls Apployd APIs through the authenticated session on behalf of the user.

This makes it possible to list projects, create deployments, inspect recent releases, and cancel active deployments without building a separate integration for each client.

• Package name: @apployd/mcp-server
• Launch mode: stdio MCP server started by the MCP client
• Auth flow: browser login similar to npm login or gh auth login
• Core tools: get_current_user, list_projects, list_recent_deployments, list_project_deployments, get_deployment, create_deployment, cancel_deployment

Install and sign in

Users do not need to clone the Apployd repo. The recommended path is to run the published npm package directly with npx, then complete the browser login flow once on that machine.

After login, the package caches credentials locally and most MCP clients can start the server without passing APPLOYD_API_TOKEN explicitly.

npx -y @apployd/mcp-server login
npx -y @apployd/mcp-server whoami

npx -y @apployd/mcp-server logout

Add it to an MCP client

Most MCP clients can start the package with npx. In the simplest setup, only the Apployd API base URL is required because the cached login session supplies the token automatically.

Set APPLOYD_DEFAULT_ORGANIZATION_ID when the authenticated user belongs to more than one organization and the client should not prompt the agent to disambiguate.

{
  "mcpServers": {
    "apployd": {
      "command": "npx",
      "args": ["-y", "@apployd/mcp-server"],
      "env": {
        "APPLOYD_API_BASE_URL": "https://apployd.com/api/v1",
        "APPLOYD_DEFAULT_ORGANIZATION_ID": "optional organization cuid"
      }
    }
  }
}

Common usage patterns

Once the MCP client is configured, the user can ask the client to operate on Apployd resources in natural language. The MCP package translates those requests into the underlying API calls.

Good prompts are explicit about the project, environment, and source reference so the resulting deployment matches the intended release.

• List my Apployd projects.
• Show the latest deployments for my organization.
• Deploy project abc123 to production from branch main.
• Cancel deployment dep_123 if it is still in progress.

Direct environment-variable auth

For controlled environments such as CI, shared workstations, or clients that should not rely on local cached credentials, set the token explicitly in the MCP client configuration.

{
  "mcpServers": {
    "apployd": {
      "command": "npx",
      "args": ["-y", "@apployd/mcp-server"],
      "env": {
        "APPLOYD_API_TOKEN": "your apployd token",
        "APPLOYD_API_BASE_URL": "https://apployd.com/api/v1",
        "APPLOYD_DEFAULT_ORGANIZATION_ID": "optional organization cuid"
      }
    }
  }
}

FAQ