WebBase

dev.webbasePublished by webbase.devOfficial publisherv1.0.0Updated Oct 27, 2026

Web hosting your AI runs itself over MCP: deploy sites, Next.js, Postgres, domains. EU servers.

VerifiedStreamable HTTPWeb executableDatabasesCloud & Infrastructure

Overview

AI-generated overview

Remote MCP server that lets an AI deploy and manage web hosting itself: sites, Next.js apps, Postgres databases and domains.

What you can do
  • Deploy and manage hosted websites and Next.js applications
  • Provision and manage Postgres databases
  • Handle domains for hosted projects
  • Operate the hosting setup end to end from the assistant, on EU servers
When to use it
Useful when you want an assistant to stand up and maintain web hosting — publishing a site or Next.js app, adding a database and a domain — without switching to a separate control panel.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime. A WebBase account and a personal API key (wdp_…) sent in the Authorization header, which the provider offers free on registration.
Before you install
The API key in the Authorization header grants access to your WebBase account and hosted resources, so keep it secret. The assistant can create and change hosting, databases and domains, which may affect live sites and may incur costs depending on your plan.

Installation

In SourceWeft

  1. Open WebBase in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.webbase%2Fwebbase/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "webbase": {
      "type": "http",
      "url": "https://mcp.webbase.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 20, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.