FAQ

Short answers for product owners and engineers sharing a seat.

What do I need?

OpenAPI JSON, a public base URL for your API, and an optional upstream API key. Sign in with a magic link, import the spec, install the MCP URL.

Which clients work?

Anything that speaks remote Streamable HTTP MCP with a Bearer token — Cursor, Claude (Desktop / Claude.ai connectors with Request headers, or Claude Code), VS Code, Windsurf, and custom agents. ChatGPT custom MCP is OAuth or no-auth only, so it cannot use MakeCallable until an OAuth broker ships.

Do I have to learn MCP or rebuild my API?

No. Keep the REST API you have. We map OpenAPI operations to tools, host the MCP endpoint, and proxy authenticated calls upstream.

How do you measure revenue?

Every proxied tool call is logged. When an agent-driven outcome closes, you tag a revenue / GSV event so you can attribute the traffic.

Why the seat cap?

Early access is capped (default 50) so support stays real. When seats fill, the page takes a waitlist — no silent fail.

Where does data live?

Auth and Postgres on Supabase in eu-central-1. Upstream calls go to the base URL you set. Private, localhost, and metadata hosts are blocked.

Is there a dashboard UI agents use?

Agents don’t use your marketing site. They call tools. Humans use the MakeCallable dashboard to import specs, install MCP, read call logs, and tag GSV.

Can non-engineers use this?

Yes for the story and install copy. Import still needs OpenAPI JSON today. If your team doesn’t have a spec, an engineer (or white-glove help) produces one once — then product can watch calls and revenue.

YAML? OAuth? Billing?

Post-MVP. See the public roadmap posture: YAML import, OAuth 2.1 broker, and billing come after the capped loop proves out.

How do I get support?

Email hello@makecallable.com. Include your project slug, a redacted OpenAPI snippet, base URL host, and the client you’re installing.

---

Start here: Quickstart