The WebBase docs. One link, thirty tools.

Quick start. Online in three steps.

You need a free account and an AI assistant that speaks MCP. MCP (Model Context Protocol) is the open standard AI assistants use to operate tools. With it, your AI does not just write code, it publishes it too.

1. Sign up for free

   Create an account on app.webbase.dev. The Free plan costs nothing and covers three static websites.

   Start for free

2. Get your personal link

   Your dashboard shows your personal MCP link. It contains your API key wdp_… and looks like this:

   https://mcp.webbase.dev/mcp?token=wdp_••••••••••••

   Treat the link like a password: whoever has it can create and delete projects in your name. In the dashboard you can revoke keys and create new ones.

3. Give the link to your AI

   Add the link to your AI assistant as an MCP server, as described in the next section. Then just say what you want: “Build me a portfolio page and put it online.”

Authorization: Bearer wdp_••••••••••••

The first deploy. One sentence, three calls.

Deploy means publish: build the files and put them online under an address. You write one sentence, your AI calls the tools. This is what it looks like:

The register. Thirty tools, eight groups.

Everything your AI can do on WebBase. For each tool: what it is for, a sentence that triggers it, and the parameters exactly as the server validates them. You do not need to memorise anything. Your AI receives the same list when it connects.

Project types and limits. What each plan includes.

Every project has one of three types. Your AI picks it when it calls create_project, depending on what you want to build.

Database. Postgres, set up by your AI.

From Basic you get your own Postgres databases with their own credentials. Your AI creates them, builds the tables and connects them to your site. Five steps, all through tools:

1. db_create_databaseCreates the database.
2. db_queryCreates tables and reads or writes data, in SQL.
3. db_get_connection_infoReturns the credentials and a ready DATABASE_URL.
4. set_envAdds the DATABASE_URL to the project, encrypted.
5. deployRestarts the project. Your code reads process.env.DATABASE_URL.

Custom domains. Your address, with automatic TLS.

On paid plans your project also runs under your own domain. The certificate for HTTPS (TLS) is issued automatically. You only set two DNS records at your domain provider, your AI does the rest.

1. add_custom_domain registers the domain with the project and returns a verification value.
2. You set a TXT record: name _webbase-verify.your-domain.example, value is the verification value. It proves the domain is yours.
3. verify_domain checks the TXT record.
4. You set up routing: a CNAME from your domain to name.webbase.dev, or an A record pointing to the IP address the tool gives you.
5. verify_domain checks the routing and switches the domain on. From then on your project answers at https://your-domain.example.

How many domains per project you get depends on the plan. A domain can only be attached to one project. DNS changes sometimes take a while to show up everywhere; just call verify_domain again later. To detach a domain: remove_custom_domain.

Git. For everyone who would rather push.

Every project has a private Git repository on git.webbase.dev. Everything your AI writes with write_files ends up there. You can clone it and keep working yourself at any time.

1. get_git_credentials returns the clone URL with an embedded access token. Do not share it.
2. Clone, change, commit, push, as usual:

   git clone <clone-url>
   cd portfolio
   git add . && git commit -m "New start page"
   git push

3. A push to main or master starts the deploy automatically.

You can mix both: write files through tools and push through Git. Run git pull before you push so nothing collides.

Environment variables. Secrets kept apart from the code.

Environment variables are settings your code reads at start-up, such as an API key or the database address. They do not belong in the files, they belong in set_env.

Where

In Next.js projects, static export and SSR. Static HTML projects have no environment variables.

Names

Uppercase letters, digits and underscore, starting with a letter: ^[A-Z][A-Z0-9_]*$. At most 50 variables per call.

Reserved

PORT, NODE_ENV, HOME, PATH and HOSTNAME are set by the platform.

Storage

AES-256-GCM encrypted.

Applied

On the next deploy.

Reading

get_env lists the names. Values only with includeValues: true.

Team. Collaboration by invitation.

You can invite other people to a project. They get an email with a link, in German or English, and accept the invitation themselves. Anyone without an account signs up through the link. Shared projects show up in their list_projects.

Members may

Read and write files, git push, deploy, read logs and visitor statistics.

Members may not

See or set environment variables, manage domains, delete the project.

Owners only

Invite (invite_member), list (list_members) and remove (remove_member). Removing someone also ends their Git access immediately.

Frequently asked. Short answers.