
Appbricx
com.appbricxPublished by appbricx.comOfficial publisherv1.0.0Updated Oct 24, 2026
Build, verify and deploy full-stack apps: Postgres, sign-in, workflows, realtime, AI, rollback.
Overview
Lets a coding agent build, verify and deploy full-stack apps on Appbricx, including Postgres databases, sign-in, workflows, realtime and rollback.
- What you can do
- Appbricx is a remote MCP endpoint that connects a coding agent to the Appbricx platform so it can build and run full-stack apps. The platform supplies a Postgres database per project with separate dev and prod databases, per-role access enforced by the database, sign-in, workflows, realtime, in-app AI, payments, releases tested as every user, and one-click rollback. Agents can find and apply templates with the search_templates, get_template and use_template tools, and a companion CLI handles login, check, apply, verify, deploy, SQL, row edits and snapshots.
- When to use it
- Worth adding when you want an assistant to scaffold, verify and deploy a hosted full-stack application rather than only write code locally. It suits teams that want managed Postgres, authentication, workflows and payments wired in, and who prefer starting from the provided templates and blocks.
- Requirements
- A remote MCP endpoint at added over streamable HTTP. Authentication is interactive: browser sign-in, or a token header for the Cursor config. The optional CLI is installed from the examples repository with npm link and also logs in through the browser. No environment variables are declared.
Installation
In SourceWeft
- Open Appbricx in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.appbricx%2Fappbricx/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"appbricx": {
"type": "http",
"url": "https://www.appbricx.com/api/mcp"
}
}
}README
Appbricx examples and tools
Everything you need to build on Appbricx from your own machine: a complete example app, ten app templates, the Claude Code plugin, the CLI, a Cursor config and the HyperFrames templates behind our demo videos.
Your coding agent builds the app; Appbricx runs it: Postgres per project with separate dev and prod databases, per-role access enforced by the database, sign-in, workflows, realtime, in-app AI, payments, releases tested as every user, and one-click rollback.
Connect your coding agent
Claude.ai and Claude Desktop: Appbricx is in Claude's connectors directory: https://claude.ai/directory/appbricx (choose Connect, then sign in).
Then ask your agent to build something. Agents can also find these templates themselves with the search_templates, get_template and use_template tools, or browse them at https://www.appbricx.com/templates. The format is in TEMPLATE_FORMAT.md.
Use the CLI
Docs
- Quickstart with a coding agent
- Guides for every feature
- Reference: SDK, HTTP API, MCP tools, CLI, integrations
License
The contents of this repository are MIT licensed (see LICENSE). The Appbricx platform itself is covered by the Appbricx Self-Hosted License; see pricing.
Source: README.md at commit 353ac02
Tools
0Version history
1- v1.0.0LatestOct 13, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts