Appbricx

What the Appbricx MCP server does

The Appbricx MCP server gives coding agents an interface to the Appbricx application platform. Appbricx projects can use a separate development and production Postgres database, database-enforced role access, sign-in, workflows, realtime features, in-app AI, payments, releases tested for each user, and rollback. The repository supplies examples and supporting tools rather than functioning only as a database connector.

Agents can discover reusable application starting points through search_templates, inspect a selected template with get_template, and apply one with use_template. The repository includes ten showcase app contracts, a studio-bookings example, feature blocks for organisations, teams, subscriptions, payments, booking calendars, comments, and notifications, plus reusable workflow definitions.

How it works

The MCP endpoint is exposed at https://www.appbricx.com/api/mcp. Claude Code can add it with an HTTP transport and then authenticate through the /mcp menu; authentication opens a browser. Appbricx is also listed as a connector for Claude.ai and Claude Desktop. A Cursor configuration is included in the repository, with browser sign-in or a token-header option described by the project materials.

The repository separates agent connectivity from local project utilities. The cli directory contains the appbricx command, which can log in, create projects, check and apply app definitions, verify and deploy, run SQL, edit rows, and take snapshots. The examples and templates give agents concrete application structures to adapt.

Setup and configuration

Clone the repository when you need the examples, templates, CLI, plugin, or client configuration. To put the CLI on your path, enter cli and run npm link, then use appbricx login; the login flow opens a browser for authorization. A project can then be created and populated from a template, such as the Kanbo app definition.

For Claude Code, add the HTTP MCP endpoint with the documented claude mcp add --transport http command, or install the repository’s Claude Code plugin. The plugin also adds a skill. Cursor users can use the configuration under cursor/. The repository also contains a Gemini CLI extension installation URL, although the provided instructions do not describe that extension as a separate MCP connection procedure.

Tools and capabilities

The Appbricx MCP server supports template discovery and reuse through these documented tools:

• search_templates finds available templates.
• get_template retrieves a template.
• use_template applies a template.

The repository’s adjacent CLI adds project and deployment operations, including checks, verification, deployment, SQL execution, row editing, and snapshots. Included workflows cover events such as welcome messages, signup notifications, booking confirmations and reminders, payment receipt, daily digests, overdue alerts, and reply-deadline escalation.

Limitations and notes

The Appbricx MCP server is documented as part of a broader Appbricx repository containing examples, templates, plugins, client setup, and a CLI. The supplied material does not provide a complete MCP tool catalog, detailed request schemas, token names, or operational limits. Repository contents are MIT licensed, while the Appbricx platform itself uses the Appbricx Self-Hosted License.