HIVE CLI Docs
Home
Docs / Deploy on Vercel

Deploy on Vercel

Host the generated MCP server on your own Vercel account and use it from Claude or ChatGPT.

How it works

Chat apps like Claude and ChatGPT reach MCP servers over the internet, so a server on 127.0.0.1 isn't enough for them. deploy hosts the generated server as a Vercel Function on your own Vercel account and prints a private link to paste into the chat app. No HIVE account is needed.

Before you deploy

Generate the server first with scan --install, and deploy your app itself, because the hosted server calls your live app's API. If the API needs a credential, set HIVE_APP_BEARER_TOKEN (preferred) or HIVE_APP_COOKIE in .hive/mcp/.env. Cookies expire and break the live server, so use an API key when you can.

Deploy

terminal
npx @usehive/cli deploy --app-url https://myapp.com

The first time, vercel login opens your browser. HIVE then runs three steps:

1. Checks your live appYour app must already be deployed, because the hosted server calls its API over the internet. HIVE refuses localhost and private addresses, and flags an offline app, routes missing from the live version, and API keys the app rejects. Write routes are only probed with OPTIONS, never called.
2. DeploysBuilds a Vercel Function from .hive/mcp through the Vercel CLI; vercel login opens your browser the first time. The project is named <app>-mcp, and --project overrides it.
3. VerifiesCalls the live endpoint the way a chat app would (initialize, then tools/list) before printing the link.

Your secret link

The link looks like https://<app>-mcp.vercel.app/mcp/<secret>. Anyone with it can use the approved tools, so keep it private. If it leaks, run deploy --rotate-key: you get a new link and the old one stops working.

Connect Claude

Add the link as a custom connector and choose No sign-in. On Team and Enterprise plans, an Owner adds it under Organization settings → Connectors.

Connect ChatGPT

Add a custom MCP server with the link and choose No authentication.

Keep it up to date

The deployment uses a snapshot of .hive/mcp/.env and .hive/policy.json. Run deploy again after changing tools, the policy, or running sync. The link stays the same.

deploy --app-url <url>First deploy. Checks your live app, deploys, verifies, and prints the link.
deployRedeploy with the same link, after changing tools, the policy, or running sync.
deploy --rotate-keyRedeploy with a new secret link. The old link stops working.
deploy --project <name>Use a Vercel project name other than <app>-mcp.

Limits

HostingVercel only, on your own account. Other hosting providers aren't supported yet.
AccessOne shared secret link per deployment. Per-user OAuth isn't supported yet.
PlanThe free Hobby plan works for personal, non-commercial use. Commercial use needs Vercel Pro.
LogsAgent calls appear in the Vercel project's runtime logs, not .hive/logs.