Koskamo

Appbricx MCP

The Appbricx MCP server allows coding agents to interact with the Appbricx platform to build, verify, and deploy full-stack applications. It enables agents to create projects, manage data tables, handle user authentication, execute workflows, and perform rollbacks. The server supports OAuth 2.1 authorization and provides tools for reading contracts, listing projects, and applying changes, effectively mirroring the functionality of the developer HTTP API and CLI within an MCP client environment.

Visit Appbricx

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Appbricx MCP logo, by AppbricxVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-10-26Operated by Appbricx
You need:Add the URL to your client with no token; the first time it connects it opens a browser window where you sign in, check the workspace and the permissions, and click AuthorizeWhere no browser can open, send a personal access token as Authorization: Bearer apx_pat_…Scopes: read , apply , deploy . You choose them on the authorize page
MCP endpoint (Streamable HTTP)
https://www.appbricx.com/api/mcp
Vendor documentation

What you can do with it

  • Create and manage Appbricx projects via coding agents
  • Read and modify application data tables and schemas
  • Deploy applications and manage rollbacks
  • Execute workflows and manage user sign-in

Source and maintenance

Vendor evidenceRegistry 1.0.0MIT
mcp-registry: com.appbricx/appbricx@1.0.0Source repositoryProject website
Last repository push
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · repository · passed · metadata changed · unchanged
  • · repository · passed · metadata changed · updated
  • · registry · passed · metadata changed · Source metadata updated
  • · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http appbricx-mcp https://www.appbricx.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add appbricx-mcp --url https://www.appbricx.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable appbricx-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "appbricx-mcp": {
      "url": "https://www.appbricx.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "appbricx-mcp": {
      "type": "streamableHttp",
      "url": "https://www.appbricx.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start appbricx-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "appbricx-mcp": {
      "type": "http",
      "url": "https://www.appbricx.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http appbricx-mcp https://www.appbricx.com/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "appbricx-mcp": {
      "url": "https://www.appbricx.com/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "appbricx-mcp": {
      "serverUrl": "https://www.appbricx.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Appbricx MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,473

Do you run Appbricx MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing