Where does Claude Code store the MCP config?

In ~/.claude.json after `claude mcp add`. The config persists across sessions, so you only register once per machine.

Can I scope the MCP server to a single project?

Yes. Pass `--scope project` on `claude mcp add` and the registration lives in .claude/ inside the repo, not your home directory. Useful for repos with team-shared MCP setups.

How do I rotate the API key?

Run `claude mcp remove openberth`, then re-add with the new key. Or edit ~/.claude.json directly under mcpServers.openberth.headers.Authorization.

Does this conflict with other MCP servers?

No. Claude Code merges all registered MCP servers into the tool pool. Name them differently (e.g. openberth, github, linear) and they coexist.

What if my server uses a self-signed cert?

Use a real cert — Let's Encrypt is free and the OpenBerth installer wires it up. Self-signed certs trip Claude Code's HTTP client. Easier to fix the cert than the client.

Claude Code × OpenBerth

Deploy from Claude Code

One command registers OpenBerth as an HTTP MCP server. Then ask Claude Code to ship the project — it pushes straight to your box.

30-second setup Spin up your server →

Live in 30 seconds
Your domain
No per-app bills

Quickstart

Connect Claude Code in under a minute

Claude Code stores MCP config in ~/.claude.json. One add command, persistent forever.

Install the CLI if you don't have it.
Terminal
```
npm install -g @anthropic-ai/claude-code
```

Terminal

claude mcp add --transport http openberth \
  https://yourdomain.com/mcp \
  --header "Authorization: Bearer bt_your_api_key"

Run claude from any project directory and ask it to deploy: “use OpenBerth to ship this.”

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 Code, 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

Where does Claude Code store the MCP config?
In ~/.claude.json after `claude mcp add`. The config persists across sessions, so you only register once per machine.
Can I scope the MCP server to a single project?
Yes. Pass `--scope project` on `claude mcp add` and the registration lives in .claude/ inside the repo, not your home directory. Useful for repos with team-shared MCP setups.
How do I rotate the API key?
Run `claude mcp remove openberth`, then re-add with the new key. Or edit ~/.claude.json directly under mcpServers.openberth.headers.Authorization.
Does this conflict with other MCP servers?
No. Claude Code merges all registered MCP servers into the tool pool. Name them differently (e.g. openberth, github, linear) and they coexist.
What if my server uses a self-signed cert?
Use a real cert — Let's Encrypt is free and the OpenBerth installer wires it up. Self-signed certs trip Claude Code's HTTP client. Easier to fix the cert than the client.

Ready to ship from Claude Code?

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

Set up your server Star on GitHub

Connect another tool