For the complete documentation index, see llms.txt. This page is also available as Markdown.

Norbix + AI

Norbix is an MCP-native backend. Build with AI agents, ship to production.

Project β†’ Integrations β€” connect LLM providers and MCP servers to your project.

Norbix is an MCP-native Backend-as-a-Service. That means AI tools are not an add-on β€” they are a first-class way to work with your backend, next to the SDKs and the REST API.

There are two moments where AI meets Norbix:

Build time β€” your agent becomes your backend engineer. Connect Claude Code, Cursor, Windsurf, or any MCP-compatible tool, and let it scaffold database schemas, configure providers, wire events, and deploy modules. Because Norbix already enforces auth, schemas, audit, and permissions, what your agent produces is production-ready β€” not a prototype that needs a month of hardening.

Runtime β€” your shipped app talks to the same backend. The agents and workflows you ship (LangGraph, LangChain, CrewAI, n8n, and others) call the same Norbix through MCP, SDKs, or REST. One platform, one API, one event bus, same permissions, same audit trail.

What is in this section

MCP ServerConnect Your AI ToolFramework Integrations

How access control works with AI

The MCP server can do exactly what its API key can do β€” nothing more. You create a service user in Membership, give it a role, and issue an API key. Want an agent that can only read? Give it a read-only role. Everything the agent does is visible in Logs & Monitoring.

Last updated