Build your backend without leaving your editor.
A coding agent runs commands all day. Instead of loading hundreds of tools into its context, it runs norbix like you do and reads one JSON answer per command. The MCP server stays there as the second way in.
norbix login → norbix ai init → norbix … --json --dry-run first, --yes only for destructive changes. Same commands in CI.https://hub.norbix.ai/v3/account/mcp The blocks below are the ones Cloud shows for the managed service. On your own installation Cloud fills in your own addresses.
In your project folder. --target cursor writes .cursor/rules/norbix.mdc.
npm i -g @norbix.ai/cli
norbix login
norbix ai init --target cursorCheck the code, pick the roles Cursor's agent gets, press Allow.
The rules file tells it to run norbix with --json, to --dry-run a change first and to add --yes only for destructive commands.
In the project, or in ~/.cursor/mcp.json for all projects.
{
"mcpServers": {
"norbix": {
"url": "https://hub.norbix.ai/v3/account/mcp"
}
}
}Cursor shows Needs login next to the server in its MCP settings. Click it and allow in the browser.
{
"mcpServers": {
"norbix": {
"url": "https://hub.norbix.ai/v3/account/mcp",
"headers": {
"Authorization": "Bearer ${env:NORBIX_API_KEY}"
}
}
}
}Cursor runs norbix whoami --json, then the read commands it needs, and answers from the JSON. Ask for a change and it shows you the --dry-run request first. With Viewer, the change is refused by the server; with Administrator, it goes through.
Create a taxonomy called Publishers in my Norbix project.
Create a project, enable modules, build collections from a schema bundle and publish them.
Find, count, insert and update records; taxonomies, aggregates and triggers on every collection.
Email, push, SMS and payment providers; templates, campaigns, files and storage.
Roles and policies, sign-in integrations, invitations and the membership settings.
Triggers across modules, scheduler tasks, serverless code functions and webhooks.
Logs by correlation id, diagnostics, usage — the same read-only look Cloud gives you.
Sign-in happens in your browser. You tick the projects and roles the agent gets — Viewer, Developer, Data Editor, Administrator or your own.
The CLI acts as an AI service user named after your computer. Remove it in Cloud and the agent is signed out.
The agent runs --dry-run first and shows the exact request. Destructive commands refuse to run without --yes.
Every call the agent makes is in Logs with its correlation id, like any other request.
Open your avatar → Connect your AI in Cloud. It holds a prompt you can paste into any AI tool, the Hub, API and MCP addresses of your installation, and one tab per tool with the exact commands — including the key variants for CI.
Copy-paste setup for every tool, a first prompt and what it returns.
norbix login, norbix ai init, and when to choose the CLI or MCP.
The address, OAuth or a key, the consent screen, roles and environments.
Every tool group per module, which ones read, change, or ask first.
Create a free account, connect Cursor, and ask it for your first backend change.