Connect AI apps
Add Rowsafe to ChatGPT, Claude, Cursor, VS Code, Codex or Windsurf by signing in once, with no API key.
Ask your AI app "Are my databases backed up?" or "What should I fix first?", and let coding agents save a Mark before risky changes. Apps connect to:
https://api.rowsafe.sh/mcpThe first time, the app opens Rowsafe in your browser. Pick the organization, tick Save Marks and Act for you if you want them, and click Allow. No API key needed. (For CI or an app without sign-in, use an API key.)
What a connected app can do
| Connected app | |
|---|---|
| See databases, health, findings, backups, Proof, Marks, alerts, metrics, security, updates, the audit log, Rowsafe Cloud prices and servers | Yes |
| Save a Mark | With Save Marks |
| Run backups, Proof and checks, preview migrations, make masked safe copies, acknowledge alerts, change schedules | With Act for you |
| Change production (fix, restart, restore, rewind, upgrade, ...) and Rowsafe Cloud servers | With Act for you: as you, right away, while you're an owner or admin (How AI agents act) |
| Create a database and login for its app | Never: you create it in the dashboard, where your browser makes the password. A local rowsafe mcp can, on PostgreSQL (Need a database?) |
| Change what AI agents may do | Never: only an owner, in the dashboard |
| Pay | Never: a first payment is an owner's, at a checkout link the app gives you |
| Read the rows in your tables | Never: Rowsafe itself never sees them |
An app acts for the one organization you picked. Everything it does is in the audit log as you through the app.
What the Allow page says
With Act for you, the page explains that the app can make the changes you can make in the dashboard, right away, and confirms disruptive ones with you in chat. If you stop being an owner or admin, its changes are refused. Leave it unticked for an app that should only look.
Apps connected earlier
Older apps show Can't make changes yet in Settings → Connected apps. The person who connected one clicks Let it act as me, or connects it again. Until then, Rowsafe refuses its changes.
Set it up
- In ChatGPT, open Settings, Apps & Connectors, Advanced settings, and turn on Developer mode. It needs a paid plan; in a Business or Enterprise workspace an admin may need to allow it.
- Click Create. Name it Rowsafe, paste
https://api.rowsafe.sh/mcp, and choose OAuth. - Sign in with Rowsafe and click Allow.
- In a new chat, click +, pick Rowsafe, and ask away.
Rowsafe isn't in ChatGPT's app directory yet, so it's added this way.
Any other app that supports remote MCP servers with OAuth works the same way: give it the URL.
Who can connect an app
Owners and admins. A member sees Allow greyed out: an admin connects the app, or makes them an admin.
Disconnect an app
Settings → Connected apps, Disconnect. Access ends right away; Marks it saved stay.
Rowsafe also disconnects an app when the person who allowed it is removed, leaves the organization or deletes their account, or when a sign-in token is used twice (it may have leaked; connect again if it was yours).
How it stays safe
- You approve every app on a Rowsafe page, in your own browser. It shows the app's name, whether Rowsafe could verify it (ChatGPT and Claude Code show Verified: chatgpt.com and similar; others are not verified), where you'll return to, and a warning when the app runs on your own computer.
- Sign-ins go only to known apps. Rowsafe sends approvals only to the published callback addresses of ChatGPT, Claude, VS Code and Cursor, and to
localhost. A link someone sends you can't route your approval to their website, and only the browser that started a sign-in can finish it. - Short-lived tokens, for MCP only: a one-hour access token for
https://api.rowsafe.sh/mcpand a single-use refresh token. Rowsafe stores only their hashes. - Never more than you ticked, or more than you. Without Act for you, the app never sees the tools that run backups, make copies or change production, and the API refuses them. With it, Rowsafe checks your role at every change, with the dashboard's own checks and Marks (safety nets).
It follows the MCP authorization specification (OAuth 2.1 with PKCE, protected resource metadata, client ID metadata documents, dynamic client registration). Details: MCP reference.
Troubleshooting
- "We don't know this app" or "Rowsafe only sends sign-ins back to known AI apps": the app wants to return somewhere unknown. Tell us which app at [email protected], or use an API key.
- "Finish in the browser you started in": start again from the app, in one browser.
- "This sign-in expired": sign-ins last 10 minutes. Start again.
- The app keeps asking you to sign in: it was disconnected, or lost its refresh token. Connect it again.
- Allow is greyed out: you're a member. Ask an admin.