Claude.ai × OpenBerth

Connect Claude.ai to your OpenBerth server

Add a custom MCP connector once, then ask Claude to ship anything — from your laptop or your phone. OAuth handles auth, so you never paste an API key.

  • Live in 30 seconds
  • Your domain
  • No per-app bills
Quickstart

Connect Claude.ai in under a minute

Claude.ai authenticates via OAuth, so you only need the MCP URL. About 30 seconds, no terminal required.

  1. Open claude.ai/settings/connectors and choose Add custom connector.
  2. Paste the MCP URL below and save.
    MCP URL
    https://yourdomain.com/mcp
  3. Hit Connect — Claude redirects to your server to sign in. After that, the connector is live in any chat (web or mobile).
  4. In a chat, open the tools menu, enable OpenBerth, and ask: “deploy a hello-world page.”

Replace yourdomain.com with your server’s URL and bt_your_api_key with an API key from your workspace’s People page.

What you can do

Ask Claude.ai, OpenBerth handles it

Ship in one sentence

Ask the AI to deploy and it does. Real HTTPS URL in seconds, no dashboard tab-hopping.

Iterate in a sandbox

Push live edits to a sandbox berth. Promote when it's right, throw it away when it isn't.

Roll back any release

Every deploy is versioned. One command (or one ask) and you're back to the last good build.

Manage secrets in plain English

Set, list, rotate, delete — your env vars stay on your server, never in the chat transcript.

Why your own server

OpenBerth handles hosting, so you handle creating

It's yours. Forever.

Your apps live on a server you own. Nobody else holds your code, your domain, or your customer data.

No surprise bills

Pay your server's flat monthly fee. Ship one app or a hundred — the price doesn't change.

Built for real apps

Databases, file uploads, background jobs, custom domains. The boring stuff that makes a website feel like a real product.

Every AI ships to one place

Lovable, Cursor, Claude, Gemini — they all push to the same dashboard. One place to see what's live.

FAQ

Common questions

  • Do I need an API key for Claude.ai?
    No. Claude.ai uses OAuth — you click Connect and sign in to your OpenBerth server. The browser session handles auth from then on. API keys are only needed for headless tools like Claude Code or Cursor.
  • Does this work on mobile?
    Yes. Custom connectors sync between web and mobile Claude apps. Add it once on the web; mobile picks it up automatically.
  • Which Claude plans support custom MCP connectors?
    All of them — Free, Pro, Max, Team, and Enterprise. Free accounts are capped at one custom connector; paid plans can add more. If you don't see the Connectors section in claude.ai/settings, you're on a workspace where it's been turned off by an admin.
  • Can I revoke access?
    Two ways: remove the connector from claude.ai/settings/connectors, or rotate the user's API key on your OpenBerth dashboard's People page. Either kills the OAuth grant.
  • Is my code sent to Anthropic?
    Only what you put in the chat. The MCP server runs on your machine — Claude calls tools (deploy, status, logs) over HTTPS, but the apps themselves live on your server, not Anthropic's.

Ready to ship from Claude.ai?

Stand up a server in minutes, paste the snippet above, and your AI tool can deploy on its own.