Hosted MCP server/Cloud Service

WebBase MCP server

Hosted at mcp.webbase.dev·Streamable HTTP

WebBase is web hosting that an AI assistant operates over a remote, hosted MCP endpoint. It creates the project, writes files, deploys, and reports the live address, such as <name>.webbase.dev or a custom domain. It supports static HTML, Next.js static and SSR, Postgres, custom domains, environment variables, visitor stats, and team members. The server exposes 30 tools, authenticates with a wdp_ token (Bearer header or ?token= in the URL), runs on servers in Germany, and offers a free plan.

mcp.webbase.dev Streamable HTTP API key (Bearer wdp_ token or ?token= URL) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Developers and small teams that want an assistant to create, deploy, and manage web projects end to end.

  • Create a new project and deploy it to a live address.
  • Add Postgres and environment variables to a deployment.
  • Attach a custom domain and review visitor stats.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Remote hosted endpoint (Streamable HTTP)

WebBase is hosted at https://mcp.webbase.dev/mcp. Use the personal URL with ?token=wdp_... or send Authorization: Bearer <wdp_TOKEN>. There is nothing to install locally.

  1. Open the token page

    In WebBase, open the MCP settings and copy the personal MCP URL containing your wdp_ token.

  2. Add the remote server

    Register the URL as a remote Streamable HTTP server, or use the equivalent mcp.json entry with an Authorization: Bearer header.

    claude mcp add --transport http webbase "https://mcp.webbase.dev/mcp?token=wdp_YOUR_TOKEN"
  3. Deploy from the assistant

    Ask the assistant to create the project, write files, deploy, and return the live address.

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://mcp.webbase.dev/mcp
Host
mcp.webbase.dev · /mcp
Transport
Streamable HTTP
Authentication
API key (Bearer wdp_ token or ?token= URL)
Server name
webbase
Listing type
Community or directory listing

The installer uses the server name webbase. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that webbase appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Create a new project and deploy it to a live address. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

WebBase documentationhttps://app.webbase.dev/en/docs