QuintaDB MCP: manage no-code database records from chat

How to connect QuintaDB to Claude, ChatGPT or Cursor

1. 1Click Connect QuintaDB free and sign in with your QuintaDB account.
2. 2Deleting records is permanent. Switch it off, and switch off the bulk create and update tools too if you want each change made one record at a time.
3. 3Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on the Works with page.
4. 4Ask your AI app to find the records added to your leads form this week, then open Activity to see the search.

Records work in plain language

• List the forms in a database, their fields and their reports.
• Search a form's records by field values, or page through a report.
• Create one record or up to 100 at once.
• Update fields on one record or many by ID.
• Manage your QuintaDB automation by describing what you want.

Keep your data intact

• Switch off record deletion; the tool is hidden from your AI app and refused if called.
• Use a policy to warn before bulk creates or updates, which in ContextGate's app connector run one record at a time and can partly succeed.
• Activity records every record your AI app adds, changes or deletes.

What you get with QuintaDB and ContextGate

• Your AI apps can use QuintaDBClaude, Cursor, ChatGPT and other AI apps reach QuintaDB through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any QuintaDB tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

QuintaDB tools

Examples of what your AI apps can do in QuintaDB. You'll see the exact list of tools after you connect it.

• Create RecordCreate one record in a QuintaDB form using values keyed by field ID. The tool supplies QuintaDB's required entity_id inside the nested values body.
• Create RecordsCreate 2-100 QuintaDB records using sequential individual API calls in input order. This is not atomic: some records can succeed while others fail, and every item returns its own outcome.
• Delete Records By IDPermanently delete only the explicitly supplied QuintaDB record IDs from one form. This tool never supports delete-all or filter-based deletion.
• Get DatabaseGet metadata and resource counts for one allowed QuintaDB database by app ID. Use this instead of global database discovery when the API key is restricted to selected apps.
• Get RecordGet one record by exact ID from an allowed QuintaDB database. Values are returned under their field IDs for reliable use with QuintaDB schema and record tools.
• List FieldsList the fields in a QuintaDB form, including field IDs and types. Use these IDs as keys in record values and search predicates.
• List FormsList forms/tables in an allowed QuintaDB database, including IDs and record counts needed for field and record operations.
• List RecordsReturn one page of records from a QuintaDB form, optionally constrained to a report. Record values remain keyed by field ID for reliable use with schema and write tools.
• List ReportsList QuintaDB reports/views for a form. Use a returned report ID to constrain record listing or search.
• Search RecordsSearch records in one QuintaDB form using explicit field or system-column predicates. Groups are combined with OR; predicates inside each group are combined with AND.
• Update RecordUpdate selected fields on one QuintaDB record using a field-ID keyed values object.
• Update Records By IDUpdate 2-100 exact QuintaDB record IDs using sequential individual API calls in input order. This is not atomic: some updates can succeed while others fail, and every item returns its own outcome.