{"id":"com.quintadb/mcp","slug":"com-quintadb-mcp","title":"QuintaDB","description":"No-code databases, forms, portals and AI sites. Manage records and automation via natural language.","version":"1.0.0","publisher":{"kind":"domain","id":"quintadb.com","label":"quintadb.com","url":"https://quintadb.com"},"website":"","repository":"","remotes":[{"type":"streamable-http","url":"https://quintadb.com/mcp"}],"packages":[],"published":"2026-06-22","updated":"2026-06-22","status":"online","auth":"","latency_ms":1197,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"list_projects","title":"","description":"List all projects (databases) in the QuintaDB account","read_only":true},{"name":"list_forms","title":"","description":"List all forms (tables) in a project. List all forms, tables, entities in a project.","read_only":true},{"name":"get_form_fields","title":"","description":"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 has (linked_table_rows), and any links to no row or to another table; a linked_column says what it shows. When someone asks","read_only":true},{"name":"get_records","title":"","description":"Get records of a form. Supports search and pagination","read_only":true},{"name":"get_record","title":"","description":"Get one record by ID","read_only":true},{"name":"get_rel_id","title":"","description":"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.","read_only":true},{"name":"create_record","title":"","description":"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 written. One call makes ONE row: for several rows call it once per row (or seed_records). A value the person did not give ","read_only":false},{"name":"update_record","title":"","description":"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 mean several rows — a different record_id for each, and create_record for the ones no row is left for.","read_only":false},{"name":"delete_record","title":"","description":"Delete a record","read_only":false},{"name":"delete_few_records","title":"","description":"Delete several records in one request","read_only":false},{"name":"bulk_update_records","title":"","description":"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 — triggers fire as on an ordinary update.","read_only":false},{"name":"update_cell","title":"","description":"Update the value of one field in a record without overwriting the other fields. ALWAYS use the field's ID, not its name.","read_only":false},{"name":"upload_file_to_record","title":"","description":"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.","read_only":false},{"name":"attach_media_to_record","title":"","description":"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.","read_only":false},{"name":"import_records","title":"","description":"Import records in bulk from CSV or an array of objects. For the 'records' array ALWAYS use field IDs as keys.","read_only":false},{"name":"search_records","title":"","description":"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","read_only":true},{"name":"get_column_total","title":"","description":"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.","read_only":true},{"name":"get_metric","title":"","description":"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 previous one; needs date_field and compare_period). entity_id can be a form ID or a report ID (with its filter).","read_only":true},{"name":"run_action","title":"","description":"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","read_only":false},{"name":"get_reports","title":"","description":"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 entity_id: that one table's reports.","read_only":true},{"name":"get_report_data","title":"","description":"Get the data of a specific report","read_only":true},{"name":"seed_records","title":"","description":"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.","read_only":false},{"name":"remove_example_records","title":"","description":"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 entity_id it clears every table of the project; with entity_id only that table. When the person asks to delete, clear or ","read_only":false},{"name":"create_record_template","title":"","description":"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 Excel/Word/PDF — in ANY language, and even when it is one phrase inside a long project description or a pasted format spe","read_only":false},{"name":"update_record_template","title":"","description":"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.","read_only":false},{"name":"list_record_templates","title":"","description":"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 to answer «which layouts does this table have?».","read_only":true},{"name":"delete_record_template","title":"","description":"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.","read_only":false},{"name":"create_email_template","title":"","description":"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.","read_only":false},{"name":"create_sms_template","title":"","description":"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.","read_only":false},{"name":"create_telegram_template","title":"","description":"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.","read_only":false},{"name":"create_whatsapp_template","title":"","description":"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.","read_only":false},{"name":"create_formatting","title":"","description":"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 it for «make the font in field X smaller / larger», «make X bold / red», «highlight the rows where …». A condition compar","read_only":false},{"name":"create_team_group","title":"","description":"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 the fields to hide).","read_only":false},{"name":"list_team_groups","title":"","description":"List back-office team groups (roles, members, permissions). (get team groups, show staff groups)","read_only":true},{"name":"add_user_to_team_group","title":"","description":"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 a password. move_from_other_groups=true takes the person out of every other group and resets their individual roles (a fu","read_only":false},{"name":"remove_user_from_team_group","title":"","description":"Remove a user from a team group. Pass user_id or email.","read_only":false},{"name":"update_team_group","title":"","description":"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, mailings, work with files. Pass ONLY the keys that must change: keys not passed are NOT touched, so that settings made earlier ","read_only":false},{"name":"delete_team_group","title":"","description":"Delete a team group together with all its rights and members.","read_only":false},{"name":"list_portal_groups","title":"","description":"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 groups)","read_only":true},{"name":"add_user_to_portal_group","title":"","description":"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. Never tell anyone a password. move_from_other_groups (default false) moves them out of the portal's other groups.","read_only":false},{"name":"remove_user_from_portal_group","title":"","description":"Remove a user from a portal group. Pass user_id or email.","read_only":false},{"name":"delete_portal_group","title":"","description":"Delete a portal group together with its rights and members.","read_only":false},{"name":"set_table_permission","title":"","description":"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 NO role — a role you pass replaces the group's present one. The answer says CHANGED / UNCHANGED for the role and for only","read_only":false},{"name":"create_action_rule","title":"","description":"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). The answer's `page` is the address of the page that lists this table's automations: give the person that address, never on","read_only":false},{"name":"create_report","title":"","description":"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.","read_only":false},{"name":"create_project","title":"","description":"Create a new project (database) with its first form. After creating it, add fields through create_field.","read_only":false},{"name":"create_form","title":"","description":"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) — is split_column_into_table, never this: it makes the rows and links every record.","read_only":false},{"name":"create_field","title":"","description":"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, country, language, states, time_zone, record_owners, matrix. A type's full parameters — get_field_types. ⚠️ For select/checkbox","read_only":false},{"name":"update_field","title":"","description":"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.","read_only":false},{"name":"get_field_types","title":"","description":"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 and examples.","read_only":true},{"name":"get_quickstart_guide","title":"","description":"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) connecting via MCP.","read_only":true},{"name":"describe_project","title":"","description":"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 (links_to_missing_rows) or at a row of another table (links_to_other_table); a linked_column names the field it shows (shows).","read_only":true},{"name":"create_portal_group","title":"","description":"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.","read_only":false},{"name":"configure_chat","title":"","description":"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...'}.","read_only":false},{"name":"create_portal","title":"","description":"Create a new portal for the project. A portal is the client-facing interface with a menu, a dashboard and access rights.","read_only":false},{"name":"add_portal_menu_item","title":"","description":"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_ID = a calendar, chart_ID = a chart. The portal's dashboard is not an entry you add: a portal whose home is a page shows","read_only":false},{"name":"list_portal_menu_items","title":"","description":"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.","read_only":true},{"name":"update_portal_menu_item","title":"","description":"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, counted as list_portal_menu_items shows them (0 = first; a number past the end = last). The other items shift by themselv","read_only":false},{"name":"delete_portal_menu_item","title":"","description":"Delete a portal menu item. section_id for a top-level item, item_id for a submenu item.","read_only":false},{"name":"list_dashboard_items","title":"","description":"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.","read_only":true},{"name":"update_dashboard_item","title":"","description":"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, or it stays in the previous language.","read_only":false},{"name":"add_dashboard_item","title":"","description":"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; 17=growth of a table over a period (module_id, date_property_id, change_period); 18=growth between two cards (first_widg","read_only":false},{"name":"create_dashboard_charts","title":"","description":"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 dropdown, radio or checkbox field one bar per choice) and the number field(s) it shows. The whole call is checked first: a","read_only":false},{"name":"list_portal_users","title":"","description":"List of the portal's users (clients registered in the portal)","read_only":true},{"name":"invite_portal_user","title":"","description":"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. Never tell anyone a password.","read_only":false},{"name":"update_portal_user","title":"","description":"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 the chat: send_portal_user_password_letter mails the person a link to set their own.","read_only":false},{"name":"send_portal_user_password_letter","title":"","description":"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 password and never write one in the chat.","read_only":false},{"name":"delete_portal_user","title":"","description":"Remove a user from a portal","read_only":false},{"name":"list_charts","title":"","description":"The project's charts, each with the series it shows and their ids (for update_chart)","read_only":true},{"name":"create_chart","title":"","description":"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 dropdown, radio or checkbox field. data_sources are the series. Several charts for a dashboard: create_dashboard_charts.","read_only":false},{"name":"update_chart","title":"","description":"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 as it is. To change one series: remove it and add the new one in the same call. It does NOT change the horizontal axis (","read_only":false},{"name":"delete_chart","title":"","description":"Remove a chart from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_charts.","read_only":false},{"name":"update_map","title":"","description":"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 other source stays as it is. Ids come from list_maps.","read_only":false},{"name":"delete_map","title":"","description":"Remove a map from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_maps.","read_only":false},{"name":"update_calendar","title":"","description":"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 from list_calendars.","read_only":false},{"name":"delete_calendar","title":"","description":"Remove a calendar from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_calendars.","read_only":false},{"name":"update_report","title":"","description":"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 or an average needs a grouping. Ids come from get_reports.","read_only":false},{"name":"delete_report","title":"","description":"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.","read_only":false},{"name":"delete_action_rule","title":"","description":"Remove an automation (an action rule) from a table. Cannot be undone. Ids come from list_action_rules.","read_only":false},{"name":"list_maps","title":"","description":"The project's maps, each with its sources of markers and their ids (for update_map)","read_only":true}],"server_info":{"name":"quintadb","version":"1.0.0"},"category":"analytics","tags":["developer","communication","automation"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":971310,"score":100,"indexable":true,"first_seen":"2026-06-22","stars":0,"badges":["official"],"sponsor":null,"page":"https://agentsindex.org/agents/com-quintadb-mcp/"}