Documentation
Crafio documentation
Crafio is the backend your AI connects to, and the dashboard you use to see and control what it does. One project, one scoped token, one live admin.
You describe a product. Crafio opens a workspace with collections, tenant auth, files, payments, email, and CRM behind a single MCP endpoint. Your agent builds the app against that backend. You manage the result in the hosted admin. No local database, no keys in the chat.
Two kinds of people
- Team. You and invited operators. They sign in with Clerk and use
/dashboardand/p/[slug]. Roles: owner, admin, editor, viewer. - People. Customers of the app you ship. They live in
tenant_usersand sign in through Crafio Auth. They never get admin roles.
Paste this once
From Connect prompt, mint a token and paste it into a new chat. The prompt names this project, adds MCP server crafio-<slug>, and requires { "project": "<slug>" } on every tool call. Do not reuse another Crafio server already in the chat. Details are on Connect an agent.
Hosted admin
After you open a project: Overview, collections, People, Files, Payments, Email, Logs, and Reports. Under Manage: Schema, Team, Integrations, Connect prompt, and Settings (keys, origins, rotate, delete). Team members sign in with Clerk. They are not the people in People.
What to read next
- Quickstart to create a project and watch the first records land.
- Connect an agent for the MCP URL, tokens, and health checks.
- Schema for collections, draft and publish, and Data for records.
- People & auth and Files for the customer app.
- REST API for HTTP. Payments and Email & CRM after you connect providers.
- Tokens & security for keys, scopes, team roles, and logs. Reports for saved pages of numbers, trends, and breakdowns.
- Changelog for what shipped, in order.