Connect an editor

Connect Claude Code, the Claude app, Codex, Cursor, VS Code, opencode or Antigravity over MCP to find, create and edit your apps and landing pages.

Updated Oct 19, 2026

Connect your editor: All apps selected, the MCP URL with Copy, and the editor tabs with Codex's command to run — Copy the MCP URL, pick your editor, paste its command, then approve the sign-in.

Steps

Open Settings › Editors, or click MCP in a project's bar.
Copy the MCP URL, with All apps selected.
Pick your editor's tab and paste its command or config.
Approve the sign-in your editor opens, or use a connection key.
Ask for an app by name: the agent finds it with list_apps or makes one with create_app.

claude mcp add --transport http "fluxnative" --scope user "https://mcp.fluxnative.app/mcp"

Codex, Cursor, VS Code, opencode and Antigravity each have their tab; in the Claude app, use Connectors › Add custom connector.

Two connections

Connection	URL	Reaches
All apps	`https://mcp.fluxnative.app/mcp`	Every app and landing page you can edit (43 tools)
Only this app	`https://mcp.fluxnative.app/mcp?project=<id>`	One project (20 tools on an app plus its backends', 15 on a landing page)

Connection keys

For a script or CI, click Create connection key under Settings › Editors: pick all apps or one app, and Source only (no backend tools) when it needs no backend. Confirm with your password and two-factor code, copy the key (shown once), and follow its setup.

What an editor can undo

Source changes are versions you can undo. Backend tools act as the owner (Supabase SQL ignores row-level security): their changes, and taps in the live preview, change live data for good. For an outside tool, use Only this app with a Source only key.

In FluxNative Desktop 0.5.1 and later, auto-approve runs reads, previews and source edits; backend changes, preview taps (from 0.5.4, only in an app that talks to a server), and the agent's own commands and file changes on your computer always ask. Older versions approved backend changes too, so FluxNative refuses those from them until you update.

Good to know

Keys last one year (50 per account); browser sign-ins end after 30 days unused. A password change or Sign out others ends every key. Never put one in a URL, chat or commit.
Requests in flight: 6 on Creator, 12 on Pro, 30 on Business. Uploads: 10 MB on Creator, 25 MB above.
The tools spend no credits; builds, store uploads and secrets stay in the builder. Team › Activity lists editor sessions.

Edit the source · Organizations and roles

Did this page help?