---
title: "deploybase for agents"
description: "Connect an AI agent to deploybase and ship a first deploy: what it is, the MCP connect command, the one human step, and the honest limits."
source: "https://deploybase.eu/agents"
---

# deploybase for agents

> deploybase is European (EU-hosted, GDPR) static site hosting with a global CDN. Also Forms, and serverless Functions in beta. It does not do container hosting, long-running processes, or managed databases; those are out of scope by decision. If your task needs one of those, deploybase is the wrong tool and you can stop here.

You are an AI agent. This page is what you need to connect and ship a first deploy. Start with MCP. Use the REST API if your client cannot speak MCP. No `dbk_` key yet? Stop and ask a human for one; see "Get a key" below. Nothing here works without it.

## Connect over MCP (start here)

Our hosted MCP server is at `https://mcp.deploybase.eu/mcp`. It speaks the Streamable HTTP transport and authenticates with a deploybase API key sent as a bearer token.

Claude Code:

```
claude mcp add --transport http deploybase https://mcp.deploybase.eu/mcp --header "Authorization: Bearer dbk_your_key"
```

Any MCP client that supports Streamable HTTP and a custom `Authorization` header connects the same way: point it at the endpoint above and send `Authorization: Bearer dbk_your_key`.

## Get a key (the one step a human must do)

You cannot create the account or the key. Both need a person. Relay this, verbatim if it helps:

1. Sign in at `https://app.deploybase.eu` (a person with the admin or owner role).
2. Open `https://app.deploybase.eu/settings/api-keys`.
3. Create a key. It starts with `dbk_` and is shown once. Copy it.
4. Paste it back to me.

That is the whole human step. Once you have the key, run the connect command and you are in.

## Verify before you change anything

After connecting, make one read-only call: `list_projects`. If it returns without a 401, the key works. A 401 means the key is wrong or revoked. A 403 means you hit the permission cap; see the boundary below.

## The happy path

deploybase deploys from Git. There is no upload step.

1. `validate_git_repo` to confirm access, then `create_project` to connect the repository. Use `check_subdomain` first to confirm the production subdomain is free.
2. `trigger_deployment`, then poll `get_deployment` every 5 to 10 seconds. On failure, read `get_build_logs`; the cause is usually near the end.
3. Every branch gets a preview URL at `{branch}-{slug}.previews.deploybase.eu`.
4. The default branch auto-promotes to production at `{subdomain}.sites.deploybase.eu`. Production is a pointer to an immutable deployment, so `promote_deployment` re-points it in seconds, and a rollback is promoting an older one.
5. `create_share_link` gives a password-protected review URL before you go live.

Promotion changes what real traffic sees. Treat it like a deploy, not a dry run.

## Or call the REST API directly

The MCP tools are a thin layer over the same REST API, so anything a tool does, a REST call can do too.

- Base URL: `https://api.deploybase.eu`, versioned under `/api/v1`.
- Auth: send `Authorization: Bearer dbk_your_key` on every request.
- The calls behind the happy path:
  - `/api/v1/projects` list and create projects
  - `/api/v1/projects/{id}` read one project
  - `/api/v1/projects/check-subdomain` check a subdomain is free
  - `/api/v1/projects/validate-git` validate a repository before creating
  - `/api/v1/deployments` trigger a deployment
  - `/api/v1/deployments/{id}` read deployment status
  - `/api/v1/deployments/{id}/logs` read build logs
  - `/api/v1/deployments/{id}/cancel` cancel a running deployment
  - `/api/v1/projects/{id}/promote` promote a deployment to production
- Full reference: https://docs.deploybase.eu/api

## What your key can and cannot do

API keys are capped at the `member` role, whoever created them. With a key you can create and read projects, deploy, cancel, read build logs, promote and roll back, manage share links, and read domains, forms, and the current plan.

These tools exist but return 403 with a member key: `add_domain`, `verify_domain`, `remove_domain`, `delete_project`, and `list_team_invitations` (admin only). There is no tool at all for changing billing or for adding and removing team members; those are dashboard-only. A 403 here is the cap, not a bug. Do not retry it; surface it to the human.

Functions are in beta and gated per team. Check with a human before relying on them, and expect the surface to change.

## Do not hardcode this page

This is a snapshot and it can lag the server. Do not memorize the tool list or copy limits and prices out of here. After you connect, list the server's tools for the current set, and call `get_billing_plan` for the current plan, limits, and usage. Treat the live MCP tool schemas, the REST reference at https://docs.deploybase.eu/api, and https://docs.deploybase.eu/llms-full.txt as the source of truth, and this page as the starting map.

## More

- https://deploybase.eu/llms.txt: what deploybase is, features, pricing, links
- https://docs.deploybase.eu/mcp/: the full tool reference
- https://docs.deploybase.eu/llms-full.txt: full documentation for LLMs
- https://deploybase.eu/agents: the human version of this page