MCP Server

The deploybase MCP (Model Context Protocol) server lets AI coding assistants manage deployments, projects, and domains through natural language. It exposes 26 tools that map to the deploybase REST API.

Transports

Transport	Auth	Use Case
stdio (default)	API key	Local IDE integration (Claude Code, Cursor, etc.)
HTTP	OAuth JWT	Remote/hosted MCP server

Configuration

Claude Code

Add to your project’s .mcp.json:

{
  "mcpServers": {
    "deploybase": {
      "command": "deploybase-mcp",
      "args": ["--transport", "stdio"],
      "env": {
        "DEPLOYBASE_API_KEY": "dbk_your_api_key",
        "DEPLOYBASE_API_URL": "https://api.deploybase.eu"
      }
    }
  }
}

Other MCP Clients

The MCP server binary is deploybase-mcp. It reads configuration from environment variables:

Variable	Required	Description
`DEPLOYBASE_API_KEY`	Yes (stdio)	API key with `dbk_` prefix
`DEPLOYBASE_API_URL`	No	API base URL. Default: `https://api.deploybase.eu`

Tools Reference

Projects

Tool	Type	Description
`list_projects`	Read	List all projects. Supports `search` filter by name. Returns name, slug, framework, production URL, latest deployment status.
`get_project`	Read	Get full project details: git URL, framework, build command, output directory, production URL, live deployment ID.
`create_project`	Write	Create a new project. Accepts: name, framework, git_repo_url, git_provider, git_token, build_command, output_dir, default_branch.
`update_project`	Write	Partial update of project settings. Only provided fields are changed.
`delete_project`	Destructive	Permanently delete a project and all its deployments, domains, and share links. Irreversible.
`check_subdomain`	Read	Check if a subdomain is available for `sites.deploybase.eu`.
`validate_git_repo`	Read	Test whether a git repository is accessible with given credentials. Run before creating a project.

Deployments

Tool	Type	Description
`list_deployments`	Read	List deployments, filtered by `project_id` and/or `status`. Supports pagination.
`get_deployment`	Read	Full deployment details: status, branch, commit, CDN URL, build times. Poll every 5–10s after triggering to track progress.
`get_build_logs`	Read	Full build log output. Available for `building`, `deployed`, or `failed` deployments. Errors appear near the end.
`trigger_deployment`	Write	Trigger a build from a git branch. Returns immediately with `deployment_id`. Default branch deploys auto-promote to production.
`cancel_deployment`	Write	Cancel a `pending`, `queued`, or `building` deployment. Returns 409 for terminal statuses.
`promote_deployment`	Destructive	Promote a deployment to production (instant re-alias). Also how rollback works. Only `deployed` status allowed.

Domains

Tool	Type	Description
`list_domains`	Read	List custom domains with verification and SSL status.
`get_domain_status`	Read	Full domain details including DNS verification instructions and TXT record value.
`add_domain`	Write	Add a custom domain to a project. Returns verification token for DNS TXT record.
`verify_domain`	Write	Trigger DNS verification. Rate limited: once per 60s per domain. SSL provisioned automatically after success.
`get_dns_instructions`	Read	Get DNS records to configure: TXT for verification, CNAME for traffic routing.
`remove_domain`	Destructive	Remove domain, SSL certificate, and CDN mapping. Traffic falls back to default URL.

Tool	Type	Description
`create_share_link`	Write	Create a proxied share URL for any deployment. Optional password (min 8 chars) and expiry (`24h`, `7d`, `30d`).
`revoke_share_link`	Destructive	Instantly revoke a share link. Viewers lose access immediately.

Migrations

Tool	Type	Description
`analyze_project_config`	Read	Parse a hosting platform config file (`vercel.json`, `netlify.toml`, `wrangler.toml`) and return deploybase-equivalent settings.
`migrate_from_vercel`	Write	One-step migration: parse config, create project, trigger first deployment.
`migrate_from_netlify`	Write	One-step migration: parse config, create project, trigger first deployment.
`migrate_from_cloudflare`	Write	One-step migration: parse config, create project, trigger first deployment.

Migration tools return analysis results, project info, deployment info, and any manual steps needed (e.g. environment variables to set, unsupported features).

Billing

Tool	Type	Description
`get_billing_plan`	Read	Current plan, usage (bandwidth, build minutes, project count), limits, and billing period dates.

Workflow Examples

Deploy a new site

1. validate_git_repo → confirm access
2. create_project → get project_id
3. trigger_deployment → get deployment_id
4. get_deployment (poll) → wait for status=deployed
5. get_build_logs → inspect if failed

Migrate from Vercel

1. analyze_project_config → preview migration (optional)
2. migrate_from_vercel → creates project + triggers deployment
3. get_deployment (poll) → track build
4. add_domain → set up custom domain

Rollback production

1. list_deployments (project_id, status=deployed) → find previous
2. promote_deployment → instant rollback