Serveur MCP Rowbit
Commit 7 nov. 2026Fournit un filet de sécurité pour les agents IA en permettant aux utilisateurs de prévisualiser, d'approuver et d'annuler les écritures sur les bases de données MariaDB et MySQL.
Aussi connu sous Ermag/rowbit
- Étoiles
- 1
- Outils
- —
- Téléchargements, 30 jours
- —
- Dernière version
- 0.2.2
- Dernier commit
- 7 nov. 2026
- Licence
- AGPL-3.0
Qu'est-ce que Rowbit MCP ?
Fournit un filet de sécurité pour les agents IA en permettant aux utilisateurs de prévisualiser, d'approuver et d'annuler les écritures sur les bases de données MariaDB et MySQL.
Résumé généré à partir du README du projet
À propos du MCP server Rowbit
Rowbit agit comme un intermédiaire protecteur entre les agents IA et vos bases de données, prenant spécifiquement en charge MariaDB et MySQL. Il empêche la perte accidentelle de données en interceptant les opérations d'écriture via le Model Context Protocol. Au lieu que les agents se connectent directement à votre base de données, ils communiquent avec Rowbit, ce qui permet aux utilisateurs de prévisualiser exactement quelles lignes seront affectées par une commande avant que les changements ne soient validés.
Cet outil est conçu pour les développeurs utilisant des assistants de codage IA tels que Claude Code, Cursor, VS Code ou Windsurf. Il utilise un système de politiques basé sur YAML pour automatiser la sécurité, permettant aux mises à jour mineures ou prédéfinies de passer, tout en bloquant les opérations risquées pour une approbation humaine via une interface web. Si une erreur survient, le système permet d'annuler une modification spécifique en restaurant l'état original des lignes concernées sans nécessiter une restauration complète de la sauvegarde de la base de données.
Ce que vous pouvez faire avec
- 1Prévisualiser les changements de lignes en base de donnéesUn agent IA peut vous montrer exactement à quoi ressembleront les données avant et après l'application d'une mise à jour.
- 2Automatiser les corrections de données sécuriséesVous pouvez définir des règles permettant aux agents d'effectuer des mises à jour mineures automatiquement tout en bloquant les commandes dangereuses.
- 3Annuler les écritures accidentelles d'un agentSi un agent exécute une commande qui modifie trop de lignes, vous pouvez effectuer un rollback de cette transaction spécifique.
- 4Restreindre les permissions de l'agentVous pouvez limiter les tables ou les colonnes auxquelles un agent est autorisé à accéder ou à modifier.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer Rowbit MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller Rowbit MCP dans Claude Code
$ claude mcp add rowbit -- docker run -i --rm ghcr.io/ermag/rowbit:0.2.2Installer Rowbit MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"rowbit": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ermag/rowbit:0.2.2"
]
}
}
}Installer Rowbit MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"rowbit": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ermag/rowbit:0.2.2"
]
}
}
}Installer Rowbit MCP dans VS Code CLI
$ code --add-mcp '{"name":"rowbit","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/ermag/rowbit:0.2.2"]}'Installer Rowbit MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"rowbit": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ermag/rowbit:0.2.2"
]
}
}
}Installer Rowbit MCP dans Codex
$ codex mcp add rowbit -- docker run -i --rm ghcr.io/ermag/rowbit:0.2.2Installer Rowbit MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.rowbit] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/ermag/rowbit:0.2.2"]
Installer Rowbit MCP dans Gemini CLI
$ gemini mcp add -s user rowbit docker -- run -i --rm ghcr.io/ermag/rowbit:0.2.2Installer Rowbit MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"rowbit": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ermag/rowbit:0.2.2"
]
}
}
}Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →Pas encore vérifié. Un serveur nécessite un score de 80, aucune faille sérieuse et suffisamment de données pour que nous puissions effectuer les vérifications. Fonctionnement des vérifications · Ce qu'il faut corriger pour gagner des points
- Dépôt source lié et accessibleermag/rowbit is public and reachablegithub.com/ermag/rowbit ↗Réussi
- Le nom du package correspond au dépôt sourceNon vérifié
- Provenance du build (attestation Sigstore)Non vérifié
- Licence open source (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-11-07github.com/ermag/rowbit ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNon vérifié
- Aucun avis critique dans le package ou ses dépendancesNon vérifié
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHubRowbit
A safety net for AI agents that write to your database. Preview every write, approve the risky ones, undo any single change. MariaDB and MySQL, over MCP.
Get started
curl -fsSL https://ermag.github.io/rowbit/install.sh | sh
rowbit setup
macOS and Linux (Windows through WSL). If ~/.local/bin isn't on your PATH, the installer says so: run ~/.local/bin/rowbit setup instead. Setup finds your database's URL, checks Rowbit's privileges and prints the GRANT statements to fix them, writes rules that hold every write for review, connects the agent clients you pick, and prints the review page's password. See the quickstart.
No database to try it on? Choose the sample when setup asks: it runs a shop database in Docker with Rowbit in front of it (the tour). Then ask the agent:
The pending orders are stuck. Cancel them.
Works with Claude Code, Cursor, VS Code, Claude Desktop, Codex, Gemini CLI, Windsurf and any MCP client.
| Database | Status |
|---|---|
| MariaDB, MySQL | Supported, over TLS too (MariaDB 11.4 and MySQL 8.4 tested on every change) |
| PostgreSQL | Planned, next |
| MongoDB, Redis | Exploring |
Docs · Quickstart · Interactive demo · Tell us what you think
What it does
You ask a coding agent to fix the orders stuck in pending, and it writes UPDATE shop.orders SET status = 'cancelled' WHERE status = 'pending'. That also matches every order placed in the last hour. Rowbit catches it before it touches a row, shows a person exactly which 1,284 rows would change, and waits. If something bad does get through, you undo that one change without restoring a backup.
Status: early and open source; see the changelog for each release. What we build next depends on what you tell us in the feedback discussion.
How it works
Rowbit sits between your agents and your database. Agents talk to Rowbit over MCP, never to the database directly: they read and propose writes through it, without the database's credentials.
- Exact preview. Rowbit reads the rows a write would change and replays it on a private temporary copy, so you see each row before and after, exactly as the table would store it. Your tables are only read.
- Rules, then people. A small YAML file lets safe writes through, holds risky ones for a person, and refuses the rest. Only people approve, and approval applies exactly what was previewed, or nothing. See rules.
- Undo one change. Rowbit keeps every row a change touched, so you can take back one bad write and keep everything else.
- Scopes and shadow mode. Per agent, which tables it may read or write and which columns it may never see, enforced by the database with a user of the agent's own. Shadow mode shows what the rules would hold before you enforce them.
- Review where you are. A web UI in the binary, sign-in through your identity provider, Slack or webhook notifications, and an audit log in a hash chain. See how a change moves.
# rowbit.yml
version: 0
agents:
coding-agent:
default: hold
rules:
- name: small-order-fixes
when: { statement: update, table: shop.orders, columns: status, rows: { max: 20 } }
then: allow
- name: no-deletes
when: { statement: delete }
then: block
reason: Data fixes don't delete rows.
Here the agent can change the status of up to 20 orders on its own. An update that writes any other column, or more rows, waits for a person, and deletes are refused.
See examples/rowbit.yml and the rowbit.yml spec for the full schema.
Connect your agent
rowbit setup connects the clients you pick. rowbit connect <client> sets up one more, with a token of the agent's own. See Connect your agent.
rowbit connect claude-code
Adds Rowbit with claude mcp add, for this directory (--scope user for everywhere). Add the skill that teaches the agent to use Rowbit well:
/plugin marketplace add Ermag/rowbit
/plugin install rowbit@rowbit
rowbit connect cursor
Adds Rowbit to ~/.cursor/mcp.json. Restart Cursor.
rowbit connect vscode
Or, with rowbit demo or rowbit serve running, add it to VS Code and paste the token from rowbit connect vscode --print when VS Code asks.
rowbit connect claude-desktop # macOS; starts rowbit mcp itself
rowbit connect codex
rowbit connect gemini
rowbit connect windsurf
rowbit connect --print
prints the address (http://127.0.0.1:8080/mcp) and a token to send as Authorization: Bearer <token>.
Why not just migrations?
Having an agent write a migration file that goes through code review and CI is the right answer for a coding agent changing your schema, and Rowbit doesn't compete there: it holds every schema change for a person and leaves the real workflow to your migration tool. It works badly for fixing data:
- A reviewed diff shows SQL, not rows.
UPDATE orders SET status = 'cancelled' WHERE status = 'pending'looks fine in review. What it touches depends on the data when it runs. Rowbit shows the exact rows when the decision is made, and refuses to apply if they changed since. - A one-off fix can't wait for a pull request. Repairing a few broken rows during an incident needs an answer in minutes, and nobody writes and reviews a migration for every one.
- Not every write needs a person. Rules let small, safe writes straight through and hold only the risky ones, so reviewers aren't trained to rubber-stamp.
- Undo is per change. Down-migrations for data are usually missing or lossy. Rowbit keeps the before image of every row a change touched.
The well-known incidents of coding agents wiping production databases are a credentials problem as much as anything: take the credentials away and have the agent write migrations. Rowbit is for the agents that need to write. And if an agent does the same thing over and over, like issuing refunds, give it a tool that does just that instead of SQL.
Good to know
- Only Rowbit holds the database credentials. If an agent also has its own connection string, it can write around Rowbit. Give agents Rowbit's endpoint and nothing else (over HTTP, a token of their own), and Rowbit a database user of its own.
- An agent without
scopesreads and writes with Rowbit's privileges. Its rules still decide every write, but nothing stops it reading whatever Rowbit's user can. Give production agents scopes. - Undo restores rows, not the world. It puts the data back, but it can't take back an email that was sent or a refund that was paid because of it.
- Preview never writes to your tables. It reads the affected rows without taking locks and replays the write on a temporary copy that only Rowbit's connection can see. Tables with triggers or cascading foreign keys are refused, because their side effects wouldn't show in the preview or be undone. So are tables Rowbit's database user can't fully inspect: it needs the
TRIGGERandPROCESSprivileges. See database privileges for the exact grants. - Where data lives. Change state, previews (including before and after copies of affected rows) and the audit log are stored in a local SQLite file next to Rowbit. Protect it like a replica of the database (how).
- The CLI trusts whoever runs it. Anyone who can read
rowbit.dband has the database URL can runrowbit approve, under any--asname. Keep both from agents, and run Rowbit as a user they can't act as; see Before you use it for real. - Fail closed. Anything Rowbit can't evaluate, it refuses. See the change lifecycle and SECURITY.md.
Contributing
Ideas and opinions are welcome in Discussions. For code, see CONTRIBUTING.md. Commits need a DCO sign-off (git commit -s). Report security issues as described in SECURITY.md.
License
The server is AGPL-3.0-only. The rowbit.yml policy schema (crates/rowbit-policy) and future client SDKs are Apache-2.0.
Questions sur Rowbit MCP
Comment ajouter Rowbit MCP à Claude Code ?
Exécutez claude mcp add rowbit -- docker run -i --rm ghcr.io/ermag/rowbit:0.2.2 dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter Rowbit MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Quelles bases de données sont prises en charge ?
Rowbit prend actuellement en charge MariaDB et MySQL, avec un support via TLS. PostgreSQL est prévu pour une version ultérieure.
Puis-je annuler une modification si un agent IA commet une erreur ?
Oui, Rowbit vous permet d'annuler n'importe quelle modification individuelle en suivant chaque ligne impactée par un changement.
Le processus de prévisualisation modifie-t-il mes données réelles ?
Non, le processus de prévisualisation se contente de lire les lignes concernées et de rejouer l'écriture sur une copie temporaire privée pour vous montrer les changements.
Comment connecter Rowbit à mon agent IA ?
Vous pouvez utiliser la commande rowbit setup pour trouver l'URL de votre base de données et configurer des règles, ou utiliser des commandes de connexion spécifiques comme rowbit connect cursor ou rowbit connect claude-code.