mcpmake Cloud — Quickstart

Turn an OpenAPI spec, Postman collection, or HAR recording into an authenticated MCP server you own — generated deterministically, then hosted for you (or self-hosted) — and connect it to Claude, Cursor, or any MCP client. (Website/DOM input is an experimental preview — demo/scaffold only, no production or uptime promise.)

1. Create an account

1. Go to the dashboard and register with your email.
2. Verify your email — we send a confirmation link. You must verify before you can deploy a server. (Need another link? Use Resend on the dashboard.)

2. Deploy a server

From Dashboard → New Server, pick a source:

Click Deploy Server. When the build finishes you land on the server's detail page, which shows your endpoint and a one-time bearer token.

Save the token now. It is shown only once. If you lose it, re-deploy the server (the API re-deploy path rotates the token) or create a new server.

3. Connect your MCP client

Your server is reachable at https://<slug>.<domain>/mcp and requires the bearer token on every request. Replace YOUR_TOKEN with the token you saved.

Claude Desktop / Cursor

Add to claude_desktop_config.json (Claude) or your MCP config (Cursor):

{
  "mcpServers": {
    "my-server": {
      "url": "https://my-server-a1b2.mcpmake.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Claude Code (CLI)

claude mcp add my-server https://my-server-a1b2.mcpmake.dev/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Requests without a valid token are rejected (401/403), so keep the token secret — treat it like a password.

3a. Keeping a website server fresh

Website (from website) servers are generated against a snapshot of the site's DOM, so they can drift when the site changes. With the CLI you can re-crawl and self-heal an exported project locally:

mcpmake rescan ./site-mcp            # report drift + fragile selectors
mcpmake rescan ./site-mcp --write    # heal selectors and regenerate, then re-deploy

See Website MCP servers for the full workflow.

4. Add API secrets

If your generated server calls an upstream API that needs credentials (an API key, bearer token, basic auth), add them as Secrets on the server detail page. Secrets are encrypted at rest and injected into the container as environment variables. After adding or changing a secret, re-deploy the server so it picks up the new value.

Common secret names: API_KEY, BEARER_TOKEN, BASIC_USERNAME / BASIC_PASSWORD. The exact names your server expects are derived from its spec.

5. Limits and quotas

Each plan includes:

• a maximum number of hosted servers, and
• a monthly tool-call allowance.

When you hit a limit, server creation is blocked (with an upgrade prompt) and over-quota tool calls are rejected with 429 Too Many Requests. Browser-driven (website) servers also consume browser minutes. See the Billing page for your current usage and remaining quota.

What counts as a tool call: one tools/call (each one in a JSON-RPC batch counts separately), metered when it is forwarded — a call that errors still counts. The handshake (initialize, tools/list, server/discover, ping), async-task polling (tasks/*), and health probes are not billed. See Billable-events policy for the full definition.

6. Pricing

The mcpmake CLI and the self-managed GitHub Action are free forever (Apache-2.0). The paid products are done-for-you migration and a managed-maintenance pilot (private beta) — see the Pricing section in the README. Managed hosting (this page) is a convenience add-on: it hosts code you already own, and you can take it self-hosted at any time.

Managed hosting is offered to an invitation-only validation cohort as a single add-on — the Managed HTTP Runtime ($49/month, 3 active HTTP targets). Additional targets are not self-serve yet; manual/invitation-only expansion is priced at $15/target when enabled. It is shown on the Dashboard → Billing page, where limits always match what the billing engine enforces. Every server you deploy is code you own: you can export it and self-host on your own infra, Cloudflare, or Docker at any time, so declining managed hosting never blocks you.

Browser-driven (website/Playwright) runtimes are not part of self-service hosting — they are an individually-approved, quote-only beta and consume metered browser minutes. Ask us if you need one.

Per-plan tool-call overage above the included quota is not billed: a request past the cap is rejected with 429 Too Many Requests until you upgrade (or ask for promotional credits). You can change or cancel a managed-hosting plan anytime from Dashboard → Billing; cancellation takes effect at the end of the current period.

CLI error reporting (telemetry)

When a CLI command fails, mcpmake can send an opt-in, redacted crash report so we can fix the failures real users hit. It is strictly opt-in and never blocks or slows down the CLI.

Control it with the global telemetry key in your .mcpmake.yaml:

# .mcpmake.yaml
telemetry: prompt # prompt | auto | off  (default: prompt)

Regardless of the configured mode, telemetry auto-degrades to off in CI or any non-interactive (non-TTY) environment, so it can never hang a pipeline waiting for input.

A crash report contains only: the command name (e.g. from openapi), the error message and stack trace, the CLI version, your OS/arch, and the Node version. It never includes file contents, environment variables, or secrets. Before sending, mcpmake redacts home-directory paths (/Users/<you>/… → ~), bearer tokens, mcpmake mf_…/mfd_… tokens, and URL query strings, so credentials embedded in paths or URLs don't leak.

Troubleshooting

• 401 Unauthorized — the Authorization: Bearer header is missing or malformed in your client config.
• 403 Forbidden — the token is wrong. Re-check it, or re-deploy to rotate.
• 429 Too Many Requests — you've hit your monthly tool-call quota; upgrade your plan or wait for the next period.
• 503 Server is not running — the server was paused or is rebuilding; try again, or open the server's Logs to investigate.
• Build failed — check that your spec is valid and under 5 MB; the server's Logs page shows build output.

Questions: support@mcpmake.dev