If you already code with Claude Code, Codex or Cursor, you don't have to choose between your editor and FluxNative. With MCP, your coding agent can work on your FluxNative apps directly.

Your agent edits the code. FluxNative gives you the live preview, the connections, the native builds and publishing. Here's how the two fit together.

Key takeaways

MCP lets an AI coding tool use another service's tools. FluxNative runs a remote MCP server for your apps.
One account connection lets your agent find, create and edit any app you can edit.
Every change your agent makes is a revision you can undo in FluxNative.
Keys stay in Connections. Builds and store releases stay in the builder.
Remote MCP comes with the Creator plan and above.

A coding agent in Claude Code, Codex or Cursor connects over MCP to a FluxNative project, where it reads and edits the source, runs checks and uses the live preview. — Your coding agent talks to FluxNative over MCP and works on the same project you see in the builder.

What is MCP?

MCP stands for Model Context Protocol. It's an open standard that lets an AI coding tool use tools from another service.

FluxNative's MCP server gives your agent tools to read and change an app's code, run checks and use the live preview. Your agent works on the same project you see in the builder, not on a copy.

Account or project connection?

Click MCP in the project bar and FluxNative offers both kinds of connection:

All apps, the account connection (https://mcp.fluxnative.app/mcp). Your agent can list, create and edit every app and landing page you can edit. Each request names the project it works on. Add it once, and it covers new projects too.
Only this app, a project connection (the same URL, ending in ?project= and the project's id). Your agent works on that one app only. Use it when an agent should stay on one project.

The Connect your editor window in two states: All apps, with the MCP URL https://mcp.fluxnative.app/mcp; and Only this app, with a project MCP URL that ends in ?project= and the app's id. — MCP in the project bar: All apps gives one connection for every app you can edit; Only this app keeps an agent on one project.

Connect your editor in four steps

In FluxNative, open Settings, then Editors. Or open a project and click MCP in the project bar.
Copy the MCP URL.
Pick your editor's tab (Codex, Claude Code, opencode, Cursor, VS Code or Antigravity) and follow its setup. It's one terminal command or a config file to paste.
Finish the FluxNative sign-in that your editor opens.

In Claude Code, for example, it's one command. Then you sign in from /mcp:

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

Settings, Editors: the MCP URL with a Copy button, tabs for Codex, Claude Code, opencode, Cursor, VS Code and Antigravity, and the one-line Claude Code command. — Settings, then Editors: copy the URL, pick your editor, run its command, then sign in when it asks.

No browser available? For a script, or an editor that can't open a sign-in page, create a connection key under Settings, then Editors. It's shown once and lasts one year. Keep it in the FLUXNATIVE_MCP_KEY environment variable, never in a file you commit.

A simple way to split the work

Let your agent do the code work: changes across many files, refactors and new features. Use FluxNative to check the result: the preview, the connections, the builds and the releases.

A good loop looks like this:

Ask your agent for one clear change.
The change lands in FluxNative as a revision.
Check it in the live preview.
Keep it, or press Undo and try again.

Avoid having your agent and a FluxNative chat change the same part of the app at the same time.

A loop of four steps: ask your agent for one change, the change lands as a revision, check it in the live preview, then keep it or undo it. — Ask for one change, let it land as a revision, check the preview, then keep it or undo it.

What stays in FluxNative

Some things stay in the builder on purpose:

Saving keys and secrets, under Connections.
Creating connection keys.
Native builds, store uploads, review and release.
Registering an Android signing key you already have.

Your agent never sees your secret values. When it needs one, it asks you to add it in Connections.

Two columns. Your agent can read and change the code, upload images and fonts, run checks and use the preview, and use your backend's tools. Keys and secrets, connection keys, builds, uploads and releases, and registering a signing key stay in the builder. — Your agent works on the code. Secrets, builds and store releases stay in the builder.

Teams and permissions

The connection uses your own FluxNative sign-in, and every request is checked against your current permissions. So an agent can only reach the apps you can edit. If you lose access to a project, the agent loses it on its next request.

Teams use four roles: owner, admin, developer and viewer. Developers and viewers can be limited to selected apps.

Frequently asked questions

Can my coding agent see my API keys?

No. Secrets saved in Connections are never shown to the editor. When the agent needs a key, it asks you to add it in Connections.

Do changes from Claude Code show up in FluxNative?

Yes. The agent edits the same project, and each change lands as a revision you can review and undo in FluxNative.

Which plans include MCP?

Remote MCP comes with the Creator plan and above. The Free plan doesn't include it.

Keep exploring

Connect an editor — Setup for Claude Code, Codex, Cursor, VS Code and more.
Organizations and roles — Who can build, publish and edit which apps.
Bring an existing React Native project — Move an app you already have into FluxNative.

Build a Mobile App With Claude Code or Cursor Through MCP