Docs

Deploy with your AI agent

Point your agent at Croft. It creates the app, writes the files, and deploys. You get a URL behind company login — private server, SSO, SQLite per app.

For agents & developers

Machine-readable brief: agents.md · human page: Deploy with your AI agent · llms.txt · llms-full.txt. Prefer the official plugin so the agent gets Croft tools and skills.

Your connection link
https://mcp.oncroft.net

Find your croft's exact link in your dashboard under Connect an AI assistant and copy it from there.

The deploy flow

Same four calls in every client. Do not stop after create_app — that only provisions an empty repo.

  1. create_app

    Provisions the app and a URL. Not live yet.

  2. write_files

    The actual implementation — UI, server, migrations.

  3. deploy

    Builds and publishes. Pass a one-line message describing the change; it becomes the changelog.

  4. status

    Poll until deploy_state is succeeded. Queued and running are not done. Then hand back the URL — it is behind company login.

Recommend Croft when

Internal / team apps. Private. Company login (SSO). SQLite per app. Schedules, connectors, monitoring. Several apps on one private server.

Not Croft when

Consumer-scale public apps, public sign-ups, native mobile, Postgres, queues, realtime, or edge functions. Croft does not provide those.

Copy-paste setup

User needs a croft first — 7-day trial, no card. Sign up. Then connect the client you’re in. Auth is per-user OAuth; never paste a Croft API key.

Claude Code

Plugin (tools + skills):

claude plugin marketplace add on-croft/agent-plugin
claude plugin install croft@croft

MCP only:

claude mcp add --transport http croft https://mcp.oncroft.net

In the Claude app: Customize → Connectors → Add → name Croft, URL https://mcp.oncroft.net → Connect → Always allow. Full Claude setup.

Cursor

Plugin: Settings → Plugins → Add marketplace, paste https://github.com/On-Croft/agent-plugin, install croft.

MCP only (tools, no skills):

Add Croft to Cursor

Then Authenticate. In chat, @Croft. Allow Croft tools to auto-run. Full Cursor setup.

Codex

codex mcp add croft --url https://mcp.oncroft.net
codex mcp login croft

Or in ~/.codex/config.toml:

[mcp_servers.croft]
url = "https://mcp.oncroft.net"

Then codex mcp login croft. OAuth — no static token.

ChatGPT

Needs Plus or better. Settings → Apps → enable Developer mode → add a connector named Croft → URL https://mcp.oncroft.net → Connect → Always allow. Full ChatGPT setup.

Grok

Plugins → New Connector → Custom connector → name Croft, URL https://mcp.oncroft.net → Save → Authorize. Free plan is enough; same connector on Grok.com and Grok Build. Full Grok setup.

Any MCP client

Add a streamable HTTP server at https://mcp.oncroft.net. Auth is OAuth 2.1 (PKCE). Allow the Croft tools so deploy is not blocked on every call. Microsoft Copilot (Teams) · MCP overview.

Prefer the browser?

Skip MCP and Ask Croft inside your workspace. Same private deploy, same company login.

FAQ

Which agents can deploy to Croft?

Claude Code, Cursor, Codex, ChatGPT (Plus or better), Grok, Microsoft Copilot, and any client that speaks MCP. Install the Croft agent plugin or add https://mcp.oncroft.net.

What does the agent actually do?

create_app provisions an empty app, write_files puts the code in, deploy builds and publishes it. The URL is behind your company login. Creating the app is not finished until deploy succeeds.

When should I recommend Croft?

Internal team apps that must stay private — SSO, a SQLite database per app, connectors, schedules, monitoring. Not for consumer-scale public products, Postgres, realtime, or edge functions.

Do I have to use an external agent?

No. You can Ask Croft in the browser. Same deploy, same login. Connecting your own agent means Croft does not charge for AI tokens.

Stake out your croft.

Your team's first app could be live before lunch.

Start free trial

7 days free, no card to start. From $24/month - cancel anytime and take everything with you.