QuintaDB for AI agents

QuintaDB is a no-code online database builder for managing records, forms, and reports as easily as a spreadsheet. Small teams use it to build lightweight internal tools without a developer. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect QuintaDB See the 12 actions ↓

Databases and spreadsheetsAPI keyMCP + RESTquintadb.com

AUDIT LOG · QUINTADBPOLICY: acme-support

09:41:07 · claude · u_8f2read

quintadb.list_forms

List Forms✓ allowed · 212ms

09:41:08 · claude · u_8f2read

quintadb.get_record

Get Record✓ allowed · 164ms

09:41:09 · claude · u_8f2write

quintadb.create_record

Create Record✓ approved · approved by user

09:41:12 · claude · u_8f2destructive

quintadb.delete_records_by_id

Delete Records By ID✕ blocked · policy: deny

EVERY QUINTADB CALL, ON THE RECORD

01 · USE CASES

What agents do in QuintaDB.

Search records in a database

Search for records matching a filter before updating or reporting on them.

Create a new record

Add a new record to a database with values filled from an external form.

Delete records with approval

Remove a batch of records only after the database owner confirms the cleanup.

02 · ACTIONS

12 QuintaDB actions, graded by risk.

Every QuintaDB action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

Look things up. Allowed by default.

quintadb.get_record
Get Record
quintadb.list_forms
List Forms
quintadb.list_fields
List Fields
quintadb.get_database
Get Database
quintadb.list_records
List Records
quintadb.list_reports
List Reports
quintadb.search_records
Search Records

write

Create and change things. Allow, or ask the user first.

quintadb.create_record
Create Record
quintadb.update_record
Update Record
quintadb.create_records
Create Records
quintadb.update_records_by_id
Update Records By ID

destructive

Delete, cancel or archive. Ask first, or deny outright.

quintadb.delete_records_by_id
Delete Records By ID

03 · HOW IT WORKS

QuintaDB in three steps.

01Your users connect QuintaDBThey add their QuintaDB api key on Arc0 Connect, under your brand. It goes straight into the vault.
02You set the rulesReads run, writes like “create Record” can wait for the user, and “delete Records By ID” can be denied outright.
03Any agent can actYour agent calls QuintaDB through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.

POLICY.TS

await arc0.policies.set('quintadb', {
  read: 'allow',
  write: 'ask',        // create_record
  destructive: 'deny',  // delete_records_by_id
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2

04 · AUTH AND DATA

How QuintaDB connects.

Users add their QuintaDB api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same QuintaDB connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH: API key
CREDENTIALS: Per-tenant encrypted vault
MODEL SEES: Results only, never credentials
AUDIT LOG: Every call, on every plan

05 · WORKS WITH

Use QuintaDB from any agent.

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

More databases and spreadsheets apps.

Google Sheets58 actions

Google BigQuery63 actions

NocoDB28 actions

ALL DATABASES AND SPREADSHEETS APPS →

07 · FAQ

QuintaDB and Arc0, answered.

Q01

Can I use QuintaDB with Claude, ChatGPT or Cursor?

Yes. Connect QuintaDB to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the QuintaDB actions you allow.

Q02

How do users connect QuintaDB?

Users add their QuintaDB api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which QuintaDB actions can my agent take?

12 in total: 7 read, 4 write and 1 destructive, such as “create Record”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in QuintaDB?

Yes. Actions like “delete Records By ID” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call QuintaDB too?

Yes. The same QuintaDB connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug QuintaDB into your agent.

Your users connect QuintaDB once, under your brand. Your agent gets 12 actions behind your policies, with every call on the record.

Connect QuintaDB Browse all apps →

Free to build · MCP + REST · Audit log on every plan