Point Claude Code, Cursor, or any MCP client at the QuickCasa server and it can build websites, work leads, run cadences, and more, in plain language. Two minutes, one key.
You need one thing to start: a company API key. A website ID is optional.
Create one in the QuickCasa client portal at https://clients.quickcasa.ai/developer/api-keys - go to Developer, then API Keys, then Create Key.
Only needed if you want to lock the connection to one site. Open a website in the builder and copy the ID from the URL: /website-builder/hcDdbK94qSRYUcqFVMyC. No site yet? Skip it and ask the AI to create one with create_website.
Paste your key below and copy the config for your tool. The fields update it live - nothing is sent anywhere, it all runs in your browser.
url + x-api-key header works in any MCP-compatible client. Prefer not to hardcode the key? Reference an env var instead: "x-api-key": "${QC_API_KEY}".
?mode=lite to the URL and only a handful load up front - your agent discovers the rest on demand with find_tools and calls them with run_tool. Same power, a fraction of the context.
One optional set of headers turns on image generation (imagine) - your own provider key, kept out of the model's context. Memory, personalisation, and notifications come from a small config file instead.
.quickcasa-mcp.json file - set it up by just asking your agent: "set up my Supercharger". Full details on the Supercharger page.
Once connected, just talk to it. A few good openers:
The key is not reaching the server. Check it is in the headers block (not the URL), has no stray spaces, and is a live key from the client portal. If you used an env var, confirm it is actually set in the shell that launches your editor.
You are on a personal key. Ask the AI to run connect_company with a company API key, or add one from the client portal. Company keys carry the company automatically.
Tools that edit a site need one selected. Ask "list my websites" then "switch to <name>", or pin one with ?websiteId= on the URL. CMS, media, leads, and cadences do not need a website.
Restart your editor after editing mcp.json - most clients only read it on launch. In Claude Code, run /mcp to see connection status and reconnect.
Use straight quotes (not smart quotes) in mcp.json, and forward slashes in any paths. If claude is not found, make sure the CLI is installed and on your PATH, then reopen the terminal.
Ask the AI to "read the QuickCasa developer guide" - it loads the full reference. It can also file a bug for you with send_bug_report.
Paste it above, copy the config, and start building.