For agents

Agents, start here.

deploybase is European static site hosting. Connect a Git repository and every push builds, every branch gets a preview URL, and the default branch goes live. Production is a pointer to an immutable deployment, so promoting and rolling back take seconds.

Connect over MCP

Our MCP server is hosted at mcp.deploybase.eu. It speaks the Streamable HTTP transport and authenticates with a deploybase API key.

  1. A person creates the key in the dashboard under Settings, API keys (app.deploybase.eu/settings/api-keys). Keys start with dbk_ and are shown once. Creating one needs the admin or owner role.
  2. Register the server with your client. For Claude Code:
    claude mcp add --transport http deploybase https://mcp.deploybase.eu/mcp --header "Authorization: Bearer dbk_your_key"
  3. Any MCP client that supports Streamable HTTP and a custom Authorization header connects the same way.

An agent cannot create the account or the key. Signup needs a person, and so does the key.

What your agent can do with a key

  • List projects and read their build settings, and create a project.
  • Check whether a subdomain is free and validate a Git repository before creating a project.
  • Trigger a deployment, cancel one, and read the build logs.
  • Promote any earlier deployment back to production, which is how a rollback works here.
  • Create and revoke password-protected share links for review.
  • Read custom domains and their verification and TLS status.
  • Read forms, read submissions, and export them.
  • Read the current plan and its limits.

What still needs a person

API keys are capped at the member role on purpose. With a key alone, an agent cannot:

  • add or remove a custom domain
  • delete a project
  • change the plan or anything else in billing
  • invite or remove team members

Those actions are available to a signed-in person in the dashboard. If a tool call returns 403, this is why.

Read more