One settings block, one /mcp auth.
Every Norbix installation is an MCP server — the hosted address below, nothing to install. The tool signs in with OAuth in your browser and gets described tools marked read or change.
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.
httpUrl means Streamable HTTP. Gemini loads MCP servers only in a trusted folder.
{
"mcpServers": {
"norbix": {
"httpUrl": "https://hub.norbix.ai/v3/account/mcp"
}
}
} /mcp auth norbix Inside Gemini CLI. Allow in the browser; gemini mcp list then shows norbix as Connected.
npm i -g @norbix.ai/cli
norbix login
norbix ai init --target agents {
"mcpServers": {
"norbix": {
"httpUrl": "https://hub.norbix.ai/v3/account/mcp",
"headers": {
"Authorization": "Bearer $NORBIX_API_KEY"
}
}
}
} Gemini CLI calls a read tool, for example get_database_taxonomies, and turns the JSON into a list. Ask for a change and the tool either goes through (Administrator) or answers "Caller is missing required permission" (Viewer).
How many users does my Norbix project have, and which roles do they hold?
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.
OAuth opens Cloud's consent screen. You tick the projects and roles the tool gets — Viewer, Developer, Data Editor, Administrator or your own.
The tool acts as an AI service user. Remove it under Account → AI service users and it is signed out.
Every tool is marked read or change. Tools that send messages, delete or change a lot answer requires_confirmation first.
Every call the tool 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.
The address, OAuth or a key, the consent screen, roles and environments.
norbix login, norbix ai init, and when to choose the CLI or MCP.
Every tool group per module, which ones read, change, or ask first.
Create a free account, connect Gemini CLI, and ask it for your first backend change.