Huxly

Connect Claude Code, Cursor, Windsurf, ChatGPT, Codex, or Antigravity directly to your Huxly projects. Build with your own AI subscription.

---

The AI Connector lets you point your existing AI tools — Claude Code, Cursor, Windsurf, ChatGPT, Codex, Antigravity — directly at your Huxly projects. Your AI reads real files, pushes edits, starts the sandbox, watches the build, and hands you a live preview link. All inference runs on your own subscription. Huxly only provides the infrastructure.

Plan requirement: AI Connector is available on Developer, Business, and Max plans. Free users can connect after upgrading at huxly.app/pricing.

---

Pair it with the Supabase MCP

Huxly's connector handles your app files, your backend, and deploys. It deliberately never reads your database.

Add Supabase's own MCP server alongside it and your AI gets both: it reads your real schema from Supabase while writing matching code through Huxly. Useful when building a backend, since it can see which tables already exist instead of inferring from migration files.

Both run at once — point your tool at Huxly's endpoint and Supabase's, and the AI picks whichever it needs.

---

How it works

There are two ways to connect, and the right one depends on your tool.

Sign in with Huxly (OAuth). Claude.ai and ChatGPT can install Huxly from their own directories. You click Connect, sign in to Huxly, approve access, and you're done — no key to generate, paste, or ever rotate. This is the easiest route and the one to use if your tool offers it.

API key. Every other MCP client — Claude Code, Cursor, Windsurf, Cline, Continue, Zed, Warp, Antigravity, Codex — authenticates with a Huxly API key you generate once and put in a config file.

The three endpoints, for reference:

Endpoint	Used by	Auth
https://huxly.app/api/mcp	Most MCP clients	Authorization: Bearer YOUR_API_KEY
https://huxly.app/api/mcp/stream	Codex — its transport is stricter	?key=YOUR_API_KEY
https://huxly.app/api/mcp/v2	Claude.ai and ChatGPT directory installs	OAuth

You only need to care about this if you're configuring a client by hand. The directory installs handle it for you.

---

Step 1 — Get your API key

Skip this if you're connecting Claude.ai or ChatGPT through their directories — those use OAuth and need no key.

1. Open Huxly Settings
2. Open the MCP tab
3. Click Generate API Key
4. Copy the key — it's shown once

Keep this key private. It has full access to all your Huxly projects.

---

Setup by tool

Claude.ai (browser, desktop, mobile)

Huxly is listed in Claude's Connectors Directory, so this is a one-click install with no API key.

1. Open Huxly in Claude's directory
2. Click Connect
3. Sign in to Huxly and approve access

Start a new conversation and ask Claude to list your Huxly projects. Works the same on Claude Desktop, mobile, and Cowork — connect once and it follows your account.

Claude Code is different. It runs its own sign-in on your machine and can't use the directory connector. Use the API key setup below.

Claude Code CLI

Add to your ~/.claude/claude_desktop_config.json (or claude_code_config.json):

{
  "mcpServers": {
    "huxly": {
      "type": "http",
      "url": "https://huxly.app/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Restart Claude Code. Run /mcp to verify the server connected.

Cursor

1. Open Cursor Settings → MCP
2. Click Add MCP Server
3. Set type to HTTP and paste:

{
  "huxly": {
    "type": "http",
    "url": "https://huxly.app/api/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_API_KEY"
    }
  }
}

Windsurf

In your Windsurf config file (~/.codeium/windsurf/mcp_settings.json):

{
  "mcpServers": {
    "huxly": {
      "serverUrl": "https://huxly.app/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Antigravity (Google AI Editor)

In ~/.gemini/config/mcp_config.json:

{
  "mcpServers": {
    "huxly": {
      "serverUrl": "https://huxly.app/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Codex (OpenAI)

Codex is OpenAI's agentic coding tool — the GPT-family equivalent of Claude Code. Its MCP transport is stricter than other clients, so it uses Huxly's dedicated Streamable HTTP endpoint: https://huxly.app/api/mcp/stream (note the /stream).

In the Codex app:

1. Open Codex → Settings → MCP → Add server
2. Choose Streamable HTTP as the server type, and name it huxly
3. Set the URL to (your key goes in the URL — leave bearer token and headers empty):

https://huxly.app/api/mcp/stream?key=YOUR_API_KEY

4. Save, then start a new conversation — run /mcp to confirm the Huxly tools loaded

In the Codex CLI (~/.codex/config.toml):

[mcp_servers.huxly]
url = "https://huxly.app/api/mcp/stream?key=YOUR_API_KEY"

Restart Codex and run /mcp to verify. If you see Transport channel closed, double-check you're on the /stream URL.

ChatGPT (Plus and above)

ChatGPT can build in Huxly directly — no Codex needed. There are two ways in.

Option A — sign in with Huxly (recommended)

1. Open ChatGPT → Settings → Security and turn on Developer mode
2. Go to the Plugins tab → click + for the New Plugin dialog
3. Name it Huxly and set the Server URL to:

https://huxly.app/api/mcp/v2

4. Set Authentication to OAuth, then sign in to Huxly and approve access

No API key to generate or paste, and you can revoke access from Huxly Settings at any time.

Option B — API key

If you'd rather not use OAuth, ChatGPT also works with a key in the URL:

1. Developer mode on, New Plugin, name it Huxly
2. Server URL:

https://huxly.app/api/mcp/stream?key=YOUR_API_KEY

3. Set Authentication to No Auth — the key in the URL is what authenticates you
4. Tick I understand and want to continue, then Create

Start a new chat and ask it to list your Huxly projects to confirm the tools loaded.

Why does Option B say No Auth? ChatGPT's plugin dialog can't send a custom Authorization header, so Huxly accepts the API key as a ?key= query parameter instead. It carries exactly the same access as a bearer token, so treat the whole URL as a secret — and prefer Option A, which avoids putting a credential in a URL at all.

---

What your AI can do

Tool	What it does
list_projects	List all your Huxly projects with framework and creation date
list_files	Get the full file tree for a project
read_file	Read any file in a project
search_files	Search across all files for a string or pattern
write_file	Create or fully replace a file
write_files	Create or replace multiple files in one call
edit_file	Make a surgical change — find exact text and replace it
delete_file	Delete a file
create_project	Create a new project (Expo, Flutter, or SwiftUI)
start_sandbox	Start the live preview sandbox for a project
update_sandbox	Push all current files to the running sandbox and wait for rebuild
get_build_logs	Get the current build status and any error output
get_runtime_logs	Get runtime logs from the running app
get_project_url	Get the Huxly dashboard URL for a project
get_conventions	Get coding conventions for a project's framework
get_figma_design	Pull design data from a connected Figma file
get_preview_screenshot	Take a screenshot of the live preview
exec_in_sandbox	Run a shell command inside the project sandbox

---

Typical workflow

Your AI can run this loop autonomously once connected:

1. list_projects → pick the target project
2. list_files → understand the structure
3. read_file on relevant files → understand the current code
4. write_file / edit_file → make the changes
5. update_sandbox → push and rebuild (returns the build log inline)
6. If build fails → read the log, fix, push again
7. get_project_url → return the preview link to you

You watch. The AI ships.

---

FAQ

Does this use my Huxly credits?

No. All AI inference happens on your own AI subscription (Claude, Cursor, ChatGPT, Codex, etc.). Huxly only provides the file storage, build pipeline, and sandbox — which are covered by your Huxly plan. Zero Huxly credits consumed per message.

What if I'm on the free plan?

The AI Connector is available on the Developer, Business, and Max plans — see huxly.app/pricing. Free users see an upgrade prompt in Settings.

Can I connect multiple AI tools at once?

Yes. For key-based tools, generate a separate API key for each one in Settings — each is independent, so revoking one doesn't affect the others. Claude.ai and ChatGPT connect with OAuth instead, and you revoke those from Settings too. The two kinds coexist fine on the same account.

Is my code safe?

Your API key grants full read/write access to all your Huxly projects. Treat it like a password — don't share it, don't commit it to git. You can revoke any key at any time from Settings.

What MCP protocol version does Huxly use?

2024-11-05. Compatible with all current MCP clients.

What if my AI tool isn't listed?

Any tool that supports the MCP HTTP transport works with Huxly — use the same url and Authorization: Bearer config. For strict clients like Codex, use the /api/mcp/stream endpoint instead, with ?key=YOUR_API_KEY on the URL.

Sign-in with Huxly currently works with Claude.ai and ChatGPT only, because each OAuth client is registered with us individually. Every other client uses an API key.