QuintaDB

Connect Remote server

claude mcp add --transport http mcp https://quintadb.com.ua/mcp

{
  "mcpServers": {
    "mcp": {
      "url": "https://quintadb.com.ua/mcp"
    }
  }
}

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

Settings > Connectors > Add custom connector
URL: https://quintadb.com.ua/mcp

Tools 80 found in our last check

• 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 ha…

• 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 w…

• 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 me…

• 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 — trigger…

• 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, mailin…

• 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 gro…

• 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. Ne…

• remove_user_from_portal_group

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

• delete_portal_group

  Delete a portal group together with its rights and members.

• set_table_permission

  What a group (team or portal) may do on a table or report, and whether its people see ONLY THEIR OWN records there. For a group that already has rights on the table pass ONLY what the person asked to change: «technicians see only their own orders» is only_own_records: true with…

• 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_not_send_data_if_criteria_matches, REFUSES the record. It can carry conditions and the fields to set (update_fields). T…

• 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, last_7_days, last_30_days, this_month, this_week, between (+ from/to), before, after and so on.

• create_project

  Create a new project (database) with its first form. After creating it, add fields through create_field.

• 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 options, the stages, suppliers or categories named on the rows, the parents a list must depend on (Stage → Check point)…

• 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, yes_no, rel, formula, linked_column, linked_records, subform, map, action, divider, page_break, note, signature, countr…

• update_field

  Change/rename a form field (rename field, edit property, update column). Name, description, position, options for select/radio, default value, required, sizes, uniqueness. Does not change the field's type.

• 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-standard type is needed. Returns all 40+ types and the detailed specification of formulas, with the rules of Ruby scripts a…

• 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, and the correct workflow for building or modifying a project. Essential for external AI clients (Claude, ChatGPT) conn…

• 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 to (links_to) and how many rows hold a link (rows_linked), and, when there are any, how many links point at no row (link…

• 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 on a particular table, or pass tables_permissions right here.

• 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...', telegram: '@mybot', email: 'info@...', phone: '+380...'}.

• create_portal

  Create a new portal for the project. A portal is the client-facing interface with a menu, a dashboard and access rights.

• 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_id + module_ai_id + module_id. module_ai_id kinds: form_ID/table_ID = a form, report_ID = a report, map_ID = a map, cal…

• 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 place in the list, 0 = first. Call it before a rename, a move, a delete or a module change, to get section_id or item_id.

• update_portal_menu_item

  Update a portal menu item: rename it, change its module, icon, place or URL. Give section_id (a top-level item) or item_id (an item inside a section) from list_portal_menu_items. To MOVE an item, give `position`: the place it must stand at after the move among its own siblings,…

• delete_portal_menu_item

  Delete a portal menu item. section_id for a top-level item, item_id for a submenu item.

• 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 translating the project's interface into another language.

• update_dashboard_item

  Change the NAME (the card's caption), the icon or the position of a dashboard widget. ⚠️ Dashboard captions are separate from table names: renaming forms does NOT touch them, so when the project's interface is translated the dashboard must be updated with this tool separately, o…

• 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=the average of a field; 12=the number of records; 13=records added today; 14=records changed today; 15=a link; 16=a page;…

• 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 chart: a name, a type, its table, the field along the X axis (a date or a number field puts each record's value there; a d…

• list_portal_users

  List of the portal's users (clients registered in the portal)

• 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 invitation letter shows (with a one-time link that signs the person in); the answer's `invitation` says what was mailed.…

• update_portal_user

  Change a person's account in a portal: their email address, login, first name, last name or phone. Pass only what the person asked to change; nothing else is touched. The answer says CHANGED (was → now) / UNCHANGED per item. A password is NEVER set here and never asked for in th…

• send_portal_user_password_letter

  Mail a person in a portal the portal's own letter with a link where they set a new password themselves (the link works for one day; their present password keeps working until then). For «reset X's password», «X forgot the password», «X cannot sign in». Never ask the owner for a…

• delete_portal_user

  Remove a user from a portal

• list_charts

  The project's charts, each with the series it shows and their ids (for update_chart)

• 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 record's value of that field along it (a date, a number, a name — not «by month»), axis_l field one bar per choice of a dr…

• update_chart

  Change a chart: its name, its type (pie, doughnut, line, area, bar, column, scatter) or the title of its vertical axis. Pass only what changes. `add_data_sources` adds series and `remove_data_source_ids` removes series by the ids list_charts shows (798); every other series stays…

• delete_chart

  Remove a chart from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_charts.

• update_map

  Change a map: its name, where it is centred (center_type 1 = an address, 2 = coordinates, 3 = the first record) and its zoom. Pass only what changes. `add_data_sources` adds sources of markers and `remove_data_source_ids` removes sources by the ids list_maps shows (798); every o…

• delete_map

  Remove a map from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_maps.

• update_calendar

  Change a calendar: its name, or whether it shows Saturdays and Sundays (weekends). Pass only what changes. `add_data_sources` adds sources of events and `remove_data_source_ids` removes sources by the ids list_calendars shows (798); every other source stays as it is. Ids come fr…

• delete_calendar

  Remove a calendar from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_calendars.

• update_report

  Change a report: its name, its filters, the columns it shows, how it is sorted, how many records a page holds. Pass only what changes. `criterias` REPLACES all the report's filters. `group_field_ids` REPLACES its grouping (798): an empty list makes it a plain list again; a total…

• 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_action_rule

  Remove an automation (an action rule) from a table. Cannot be undone. Ids come from list_action_rules.

• list_maps

  The project's maps, each with its sources of markers and their ids (for update_map)

Details

More communication servers See all

• Formpit

  Form backend with an inbox: create form endpoints, read submissions and reply by email.

• IGNOREO

  Tools for AI agents, pay per call in USDC (x402): privacy scan, site/email/VIN checks, chess, more

• Palimpalem

  Websites for local businesses: draft, keep, edit by chat, publish; domain, DNS, e-mail, Plus.

• Quokka Korea Tools

  Korean holidays, business days & legal deadlines, won amounts in words, NEIS/SMS byte counts

• Turbo Notify: WhatsApp for AI agents

  Send, receive, edit and react to WhatsApp messages from your own number. OAuth or API key sign-in.

• Turbo Notify: WhatsApp for AI agents

  Send, receive, edit and react to WhatsApp messages from your own number. OAuth or API key sign-in.