QuintaDB

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "quintadb": {
      "type": "http",
      "url": "https://quintadb.com/mcp"
    }
  }
}

159 tools

• list_projects

  List all projects (databases) in the QuintaDB account

• list_forms

  List all forms (tables) in a project. List all forms, tables, entities in a project.

• get_form_fields

  The form's fields with names and types. ALWAYS call it before create_record and before building a newsletter, to know the exact names and html_name of the fields. A link field (rel) also says how many rows of this form hold a link (rows_linked), how many rows the linked table…

• get_records

  Get records of a form. Supports search and pagination

• get_record

  Get one record by ID

• get_rel_id

  Get the numeric rel_id for a field of type 'rel' (a link). Needed before create/update record when a rel field must be filled in. Pass the form's entity_id and the link field's property_id.

• create_record

  Create a new record in a form (insert row, add entry, new record). FIRST read the form's fields with describe_project or get_form_fields; the keys of 'data' are a field's id, its name or its html_name — any of the three those tools show; any other key is refused and nothing is…

• update_record

  Change ONE existing record. Link fields go in 'rels', subform fields in 'subforms'. The answer says each cell's change — `changed` (was → now) and `unchanged`. A row holds one value per field: a second call on the SAME record_id replaces what the first wrote, so several names…

• delete_record

  Delete a record

• delete_few_records

  Delete several records in one request

• bulk_update_records

  Update a field (or fields) in many records at once. Instead of N update_record calls for 'set status Processed on all of today's orders'. Records can be chosen by a list of IDs, by a filter (field = value), by a report, or all records of the form. Supports action rules…

• update_cell

  Update the value of one field in a record without overwriting the other fields. ALWAYS use the field's ID, not its name.

• upload_file_to_record

  Upload a file or image to a record's field. Takes the file's content in base64. Saves the file and attaches it to the given field. For multiple-file fields it adds to the existing files.

• attach_media_to_record

  Attach a file from the MyFile library to a field of type file or image of a specific record. Use it for attached_files instead of update_record when the field is of type file/image.

• import_records

  Import records in bulk from CSV or an array of objects. For the 'records' array ALWAYS use field IDs as keys.

• search_records

  Search/filter records (filter records, find entries, query data). Operators: is, is_not, contains, not_contains, starts_with, ends_with, is_empty, is_not_empty, gt, lt

• get_column_total

  The sum (or another aggregate) of a number field, as a number for your reply: it answers «how much is it in all». It puts nothing into the table — when the person wants a total SHOWN under the column, that is the field's own setting: update_field with settings.

• get_metric

  Get a real number from the database and return it to the user in the chat. metric_type: count (number of records), sum (sum of a number field), average (average), new_today (records added today), updated_today (records updated today), growth (the current period compared with the…

• run_action

  Run an automation (action rule) for a record — send an email, trigger a webhook and so on. action_id is the ID of the action button field

• get_reports

  The project's reports (saved views of a table: filters, grouping, totals). Without entity_id: EVERY report of every table, each with its id and the table it belongs to — use this when the person names a report and not its table; never guess the table from the report's name. With…

• get_report_data

  Get the data of a specific report

• seed_records

  Seed a form with initial records in bulk. Use it to fill a form with test or reference data. For one record create_record is better. Supports subforms through subforms.

• remove_example_records

  Remove the sample records that project generation added — what the person calls «the examples», «les exemples», «приклади», «примеры», sample, demo or test data. Deletes ONLY the records the generator registered as examples; records the person entered are never touched. Without…

• create_record_template

  Create a RECORD template for printing/export (PDF/HTML) — that is, set HOW a record looks on paper or in a file: a blank to fill in by hand, a form, a delivery note, an act, a log, a checklist. 🚨 Call it when the user asks for a printed look of records or for the same record in…

• update_record_template

  Update an existing PDF/HTML record template (its name and/or body). Use this, not create_record_template, when the user asks to 'change'/'update' an existing print template — it keeps the template's ties to print buttons and the payment flow.

• list_record_templates

  The record templates of a project or one table — the layouts ONE record is shown or printed with: each with its name, whether it is a record's page or a tile, and where it is in use now. Call it before update_record_template / delete_record_template to find the template_id, and…

• delete_record_template

  Remove ONE record template, by its template_id from list_record_templates. The pages that showed a record with it go back to the standard layout; the answer says which. The records themselves are not touched.

• create_email_template

  Create an email template for mailing from a form. Put a field's 'html_name' into body and subject WITHOUT any brackets (just as text, for example: Hello, Full Name). Never use {{}} or []. Get html_name through get_form_fields.

• create_sms_template

  Create an SMS template for mailing. Put a field's 'html_name' into body WITHOUT any brackets (e.g. Full Name). Get html_name through get_form_fields.

• create_telegram_template

  Create a Telegram message template. Put a field's 'html_name' into body WITHOUT any brackets (e.g. Full Name). Get html_name through get_form_fields.

• create_whatsapp_template

  Create a WhatsApp message template. Put a field's 'html_name' into body WITHOUT any brackets (e.g. Full Name). Get html_name through get_form_fields.

• create_formatting

  Style a table's or report's columns: font size (px), font family, text and background colour, bold, italic, underline, strike — for the chosen fields (property_ids; empty = all columns), on every row (all=true) or only on rows that match conditions (all=false + conditions). Use…

• create_team_group

  Creates a team group (the internal back office) with rights on forms and reports. tables_permissions gives access at creation: an array of table (the id or name of a form or report), role (the numbers are in its own description), only_own_records, hidden_fields (names or ids of…

• list_team_groups

  List back-office team groups (roles, members, permissions). (get team groups, show staff groups)

• add_user_to_team_group

  Add a person to a team group by email. An account is created when there is none. The new account gets a password of its own, which only the invitation letter shows (with a one-time link that signs the person in); the answer's `invitation` says what was mailed. Never tell anyone…

• remove_user_from_team_group

  Remove a user from a team group. Pass user_id or email.

• update_team_group

  Change a team group's POWERS (and its name). These are not rights on tables — those are set_table_permission. Here is what a person may DO in the project: manage the team (can_add_users / can_edit_access_rights / can_delete_users), create portals, charts, maps, calendars…

• delete_team_group

  Delete a team group together with all its rights and members.

• list_portal_groups

  List a portal's user groups: members, and for each table or report the group has rights on — its role and whether the group sees only its own records (`tables`). Read it before changing who sees what: the group you need usually exists already. (get portal groups, show client…

• add_user_to_portal_group

  Add a person to a portal group by email. An account in the portal is created when there is none. The new account gets a password of its own, which only the invitation letter shows (with a one-time link that signs the person in); the answer's `invitation` says what was mailed…

Security scan

Recent checks