Rimbra

app.rimbraPublished by rimbra.appOfficial publisherv1.0.0Updated Oct 30, 2026

Deploy apps, run databases and domains, read logs, and send email and WhatsApp messages on Rimbra.

VerifiedStreamable HTTPWeb executableDatabases Cloud & Infrastructure Communication & Collaboration

Server details

Identifier: app.rimbra/rimbra
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 23, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to rimbra.app, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/app.rimbra%2Frimbra.svg)](https://sourceweft.com/mcp/app.rimbra%2Frimbra?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Rimbra connects an assistant to a Rimbra workspace to deploy apps, manage databases and domains, read logs, and send email or WhatsApp messages.

What you can do: Deploy and host apps from GitHub through the Rimbra workspace
Manage managed PostgreSQL, MySQL and Redis databases
Set up domains with automatic HTTPS
Read logs for deployed services
Send email through the Email API and WhatsApp messages via Social notifications
Work in Developer mode (can deploy) or Viewer mode (read only)
When to use it: Useful when you host projects on Rimbra and want an assistant to deploy from GitHub, inspect databases, check logs, or send notifications without leaving the chat. Also fits teams that want a read-only view of a Rimbra workspace.
Requirements: Remote MCP endpoint at app.rimbra.app over streamable HTTP. A Rimbra account and workspace; sign-in via OAuth (the /mcp flow) or an API key created in Rimbra under MCP, passed as an Authorization Bearer header. A workspace and a Developer or Viewer role must be chosen.

Before you install

Developer mode lets the assistant deploy and change hosted apps, databases and domains, so pick Viewer if you only want read access. An API key grants access to the workspace and should be kept secret. Sending email and WhatsApp messages acts on your behalf and may incur usage or billing on your Rimbra plan.

Installation

In SourceWeft

Open Rimbra in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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/app.rimbra%2Frimbra/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "rimbra": {
      "type": "http",
      "url": "https://app.rimbra.app/mcp"
    }
  }
}

README

Rimbra for Claude Code

Connects Claude Code to your Rimbra workspace and teaches it how Rimbra works.

The first time Claude uses Rimbra, run /mcp and sign in. Pick the workspace and whether Claude may deploy (Developer) or only read (Viewer).

Prefer a key? Make one in Rimbra → MCP and run:

claude mcp add --transport http rimbra https://app.rimbra.app/mcp --header "Authorization: Bearer YOUR_KEY"

claude mcp add --transport http rimbra https://app.rimbra.app/mcp --header "Authorization: Bearer YOUR_KEY"

Docs: https://rimbra.app/docs/mcp

What is Rimbra?

Rimbra puts a product on the internet from one account: app hosting from GitHub, managed PostgreSQL, MySQL and Redis, domains with automatic HTTPS, an Email API and Social notifications for WhatsApp messages. One dashboard, one bill, and a free plan to start.

Source: README.md at commit 0e92947

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestOct 23, 2026

Score

85% 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
Auth declaredRequired10 pts
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