Cursor × OpenBerth

Deploy from Cursor

Cursor speaks MCP natively. Drop a JSON snippet into ~/.cursor/mcp.json and the IDE can deploy whatever it just helped you build.

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

Connect Cursor in under a minute

Cursor's MCP config lives at ~/.cursor/mcp.json. Add one server entry, reload, and the chat panel can deploy.

  1. Open Cursor Settings → Features → Model Context Protocol, or edit ~/.cursor/mcp.json directly.
  2. Paste this server block.
    ~/.cursor/mcp.json
    {
      "mcpServers": {
        "openberth": {
          "url": "https://yourdomain.com/mcp",
          "headers": {
            "Authorization": "Bearer bt_your_api_key"
          }
        }
      }
    }
  3. Reload Cursor's MCP servers from the same settings panel.
  4. In any chat, ask: “deploy this project to my OpenBerth server.” Cursor invokes the MCP tools and ships it.

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

  • Does Cursor's free plan support MCP?
    Yes. MCP is a Cursor feature, not a tier. Any plan that has chat access can use MCP servers.
  • Where do I find the Cursor MCP config file?
    On macOS and Linux: ~/.cursor/mcp.json. On Windows: %USERPROFILE%\.cursor\mcp.json. If it doesn't exist, create it — Cursor reads it on the next reload.
  • Can I have multiple MCP servers?
    Yes. The mcpServers object holds as many keyed entries as you like. Cursor exposes all their tools to the chat.
  • Why is Cursor showing a red MCP indicator?
    Usually a typo in the URL or a missing Bearer prefix. Open Settings → MCP, click the server name, and check the error message. Reload after fixing.
  • Will this work in Cursor Composer / Background Agent?
    Yes. MCP tools are available wherever Cursor's agent runs — Chat, Composer, and Background Agent all share the same tool pool.

Ready to ship from Cursor?

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