Claude and Orbit

Build with Claude. Launch on Orbit.

Connect Orbit to Claude, and it can build the full app: screens, data, backend logic, and launch. You get a hosted app, not a repo you still need to deploy yourself.

Your Claude subscription does the AI work.

Claude connector setup

Connect Orbit to Claude in two fields

01

Click Connect Orbit to Claude to open Claude's custom connector settings.

02

Add a custom connector named Orbit MCP with the URL below.

https://mcp.orbitapps.io/mcp
Claude custom connector dialog with Orbit MCP and the Orbit MCP endpoint filled in
Claude connector settings showing Orbit MCP connected with tool permissions

The tool surface

Forty-four tools, and one thing they will not do

The connector puts forty-four Orbit tools in front of Claude. Every name reads action first, then noun, so the list itself tells you what it can reach. Four jobs cover almost everything you will ask for.

01

Read the app

orbit_list_apps and orbit_get_app find the app. orbit_get_workspace reads one screen node by node. orbit_get_app_theme returns your colour and font tokens, so a new screen matches the ones you already have. orbit_preview_app screenshots the app as it is authored, before any deploy, so Claude can look at what it just made.

02

Change the app

orbit_edit_nodes does the work: one atomic batch of nodes, where a single bad row fails the whole batch instead of leaving you half a screen. orbit_search_blocks and orbit_search_recipes find the parts to compose from. orbit_search_images returns a photo together with the attribution its licence requires.

03

Run it

orbit_create_run starts a workflow. A workflow is server-side logic that writes to your data and calls the services your app is connected to, so a run has real effects. orbit_get_run_events follows it as it goes. orbit_cancel_run stops it, and whatever it already wrote stays written.

04

Put it live

orbit_create_deployment puts the app online at its URL and returns before the deploy has finished, so orbit_get_deployment is how you learn the outcome and orbit_get_deployment_logs is how you read a failure. orbit_stop_deployment takes it offline and clears the address. orbit_get_wallet reads the balance a paid tier draws on.

Claude drives Orbit. It still writes no file.

An Orbit app is composed from parts that already run: a database, integrations, and the UI elements a screen is made of. Claude chooses the parts and wires them. Nothing is written to a file, and there is no escape hatch to one. Ask Claude Code for a custom React component and you get one. Ask for it through this connector and you do not.

Questions, answered

Do I need the Orbit CLI for this?

No. Add Orbit MCP as a custom connector with the endpoint on this page.

Does Orbit charge for Claude's work?

No. Your Claude subscription does the AI work, and Orbit charges nothing for it.

Can I use Claude Code too?

Yes. Add the same Orbit endpoint to Claude Code as a remote HTTP MCP server.

Where does the app run?

On Orbit, with a Postgres backend, sign-in, and your own domain. Your first live app is free.

What is left for me to do?

Judge the result. You review the screens and the data, rename what reads wrong, and decide when it ships.

Finish the app, not the setup

The next thing you build with Claude can be live by the end of the conversation.

Your Claude subscription does the AI work.

Créé avec Orbit