# Quintadb MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.quintadb%2Fmcp
Registry id: `mcp-registry/com.quintadb/mcp`
Status: live (checked 2026-10-26T23:21:29.925Z)

## Measurements (30 days)

- Uptime: 99.96%
- Checks: 5008
- Outages (90 days): 19

## Install

```json
{
  "mcpServers": {
    "quintadb-mcp-server": {
      "type": "http",
      "url": "https://quintadb.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http quintadb-mcp-server https://quintadb.com/mcp
```

## Tools (159)

- `add_dashboard_item`: Add a card to a portal's dashboard. Types (module_type): 2=a chart, 3=a map, 4=a calendar (module_id: its id); 9=a table or report; 10=the sum of a field; 11=th
- `add_portal_menu_item`: Add a portal menu entry. Top-level: module_ai_id + module_id. A submenu group: module_ai_id='submenu' + name (no module_id). An entry inside it: parent_section_
- `add_record_comment`: Add a comment to a record.
- `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 invi
- `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 sh
- `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 i
- `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 
- `check_ai_site_status`: Check the status of an AI site generation. Call it every 10-15 s after generate_ai_site. Returns: pending / success / error.
- `configure_chat`: Set up the contact buttons (chat widget) in a portal — WhatsApp, Telegram, email, phone, Instagram and so on. Pass channels as an object {whatsapp: '+380...', t
- `create_action_rule`: Create an automation (action rule) of a form. It runs on_create / on_update and does: send_email, send_sms, update_record, redirect, show_message — or, with do_
- `create_calendar`: Create a calendar with data sources (events from forms). date_title_type: 0=fixed text, 1=from a field. info_window_type: 0=fixed text, 1=from a field.
- `create_chart`: Create ONE chart. type_code: line, bar, column, pie, doughnut, area, scatter. The X axis comes from a field of the table (property_id): axis_l mth puts each rec
- `create_dashboard_charts`: Make several charts at once and put each on a portal's dashboard as a card: «make me a dashboard», «a chart for each metric». ONE call for all of them. Each cha
- `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 N
- `create_field`: Add a field to a form. Types: text, textarea, integer, float, date, datetime, email, phone, url, select, checkbox, radio, file, image, location, autoincrement, 
- `create_folder`: Make an EMPTY folder on one list page of the control center. module is the list the folder groups: forms, reports, charts, maps, calendars, files, portals. It o
- `create_form`: Create a new, EMPTY form (table) in an existing project; add its fields with create_field after it. A table made of what a column already holds — a dropdown's o
- `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_
- `create_map`: Create a Google Maps map with data sources (markers from forms). center_type: 1 = address, 2 = coordinates, 3 = first record.
- `create_portal`: Create a new portal for the project. A portal is the client-facing interface with a menu, a dashboard and access rights.
- `create_portal_group`: Create a group of portal users and set its access rights on forms/reports. Use it after create_portal. Call set_table_permission with portal_group_id for rights
- `create_portal_page`: Add a page of its own to a portal: a name and the page's content as HTML. It goes into the portal's menu under its name by itself — do not call add_portal_menu_
- `create_project`: Create a new project (database) with its first form. After creating it, add fields through create_field.
- `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
- `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 
- `create_reminder`: Make a reminder: an e-mail about a record, sent by a date field of its table. ONCE per record — days_before days before the date (0 = on the day, negative = aft
- `create_report`: Create a report (filter/view) for a form. Supports filter conditions, grouping, the sum/average per group, visible columns, sorting. For dates: yesterday, today
- `create_saved_view`: Save a SET OF SEARCH FILTERS for a table (criteria + sorting). ⚠️ This is NOT a report: it will not be on the «Reports» page — report widgets live there (create
- `create_schedule`: Mail a table's or a report's rows as a file on a schedule: every day or on one weekday, at a time, to the listed addresses.
- `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_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
- `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_webhook`: Make an automation CALL ANOTHER SERVICE (a webhook: Zapier, Make, n8n, your own server) when it runs. A webhook is a step of an automation — pass action_id, the
- `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.
- `delete_action_rule`: Remove an automation (an action rule) from a table. Cannot be undone. Ids come from list_action_rules.
- `delete_calendar`: Remove a calendar from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_calendars.
- `delete_chart`: Remove a chart from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_charts.
- `delete_dashboard_item`: Remove a card (widget) from a portal's dashboard. Only the card goes; the table, report or chart it showed stays. The person confirms it first.
- `delete_few_records`: Delete several records in one request
- `delete_field`: Delete ONE field (column, property) from a form. Irreversible — all data in this field will be lost. (remove field, drop column) To remove SEVERAL fields — of o
- `delete_field_rule`: Remove ONE field rule of a form, by its rule_id from list_field_rules: the fields it showed, hid or filled in go back to how the form shows them without it. Ask
- `delete_fields`: Delete SEVERAL fields in ONE call — whenever the person asks to remove more than one field, or to keep only some fields of a table (pass every field that goes).
- `delete_form`: Delete a form and all its records. Cannot be undone. The only form cannot be deleted.
- `delete_formatting`: Remove a formatting rule. The person confirms it first.
- `delete_map`: Remove a map from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_maps.
- `delete_portal`: Remove a whole portal: its pages, menu, dashboard and its portal users' accounts. The tables and records stay. The person confirms it first; it cannot be undone
- `delete_portal_group`: Delete a portal group together with its rights and members.
- `delete_portal_menu_item`: Delete a portal menu item. section_id for a top-level item, item_id for a submenu item.
- `delete_portal_page`: Remove a page from a portal, with the menu items that lead to it. The person confirms it first. The portal's start page is refused: another start is chosen firs
- `delete_portal_user`: Remove a user from a portal
- `delete_project`: Delete a project (sets hidden=true and starts the background DeleteAppJob).
- `delete_record`: Delete a record
- `delete_record_comment`: Remove ONE comment from a record, by its comment_id from list_record_comments — a comment the person you are talking to wrote (`yours`). Anyone else's comment i
- `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 say
- `delete_records_by_filter`: Delete records in bulk by a filter, a list of IDs, or all records of the form. Cannot be undone.
- `delete_reminder`: Delete a reminder.
- `delete_report`: Remove a report from its table and from every portal menu that shows it. The table and its records stay. Cannot be undone. Ids come from get_reports.
- `delete_saved_view`: Delete a saved set of search filters.
- `delete_schedule`: Delete a schedule.
- `delete_team_group`: Delete a team group together with all its rights and members.
- `delete_template`: Delete a template (record/email/sms/telegram/whatsapp).
- `delete_webhook`: Remove a webhook. The automation that called it stops calling a webhook; its other steps stay.
- `describe_project`: The project's whole schema: every form, its fields with types and choices, the number of records, and the portals. A link field (rel) names the table it links t
- `duplicate_form`: Copy a form with its fields, settings and records. An asynchronous operation (~10 s).
- `duplicate_record`: Make a copy of a record with all its field values (asynchronously, through CloneRecordJob).
- `edit_site_block`: Replace ONE block of the site without touching the rest of the page (the rest stays byte for byte). Use it instead of generate_ai_site when something specific m
- `export_records`: Export a form's records to XLSX or PDF and send them by email.
- `fetch_url`: Download a particular web page and get its text (to pull facts about a book/product/company from a publisher's site and so on). Call it after web_search or when
- `generate_ai_project`: Generate a whole project with forms and reports from a text description
- `generate_ai_site`: Generate or update the portal's AI landing page. An asynchronous operation — check the status through check_ai_site_status. For a redesign pass existing_html fr
- `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 pers
- `get_field_types`: The full reference of QuintaDB field types with descriptions of their parameters. Call it before create_field when a formula, linked_column, rel or any non-stan
- `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 field
- `get_form_settings`: Get a form's detailed settings: post_action, sort_by, per_page, allow_delete, send_emails, inline_editing and so on.
- `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
- `get_portal_page`: Get the HTML content of a portal page. If page_id is not passed, the portal's default page is used; if it cannot be told for sure, call list_portal_pages first.
- `get_project`: Get detailed information about a project by its app_id.
- `get_public_page`: A table's PUBLIC page — the address its owner gives to people who have no account. Answers every switch of the page with its meaning, what a visitor can do ther
- `get_quickstart_guide`: QuintaDB domain knowledge guide. Call this at the start of a session to learn field types, rel/linked_column rules, validation syntax, portal theme/color codes,
- `get_record`: Get one record by ID
- `get_records`: Get records of a form. Supports search and pagination
- `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 
- `get_relationship`: Show how a field's link to another table is set up: the type (list / radio / autocomplete / checkboxes), which column is shown instead of the id, the link colum
- `get_report_data`: Get the data of a specific report
- `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 bel
- `get_usage_stats`: The account's usage statistics: plan, the total % of capacity used this month, the split by category (system_activity, database_records, file_storage, ui_and_ap
- `get_user_info`: Return information about the current user (email, plan, number of projects/records).
- `import_records`: Import records in bulk from CSV or an array of objects. For the 'records' array ALWAYS use field IDs as keys.
- `invite_portal_user`: Invite a new person into a portal: creates their account and mails the portal's invitation letter. The new account gets a password of its own, which only the in
- `list_action_rules`: Return all automation rules of a form with their conditions and update fields (update_fields). id is a string; pass it to update_action_rule as it is.
- `list_calendars`: The project's calendars, each with its sources of events and their ids (for update_calendar)
- `list_charts`: The project's charts, each with the series it shows and their ids (for update_chart)
- `list_dashboard_items`: List the widgets of the portal's dashboard (id, name, type, position, icon). Needed to find a widget's id before update_dashboard_item — for example when transl
- `list_field_rules`: The field rules of one table, or of every table of the project that has any — «show these fields when…», «hide…», «set a value when…». Each rule comes as the se
- `list_folders`: The folders of a project: each with its name, the list it groups (module) and how many items are in it. A folder only groups one list page of the control center
- `list_formattings`: The formatting rules (column styles, highlighted rows) of a project or one table: id, name, the fields, the style, the conditions. Call it before update_formatt
- `list_forms`: List all forms (tables) in a project. List all forms, tables, entities in a project.
- `list_maps`: The project's maps, each with its sources of markers and their ids (for update_map)
- `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`)
- `list_portal_menu_items`: The portal's menu: its top-level items, each with the items inside it (`submenu_items`) — a top-level item may open a table AND hold items. `position` is the pl

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.