Connect Casa to your AI tools

Choose your AI tool

Select the app you use, then follow its setup below. Replace the example key only in your own configuration.

Connect Cursor

Let your AI help set this up

Give your assistant the instructions, then enter your API key privately.

View prompt

Read https://docs.casamakes.com/mcp/setup.md and help me connect Cursor to Casa MCP. Preserve my existing MCP servers. Have me enter my Casa API key privately in my local configuration, not in this chat. Verify the connection with a read-only workspace request. Do not create, edit, or remove any Casa data during setup.

AI setup guide · llms.txt

Open Cursor’s MCP settings, or edit ~/.cursor/mcp.json for a connection available across your projects. Add the configuration below and replace YOUR_API_KEY_HERE with your Casa key.

If the file already has an mcpServers object, add just the casa-v1 entry inside it. Preserve your other servers. Save, enable casa-v1 in Cursor, and open an Agent chat.

Cursor configuration

{
  "mcpServers": {
    "casa-v1": {
      "url": "https://plugins.casamakes.com/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Cursor’s MCP setup reference →

Connect Claude Desktop

Let your AI help set this up

Give your assistant the instructions, then enter your API key privately.

View prompt

Read https://docs.casamakes.com/mcp/setup.md and help me connect Claude Desktop to Casa MCP. Preserve my existing MCP servers. Have me enter my Casa API key privately in my local configuration, not in this chat. Verify the connection with a read-only workspace request. Do not create, edit, or remove any Casa data during setup.

AI setup guide · llms.txt

Install a current Node.js LTS release first; it includes npx. In Claude Desktop, open Settings → Developer → Edit Config. This setup uses mcp-remote to pass Casa’s API-key header.

Add the configuration below, replacing YOUR_API_KEY_HERE. If mcpServers already exists, merge the casa-v1 entry into it. Save, fully quit Claude Desktop, and reopen it. Look for casa-v1 in its available tools.

If Claude Desktop reports that npx is missing, install Node.js LTS and restart the app. For the terminal app, expand the Claude Code instructions below.

Claude Desktop configuration

{
  "mcpServers": {
    "casa-v1": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://plugins.casamakes.com/mcp",
        "--header",
        "X-API-Key:${CASA_API_KEY}"
      ],
      "env": {
        "CASA_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Download Node.js LTS →

mcp-remote setup reference →

Using Claude Code?

Let your AI help set this up

Give your assistant the instructions, then enter your API key privately.

View prompt

Read https://docs.casamakes.com/mcp/setup.md and help me connect Claude Code to Casa MCP. Preserve my existing MCP servers. Have me enter my Casa API key privately in my local configuration, not in this chat. Verify the connection with a read-only workspace request. Do not create, edit, or remove any Casa data during setup.

AI setup guide · llms.txt

With Claude Code installed, replace YOUR_API_KEY_HERE and run this command in your terminal. User scope makes the connection available across your projects.

Start Claude Code and enter /mcp to check casa-v1. If that name already exists, update its existing configuration instead of adding a second connection. The command contains your key, so keep terminal history private.

Claude Code command

claude mcp add --transport http --scope user --header "X-API-Key: YOUR_API_KEY_HERE" casa-v1 https://plugins.casamakes.com/mcp

Claude Code’s MCP setup reference →

Connect OpenAI Codex

Let your AI help set this up

Give your assistant the instructions, then enter your API key privately.

View prompt

Read https://docs.casamakes.com/mcp/setup.md and help me connect OpenAI Codex to Casa MCP. Preserve my existing MCP servers. Have me enter my Casa API key privately in my local configuration, not in this chat. Verify the connection with a read-only workspace request. Do not create, edit, or remove any Casa data during setup.

AI setup guide · llms.txt

Open ~/.codex/config.toml and add the configuration below. Replace YOUR_API_KEY_HERE with your Casa key. If a casa-v1 entry already exists, update it instead of adding another.

Save the file and start a new Codex session. In the CLI, run codex mcp list to check that casa-v1 is configured. Keep this personal configuration private.

Codex configuration

[mcp_servers.casa-v1]
url = "https://plugins.casamakes.com/mcp"
http_headers = { "X-API-Key" = "YOUR_API_KEY_HERE" }

OpenAI’s MCP setup reference →

Connect GitHub Copilot in VS Code

Let your AI help set this up

Give your assistant the instructions, then enter your API key privately.

View prompt

Read https://docs.casamakes.com/mcp/setup.md and help me connect GitHub Copilot in VS Code to Casa MCP. Preserve my existing MCP servers. Have me enter my Casa API key privately in my local configuration, not in this chat. Verify the connection with a read-only workspace request. Do not create, edit, or remove any Casa data during setup.

AI setup guide · llms.txt

In VS Code, open the Command Palette and run MCP: Open User Configuration. Add the example below, replacing YOUR_API_KEY_HERE with your Casa key. If the file already has a servers object, merge the casa-v1 entry into it.

Save, run MCP: Show Installed Servers, and start casa-v1. Review the trust prompt, then open Copilot Chat and enable the Casa tools for your agent session. Keep the key in your personal configuration and out of shared repositories.

VS Code MCP configuration

{
  "servers": {
    "casa-v1": {
      "type": "http",
      "url": "https://plugins.casamakes.com/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

VS Code’s MCP setup reference →

Try your first request

Start a new conversation and ask the assistant to use Casa. Review its tool request when your client asks for permission.

Check that the answer names the workspace, projects, and rooms you expected. An empty new workspace may have no projects yet. A connected indicator alone does not confirm that your key can access workspace data.

Use Casa to show my workspace, projects, and rooms. Do not create or change anything.

What you can ask Casa to do

Start with workspace context, then name the project and room you want. For changes, ask the assistant to show its plan and wait for your approval. Reopen Casa afterward to check the saved result.

• Explore your workspace, list products, and inspect a product’s details.
• Create or rename projects and rooms.
• Create blank products, import supplier URLs, and update product details, suppliers, shipping, or procurement status.
• Move, copy, or remove products, change their schedule, and choose a cover image.
• Check the status of an existing export. This does not create a new export.

Find the furniture in my Living Room and summarize which products are missing prices or dimensions. Show me the list before making any changes.

If the connection does not work

“Missing X-API-Key header” in your browser is expected: opening the endpoint directly does not send your key. Configure an MCP client using one of the examples above.

If a tool rejects the key, confirm you replaced the placeholder, copied the entire casa_ key, and used the X-API-Key header. A revoked key must be replaced. If you see the wrong workspace, use a key created in the intended workspace.

If you still have an old setup, replace its IP-based URL with https://plugins.casamakes.com/mcp and remove --allow-http. Save and restart the client.

If requests time out, retry once and check your network. Contact Casa Support from the app with the client name and error text, leaving out your API key.

Understand your key’s access

The key lets the connected assistant read and modify data in its Casa workspace; it is not a read-only connection. Share this guide with designers so each person can configure their own authorized access. Do not share a working key in a message, screenshot, or repository.

Revoke an exposed or unused key in Casa Settings → API Keys. Removing a client configuration does not revoke the key.

The public endpoint uses HTTPS to Cloudflare. The connection from Cloudflare to the existing Casa MCP server currently uses HTTP.

Check the result

Your assistant can read the intended Casa workspace through casa-v1, and you have checked that the returned projects and rooms match Casa Studio.

Keep exploring