Point ChatGPT, Claude, Claude Code, Cursor, or any MCP client at the QuickCasa server and it can work your leads, book tours, manage follow-ups, build websites, and more, in plain language. Chat apps sign in with your QuickCasa account. Developer tools use a key.
Chat apps cannot send an API key, so they do not need one. Add QuickCasa as a connector, sign in with the account you already use for the client portal, pick your company, and you are done. It works like connecting Google Drive or Slack.
In ChatGPT: Settings, then Connectors, then Create (developer mode). In Claude: Settings, then Connectors, then Add custom connector. Name it QuickCasa and paste this URL:
https://api.quickcasa.ai/v1/mcp
Leave the client id and secret blank. The app registers itself.
A QuickCasa page opens. Sign in if you are not already, pick the company to connect (most people only have one), and press Allow access. You are sent straight back to the chat. Belong to several? Tell the AI to switch company any time; it only ever sees companies you are an employee of.
"Who came in this week and has not heard back?", "Book a tour for Maria on Thursday afternoon", "Add a note that the Wilsons want a two bedroom with parking". It acts as you and only sees what you can see.
Chat apps get the day-to-day leasing toolset (about 30 tools) so they stay fast and sharp. Everything else is a find_tools away, or add ?mode=full to the URL.
Claude Code, Cursor, and other editors can send headers, so they use a 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 and belong to more than one company, so the server will not guess. Ask the AI to run switch_company: with no arguments it lists your companies, with a name or id it switches. A personal key whose owner is in exactly one company connects to it automatically, and company keys carry the company always.
Access lasts seven days and renews itself while the app is in use. If it lapses, remove the QuickCasa connector in the app and add it again; you will be asked to sign in once more. Nothing in QuickCasa is lost.
Only site-building tools need one: pages, files, publishing, redirects, fonts, revisions, and per-site settings. Ask "list my websites" then "switch to <name>", or pin one with ?websiteId= on the URL. Everything else is company-level, so leads, cadences, CMS, media, inventory, quotes, calendars, and the product-knowledge tools all work without a website. Connecting itself never needs one.
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 the URL, sign in, and start asking. Developers: grab a key and copy the config above.