QuintaDB
REMOTE · QUINTADB.COM.UA
No-code databases, forms, portals and AI sites. Manage records and automation via natural language.
Available components
Last scanned (17 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Databases
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_record). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 31312 tokens (~196/item across 159 items; 159 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management96
- Stability check failed: schema churn in the 29 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 13 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 32 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 160 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Tool “delete_dashboard_item” rewrote its description, which is the text the model reads security
- “delete_dashboard_item” added an optional parameter “item_ids” cosmetic
- “delete_dashboard_item” reworded the description of “item_id” cosmetic
- “delete_dashboard_item” made “item_id” optional cosmetic
- 27 Oct 26 0
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- Tool “update_project” rewrote its description, which is the text the model reads security
- Tool “list_saved_views” rewrote its description, which is the text the model reads security
- Tool “create_field” rewrote its description, which is the text the model reads security
- Tool “update_dashboard_item” rewrote its description, which is the text the model reads security
- Tool “get_portal_page” rewrote its description, which is the text the model reads security
- Tool “create_report” rewrote its description, which is the text the model reads security
- Tool “get_record” rewrote its description, which is the text the model reads security
- Tool “import_records” rewrote its description, which is the text the model reads security
- Tool “list_site_blocks” rewrote its description, which is the text the model reads security
- Tool “export_records” rewrote its description, which is the text the model reads security
- Tool “run_action” rewrote its description, which is the text the model reads security
- Tool “delete_team_group” rewrote its description, which is the text the model reads security
- Tool “create_telegram_template” rewrote its description, which is the text the model reads security
- Tool “configure_chat” rewrote its description, which is the text the model reads security
- Tool “generate_ai_site” rewrote its description, which is the text the model reads security
- Tool “delete_template” rewrote its description, which is the text the model reads security
- Tool “create_whatsapp_template” rewrote its description, which is the text the model reads security
- Tool “delete_few_records” rewrote its description, which is the text the model reads security
- Tool “delete_form” rewrote its description, which is the text the model reads security
- Tool “list_portal_pages” rewrote its description, which is the text the model reads security
- Tool “seed_records” rewrote its description, which is the text the model reads security
- Tool “check_ai_site_status” rewrote its description, which is the text the model reads security
- Tool “get_rel_id” rewrote its description, which is the text the model reads security
- Tool “create_map” rewrote its description, which is the text the model reads security
- Tool “reorder_fields” rewrote its description, which is the text the model reads security
- Tool “create_project” rewrote its description, which is the text the model reads security
- Tool “generate_ai_project” rewrote its description, which is the text the model reads security
- Tool “update_field” rewrote its description, which is the text the model reads security
- Tool “create_portal_group” rewrote its description, which is the text the model reads security
- Tool “list_portal_users” rewrote its description, which is the text the model reads security
- Tool “create_record_template” rewrote its description, which is the text the model reads security
- Tool “delete_saved_view” rewrote its description, which is the text the model reads security
- Tool “update_cell” rewrote its description, which is the text the model reads security
- Tool “delete_project” rewrote its description, which is the text the model reads security
- Tool “get_metric” rewrote its description, which is the text the model reads security
- Tool “create_saved_view” rewrote its description, which is the text the model reads security
- Tool “bulk_update_records” rewrote its description, which is the text the model reads security
- Tool “update_portal_page” rewrote its description, which is the text the model reads security
- Tool “set_column_size” rewrote its description, which is the text the model reads security
- Tool “edit_site_block” rewrote its description, which is the text the model reads security
- Tool “duplicate_record” rewrote its description, which is the text the model reads security
- Tool “upload_file_to_record” rewrote its description, which is the text the model reads security
- Tool “get_field_types” rewrote its description, which is the text the model reads security
- Tool “get_relationship” rewrote its description, which is the text the model reads security
- Tool “list_projects” rewrote its description, which is the text the model reads security
- Tool “list_portals” rewrote its description, which is the text the model reads security
- Tool “list_schedules” rewrote its description, which is the text the model reads security
- Tool “list_forms” rewrote its description, which is the text the model reads security
- Tool “update_form_settings” rewrote its description, which is the text the model reads security
- Tool “create_portal” rewrote its description, which is the text the model reads security
- Tool “remove_user_from_portal_group” rewrote its description, which is the text the model reads security
- Tool “get_form_settings” rewrote its description, which is the text the model reads security
- Tool “search_records” rewrote its description, which is the text the model reads security
- Tool “delete_records_by_filter” rewrote its description, which is the text the model reads security
- Tool “update_relationship” rewrote its description, which is the text the model reads security
- Tool “list_dashboard_items” rewrote its description, which is the text the model reads security
- Tool “list_action_rules” rewrote its description, which is the text the model reads security
- Tool “get_report_data” rewrote its description, which is the text the model reads security
- Tool “duplicate_form” rewrote its description, which is the text the model reads security
- Tool “delete_portal_user” rewrote its description, which is the text the model reads security
- Tool “web_search” rewrote its description, which is the text the model reads security
- Tool “update_team_group” rewrote its description, which is the text the model reads security
- Tool “get_usage_stats” rewrote its description, which is the text the model reads security
- Tool “update_record_template” rewrote its description, which is the text the model reads security
- Tool “set_user_role” rewrote its description, which is the text the model reads security
- Tool “update_action_rule” rewrote its description, which is the text the model reads security
- Tool “delete_portal_group” rewrote its description, which is the text the model reads security
- Tool “search_image” rewrote its description, which is the text the model reads security
- Tool “delete_schedule” rewrote its description, which is the text the model reads security
- Tool “delete_reminder” rewrote its description, which is the text the model reads security
- Tool “add_record_comment” rewrote its description, which is the text the model reads security
- Tool “create_email_template” rewrote its description, which is the text the model reads security
- Tool “place_media_on_site” rewrote its description, which is the text the model reads security
- Tool “delete_portal_menu_item” rewrote its description, which is the text the model reads security
- Tool “update_form” rewrote its description, which is the text the model reads security
- Tool “get_records” rewrote its description, which is the text the model reads security
- Tool “list_user_roles” rewrote its description, which is the text the model reads security
- Tool “get_user_info” rewrote its description, which is the text the model reads security
- Tool “delete_record” rewrote its description, which is the text the model reads security
- Tool “remove_user_from_team_group” rewrote its description, which is the text the model reads security
- Tool “attach_media_to_record” rewrote its description, which is the text the model reads security
- Tool “list_webhooks” rewrote its description, which is the text the model reads security
- Tool “fetch_url” rewrote its description, which is the text the model reads security
- Tool “get_project” rewrote its description, which is the text the model reads security
- Tool “create_sms_template” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- “add_dashboard_item” reworded the description of “first_widget_id” cosmetic
- “delete_records_by_filter” reworded the description of “entity_id” cosmetic
- “create_action_rule” reworded the description of “on_create” cosmetic
- “create_field” reworded the description of “allow_new_values” cosmetic
- “edit_site_block” reworded the description of “html” cosmetic
- “create_field” reworded the description of “entries_num” cosmetic
- “upload_file_to_record” reworded the description of “record_id” cosmetic
- “add_dashboard_item” reworded the description of “second_widget_id” cosmetic
- “configure_chat” reworded the description of “portal_id” cosmetic
- “create_field” reworded the description of “name” cosmetic
- “get_records” reworded the description of “search” cosmetic
- “bulk_update_records” reworded the description of “record_ids” cosmetic
- “update_portal_page” reworded the description of “must_contain” cosmetic
- “set_table_permission” reworded the description of “entity_id” cosmetic
- “create_report” reworded the description of “total_by_group” cosmetic
- “list_dashboard_items” reworded the description of “portal_id” cosmetic
- “update_action_rule” reworded the description of “action_id” cosmetic
- “web_search” reworded the description of “query” cosmetic
- “export_records” reworded the description of “email” cosmetic
- “update_dashboard_item” reworded the description of “item_id” cosmetic
- “set_user_role” reworded the description of “email” cosmetic
- “create_field” reworded the description of “app_id” cosmetic
- “update_cell” reworded the description of “value” cosmetic
- “update_field” reworded the description of “script_body” cosmetic
- “update_field” reworded the description of “separator” cosmetic
- “create_saved_view” reworded the description of “sort_by” cosmetic
- “create_record_template” reworded the description of “name” cosmetic
- “set_user_role” reworded the description of “entity_id” cosmetic
- “create_report” reworded the description of “group_field_ids” cosmetic
- “import_records” reworded the description of “csv_text” cosmetic
- “get_report_data” reworded the description of “report_id” cosmetic
- “bulk_update_records” reworded the description of “filter” cosmetic
- “get_metric” reworded the description of “date_field” cosmetic
- “add_user_to_team_group” reworded the description of “move_from_other_groups” cosmetic
- “update_relationship” reworded the description of “show_column_id” cosmetic
- “create_field” reworded the description of “delimiter” cosmetic
- “update_action_rule” reworded the description of “app_id” cosmetic
- “update_form_settings” reworded the description of “dtype_added_text” cosmetic
- “create_field” reworded the description of “ampm” cosmetic
- “bulk_update_records” reworded the description of “report_id” cosmetic
- “create_field” reworded the description of “choices” cosmetic
- “update_field” reworded the description of “formula_type” cosmetic
- “update_portal_page” reworded the description of “embed_form” cosmetic
- “list_portal_users” reworded the description of “per_page” cosmetic
- “upload_file_to_record” reworded the description of “file_content” cosmetic
- “create_field” reworded the description of “func_fields” cosmetic
- “get_relationship” reworded the description of “field_id” cosmetic
- “set_table_permission” reworded the description of “view_record_history” cosmetic
- “update_action_rule” reworded the description of “entity_id” cosmetic
- “add_dashboard_item” reworded the description of “block_width” cosmetic
- “update_record” reworded the description of “subforms” cosmetic
- “create_field” reworded the description of “uniqueness” cosmetic
- “delete_field” reworded the description of “entity_id” cosmetic
- “create_field” reworded the description of “vertical_align” cosmetic
- “create_field” reworded the description of “icon” cosmetic
- “list_portal_users” reworded the description of “portal_id” cosmetic
- “add_user_to_team_group” reworded the description of “user_group_id” cosmetic
- “delete_field” reworded the description of “field_name” cosmetic
- “set_table_permission” reworded the description of “show_related_records” cosmetic
- “update_field” reworded the description of “precision” cosmetic
- “create_form” reworded the description of “name” cosmetic
- “create_portal_group” reworded the description of “tables_permissions” cosmetic
- “create_field” reworded the description of “entity_id” cosmetic
- “update_field” reworded the description of “position” cosmetic
- “add_user_to_portal_group” reworded the description of “move_from_other_groups” cosmetic
- “update_portal_page” reworded the description of “name” cosmetic
- “update_field” reworded the description of “cols” cosmetic
- “create_field” reworded the description of “matrix_rows” cosmetic
- “create_email_template” reworded the description of “from” cosmetic
- “import_records” reworded the description of “records” cosmetic
- “upload_file_to_record” reworded the description of “file_name” cosmetic
- “set_column_size” reworded the description of “size” cosmetic
- “create_report” reworded the description of “order” cosmetic
- “list_webhooks” reworded the description of “entity_id” cosmetic
- “update_form” reworded the description of “per_page” cosmetic
- “create_action_rule” reworded the description of “email_column” cosmetic
- “export_records” reworded the description of “report_id” cosmetic
- “update_action_rule” reworded the description of “new_name” cosmetic
- “update_action_rule” reworded the description of “update_fields” cosmetic
- “create_field” reworded the description of “linked_records_count_form_id” cosmetic
- “update_field” reworded the description of “currency_unit” cosmetic
- “create_record” reworded the description of “rels” cosmetic
- “create_field” reworded the description of “text_align” cosmetic
- “create_action_rule” reworded the description of “subject” cosmetic
- “set_table_permission” reworded the description of “revoke” cosmetic
- “update_field” reworded the description of “func” cosmetic
- “seed_records” reworded the description of “subforms” cosmetic
- “create_action_rule” reworded the description of “email_body” cosmetic
- “invite_portal_user” reworded the description of “login” cosmetic
- “create_report” reworded the description of “average_by_group_column_id” cosmetic
- “delete_few_records” reworded the description of “record_ids” cosmetic
- “create_field” reworded the description of “operation” cosmetic
- “add_portal_menu_item” reworded the description of “name” cosmetic
- “place_media_on_site” reworded the description of “page_checksum” cosmetic
- “update_field” reworded the description of “formula_link_column” cosmetic
- “create_report” reworded the description of “total_by_group_column_id” cosmetic
- “add_portal_menu_item” reworded the description of “position” cosmetic
- “delete_records_by_filter” reworded the description of “filter” cosmetic
- “update_portal_page” reworded the description of “page_checksum” cosmetic
- “create_team_group” reworded the description of “tables_permissions” cosmetic
- “create_field” reworded the description of “field” cosmetic
- “create_report” reworded the description of “only_groupname_and_count” cosmetic
- “delete_records_by_filter” reworded the description of “record_ids” cosmetic
- “create_field” reworded the description of “operand_is” cosmetic
- “update_portal_menu_item” reworded the description of “section_id” cosmetic
- “add_record_comment” reworded the description of “body” cosmetic
- “update_field” reworded the description of “field” cosmetic
- “create_field” reworded the description of “formula_link_to” cosmetic
- “update_field” reworded the description of “step” cosmetic
- “update_field” reworded the description of “func_fields” cosmetic
- 1 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://quintadb.com.ua/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.quintadb.com.ua | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 10 May 2026 | 24 Nov 2026 | RSA 2048 | SHA256-RSA | b2830a7a4c13d5dc8cb1751d27ee232e |
| SANs: *.quintadb.com.ua, quintadb.com.ua | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of quintadb.com.ua. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ua. | present | 51024, 51024 | 13, 13 | Verified |
| com.ua. | present | 43285 | 13 | Verified |
| quintadb.com.ua. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | ALLOWALL |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://quintadb.com.ua/mcp | Verified | 200 | |
| http (plaintext) | http://quintadb.com.ua/mcp | HTTPS enforced | 301 | https://quintadb.com.ua/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_dashboard_item ~683
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_widget_id, second_widget_id); 5=the account's files total; 6=the number of the portal's people. Several charts for a dashboard: create_dashboard_charts.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| block_height | integer | – | Height of the card in px |
| block_width | integer | – | Width of the card in the grid (1-12, bootstrap grid) |
| change_period | integer | – | For growth: 0 = yesterday vs the day before, 1 = this week vs last week, 2 = this month vs last month, 3 = quarter, 4 = year |
| currency | string | – | Currency symbol: $, €, ₴ and so on |
| currency_position | integer | – | 0 = before the number (default), 1 = after the number |
| date_property_id | string | – | ID or name of the date field — for growth_by_table (17), to count the records per period |
| first_widget_id | string | – | ID of the first dashboard widget for growth_by_widgets (18) — take it from a previous add_dashboard_item |
| icon | string | – | The icon's FontAwesome class (optional, chosen automatically if not given) |
| module_id | string | – | The table's or report's id (types 9–14, 17) / the chart's (2), map's (3) or calendar's (4) id |
| module_type | integer | yes | 2=chart, 3=map, 4=calendar, 9=table or report, 10=sum, 11=average, 12=count, 13=added today, 14=changed today, 15=link, 16=page, 17=growth by table, 18=growth between cards, 5=files total, 6=portal's… |
| name | string | yes | Widget name |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
| position | integer | – | Position in the grid (autoincrement if not given) |
| property_id | string | – | ID or name of the number field — for sum (10), average (11). For growth (17): the field that is counted. |
| second_widget_id | string | – | ID of the second dashboard widget for growth_by_widgets (18) |
| show_compare_period | boolean | – | Show the value for the compared period (default: false) |
| show_currency | boolean | – | Show the currency symbol next to the number |
| show_current_value | boolean | – | Show the current value next to the % of growth (default: true) |
No output schema declared.
No examples provided.
add_portal_menu_item ~406
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 the dashboard's cards on that home page (its first entry); otherwise the menu shows «Dashboard» by itself. A URL entry never points at the project's own address (/apps/<project>): people of the portal cannot open it.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| icon | string | – | The icon's FontAwesome class |
| module_ai_id | string | – | form_ID, table_ID, report_ID, map_ID, cal_ID, chart_ID, 'submenu' for a submenu group, or 'quintachat' for the project's inbox (QuintaChat: clients write to the business's Telegram bot or WhatsApp nu… |
| module_id | string | – | The real ID of the module (a form, report, map and so on). Not needed for a submenu group. |
| module_type | integer | – | Alternative to module_ai_id: 10=submenu, 12=URL, 13=HTML page |
| name | string | – | Menu item name |
| parent_section_id | string | – | ID of the parent submenu section (from list_portal_menu_items) — for sub-items |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
| position | integer | – | Position in the menu |
| url | string | – | URL for module_type=12 |
No output schema declared.
No examples provided.
add_record_comment ~56
Add a comment to a record.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| body | string | yes | Comment text |
| record_id | string | yes | Record ID (from get_records or search_records) |
No output schema declared.
No examples provided.
add_user_to_portal_group ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| string | yes | User email address | |
| move_from_other_groups | boolean | – | Remove from all other groups of this portal (default false) |
| portal_group_id | string | yes | Group ID (from list_portal_groups or create_portal_group) |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
| send_email | boolean | – | Mail the portal's invitation letter to a NEW account (default true). false: nobody is told a password — the person sets their own from the portal's sign-in page. |
No output schema declared.
No examples provided.
add_user_to_team_group ~209
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 full move into this group).
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| string | yes | User email address | |
| move_from_other_groups | boolean | – | Remove the user from all other groups and reset their individual roles (default false) |
| send_email | boolean | – | Mail the invitation letter to a NEW account (default true). false: nobody is told a password — the person sets their own from the sign-in page. |
| user_group_id | string | yes | Group ID (from list_team_groups or create_team_group) |
No output schema declared.
No examples provided.
attach_media_to_record ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form ID |
| field_id | string | yes | ID of a field of type file or image |
| my_file_id | string | yes | media_id of the attached MyFile |
| record_id | string | yes | Record ID |
No output schema declared.
No examples provided.
bulk_update_records ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| fields_to_set | object | yes | Fields to update: {"Field name" or field_id: "new value"}. For example: {"Status": "Processed", "Priority": "Low"} |
| filter | object | – | Filter by one field: {field: "Field name", value: "value"}. For example: {field: "Status", value: "New"} |
| record_ids | array | – | The specific record IDs to update. If not given, filter or report_id or all records are used. |
| report_id | string | – | Report/filter ID — updates only the records in this report |
No output schema declared.
No examples provided.
check_ai_site_status ~72
Check the status of an AI site generation. Call it every 10-15 s after generate_ai_site. Returns: pending / success / error.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
No output schema declared.
No examples provided.
configure_chat ~169
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...'}.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| channels | object | – | Contact channels. Available keys: whatsapp, telegram, messenger, viber, email, phone, instagram, snapchat, line, vk, sms, slack, skype, apple, linkedin, twitter, map, waze, tiktok, envelope, link. Th… |
| portal_id | string | – | Portal ID (optional — if not given, the first portal is used) |
No output schema declared.
No examples provided.
create_action_rule ~548
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 one you compose.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| conditions | array | – | Conditions under which the rule fires |
| do_not_send_data_if_criteria_matches | boolean | – | true = when the conditions match, the record is NOT saved and the person filling in the form reads `message` instead (the automation page's «Do not submit data to table if criteria matches»). For «do… |
| email_body | string | – | Email body |
| email_column | string | – | Name or ID of the field with the recipient's email |
| emails | string | – | Addresses the mail always goes to, comma-separated. "me" = the person you are talking to (their own account's address): «email me», «notify me», «let me know» — never ask them for it. The answer's em… |
| entity_id | string | yes | Form ID |
| message | string | – | The text the person reads: after the save (show_message) or instead of it (do_not_send_data_if_criteria_matches) |
| name | string | yes | Rule name |
| numbers | string | – | Written phone numbers the text always goes to, comma-separated — only when it is NOT a number from the record |
| on_create | boolean | – | Fires when a record is created |
| on_update | boolean | – | Fires when a record is updated |
| redirect | boolean | – | – |
| send_email | boolean | – | – |
| send_sms | boolean | – | – |
| show_message | boolean | – | Show `message` AFTER the record is saved. It refuses nothing. |
| sms_body | string | – | SMS text |
| sms_column | string | – | Where the text goes when each record has its own number: the name or id of the field of this form that holds the phone (the client's phone). Use this for «text the client». |
| subject | string | – | Email subject |
| update_fields | array | – | Fields to update (when update_record=true) |
| update_record | boolean | – | – |
| url | string | – | URL to redirect to |
No output schema declared.
No examples provided.
create_calendar ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| data_sources | array | – | – |
| name | string | yes | Display name |
No output schema declared.
No examples provided.
create_chart ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| axis_l | string | – | mth = the values of the property_id field; field = the choices of the property_id field |
| data_sources | array | – | The series (lines or bars) |
| entity_id | string | – | The table of the X axis |
| name | string | yes | Display name |
| order | string | – | asc or desc |
| property_id | string | – | The field along the X axis (id or name) |
| type_code | string | yes | line, bar, column, pie, doughnut, area, scatter |
| y_axis_title | string | – | – |
No output schema declared.
No examples provided.
create_dashboard_charts ~197
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 table or a field that is not there, a series over a field that holds no number, or a name the project's charts already have makes nothing, and the answer says which. Up to 30 charts.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| charts | array | yes | – |
| portal_id | string | – | The portal whose dashboard gets the cards; may be left out when the project has one portal |
No output schema declared.
No examples provided.
create_email_template ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| body | string | yes | The email's HTML body |
| email_column_id | string | – | Name or ID of the field with the recipient's email (note: NOT html_name, but the name or id itself) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| from | string | – | Sender address |
| name | string | yes | Display name |
| recipient_source | integer | – | 0 = the given addresses, 1 = from a field of the form |
| reply_to | string | – | – |
| subject | string | yes | Email subject (use the fields' html_name without brackets) |
No output schema declared.
No examples provided.
create_field ~2,387
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/radio ALWAYS pass choices in the SAME call — without them the field is not created.
| Name | Type | Req | Description |
|---|---|---|---|
| action_color | integer | – | action field: 0=primary,2=success,3=danger,6=light(default) |
| action_display_rules | array | – | Rules for when the Action button is shown. For all records — do not pass this array. |
| action_done_message | string | – | action field: the message after the task is done |
| action_fill | integer | – | action field: 0=inline(default), 1=block |
| action_name_column_id | string | – | action: the id of the field of this form whose value is the button's caption — with action_name_from_column true |
| action_name_from_column | boolean | – | action: the button's caption is taken from a field of the record (action_name_column_id) instead of the field's name |
| action_size | integer | – | action field: 0=small,1=medium(default),2=large |
| action_tasks | array | – | Tasks of an Action field (field_type=action). task_type: 0=email, 1=sms, 2=update_record, 3=payment, 4=webhook, 5=open_form_or_url, 6=telegram/whatsapp. The full specification — get_field_types. |
| action_type | integer | – | action field: 0=link(default), 1=button |
| add_percent_to_number | boolean | – | Add a % sign after the number |
| add_to_actions_control | boolean | – | action: add to the bulk actions menu |
| allow_new_values | boolean | – | For select only. true — users can add new options right from the record form, without editing the field. Default false. |
| ampm | boolean | – | true — 12-hour format (AM/PM) for time/datetime |
| app_id | string | yes | Project ID |
| average_table_column | string | – | Not for an average over the rows linked to this record: their sum (linked_records + linked_column) divided by a linked_records_count. formula_type average is refused by this tool. |
| average_table_ref_column | string | – | formula_type average: the link field in that other table that points at this form, by id or name; may be left out when only one table links here |
| choices | array | – | REQUIRED for select/checkbox/radio: an array of options. A call WITHOUT choices is refused with an error — do not make it; pass the options at once (take them from the user's words or propose sensibl… |
| column | string | – | REQUIRED for linked_column: the id of the field of the LINKED table that this column shows — «show the activity's description in the registration form» is a linked_column on Registrations with column… |
| currency_unit | string | – | Currency symbol: '$', '€', '₴' and so on |
| default | string | – | Default value (for select — one of the choices) |
| default_type | integer | – | 0 = fixed, 1 = current date/time (date/datetime), 2 = current user (record_owners) |
| delimiter | string | – | Thousands separator: '' or ',' or '.' |
| dependent | boolean | – | rel only: true — the list offers only the rows linked to what another field of the same form holds (Country → City, Stage → Check point); give depends_from_field_id with it. get_field_types with fiel… |
| depends_from_field_id | string | – | rel only: the field of the same form (name or id) whose pick narrows this list — itself a link to a table that the linked table links to as well |
| desc | string | – | A tooltip hint for the person filling in the form |
| disable_future | boolean | – | Forbid choosing future dates (for date/datetime/dob) |
| disable_past | boolean | – | Forbid choosing past dates (for date/datetime/dob) |
| display_as_image | boolean | – | true — show the URL as a picture (field_type=url only, for photos) |
| entity_id | string | yes | Form ID |
| entries_num | integer | – | Number of linked records for linked_records (default 5) |
| field | array | – | Array of field IDs or constants ['Constant', 'text'] for formula_type=formula |
| field_type | string | yes | Field type. Call get_field_types for the full list with descriptions. |
| formula_link_column | string | – | formula_type=link: ID of the field with the table/form name |
| formula_link_target | string | – | formula_type=link: _blank, _self, _parent, _top |
| formula_link_to | string | – | formula_type=link: on_table or table_form |
| formula_type | string | – | Formula type: formula (arithmetic/concatenation), function (built-in functions + Ruby), link (clickable link), total (sum), average (average). REQUIRED for field_type=formula. |
| func | integer | – | Function for formula_type=function: 0=MIN, 1=MAX, 2=ROUND_UP, 3=ROUND_DOWN, 4=Ruby script |
| func_fields | array | – | IDs of all fields used in func/script_body. REQUIRED for formula_type=function — without it the formula is not recalculated. |
| hide_column_name | boolean | – | action/formula: hide the column's name in the table |
| icon | string | – | action field: the icon's FontAwesome class |
| icon_align | integer | – | action: where the icon stands beside the caption — 1 left (default), 2 right |
| is_currency | boolean | – | Show as currency |
| linked_entity_id | string | – | The id of the other table: for linked_records / linked_records_count, and for a subform the table whose rows are filled in inside this form. A linked_column names its table by its column |
| linked_records_count_form_id | string | – | ID of the form to count (required for field_type=linked_records_count) |
| matrix_columns | array | – | Matrix columns (field_type=matrix) |
| matrix_rows | array | – | Matrix rows (field_type=matrix) |
| name | string | yes | Field name |
| not_add_space_between_operands | integer | – | 1 = no space between the operands (for concatenation without spaces) |
| operand_is | string | – | Operand type for formula_type=formula: numbers, decimal, text, days, hours, year. REQUIRED when formula_type=formula. |
| operation | array | – | Operators between the fields: +, -, *, / (one fewer than the number of fields) |
| precision | integer | – | Digits after the decimal point for float (default 2) |
| rel_entity_id | string | – | ID of the form the rel field links to (required for rel) |
| rel_show_field_id | string | – | ID of the field to show in the rel dropdown (optional) |
| rel_type | integer | – | Link type (default 2): belongs_to=2/6/8 (dropdown/radio/multi), has_one=3/5/9 (dropdown/radio/multi), many-to-many=1/4 (autocomplete/checkboxes) |
| required | boolean | – | true — the field must be filled in |
| rich | boolean | – | true — a text editor (for field_type=textarea) |
| script_body | string | – | Ruby code for func=4. Rules: the result goes into the variable 'a', the last line is 'a'; field names in single quotes 'field_name'.to_f; def/while/puts/return/require are forbidden; aggregating subf… |
| separator | string | – | Decimal separator: '.' or ',' |
| settings | object | – | Any other setting of the field, as setting: value pairs in the product's own names — totals and averages under a column, barcode / QR code, an input mask, several files at once, a list's options side… |
| start_from | integer | – | Starting value of the autoincrement (default 1) |
| step | integer | – | Step of the autoincrement (default 1) |
| text_align | integer | – | Alignment in the cell: 1=left, 2=right, 3=center, 4=justify |
| time_settings | object | – | time field: how the time is picked. clock_system "12h" | "24h"; control_type "dropdown" | "slider"; units: { hour | minute | second | millisec | microsec: { show: true|false, min, max, step, grid } }… |
| total_table_column | string | – | Not for a sum over the rows linked to this record — that is a linked_records field and a linked_column over it (937). formula_type total is refused by this tool. |
| total_table_ref_column | string | – | Not for a sum over the rows linked to this record (see total_table_column). |
| truncates_after | integer | – | Cut the text in the table after N characters (default 1000) |
| uniqueness | object | – | Check that the field's values are unique. |
| validations | object | – | The field's checks. required: true is the shorter way to make it required. They check the text typed into the add or edit form, in the browser: none reads a date's weekday, a holiday, opening hours o… |
| vertical_align | integer | – | Vertical alignment: 1=top, 2=middle, 3=bottom |
| visible | boolean | – | false — the field's column is not shown on the table's PUBLIC page (the page, a found record, one record's own page). Signed in, the owner still sees it in their own table and in the form. For a publ… |
No output schema declared.
No examples provided.
create_folder ~142
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 only groups that list: the person moves items into it themselves, on that page — you cannot put anything into a folder, rename one or remove one. Refused where the site has no page for that list.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | – | Only with module reports: the table whose reports the folder groups |
| module | string | yes | The list the folder groups |
| name | string | yes | Display name |
No output schema declared.
No examples provided.
create_form ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID |
| name | string | yes | Form name |
No output schema declared.
No examples provided.
create_formatting ~735
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 compares a field with a written value, never with another field: for «under its minimum», «over its limit» first create_field a formula that subtracts one from the other, then put the rule on that field (less_than 0) — both in this turn, without asking. It shows in the table view; the form editor has no per-field font size. ⚠️ The rule's name is its key within the form: a call with the same name REWRITES that rule (status: updated), it does not add a second one — give a second rule another name.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | true = every row, false = only rows that match the conditions |
| app_id | string | yes | Project ID (from list_projects) |
| conditions | array | – | Conditions (when all=false). A condition is one of: is, is_not, is_empty, is_not_empty, starts_with, ends_with, like, contains, not_contains, less_than, greater_than, less_than_or_equal_to, greater_t… |
| criteria_name | string | – | The conditions in words (e.g. 'Amount over 1000'). Required when all=false. |
| entity_id | string | yes | ID of the form or report |
| name | string | yes | The rule's name |
| property_ids | array | – | Names or IDs of the fields the style applies to (empty = all columns) |
| settings | object | – | The style: background_color (#hex), text_color (#hex), bold, italic, underline, strike (boolean), font_family, font_size (a number of px), all_columns (boolean) |
No output schema declared.
No examples provided.
create_map ~130
Create a Google Maps map with data sources (markers from forms). center_type: 1 = address, 2 = coordinates, 3 = first record.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| center_address | string | – | Address of the center (for center_type=1) |
| center_latitude | number | – | – |
| center_longitude | number | – | – |
| center_type | integer | – | 1 = address, 2 = coordinates, 3 = first record |
| data_sources | array | – | – |
| name | string | yes | Display name |
No output schema declared.
No examples provided.
create_portal ~226
Create a new portal for the project. A portal is the client-facing interface with a menu, a dashboard and access rights.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| color | integer | – | Color: 0=White, 1=Black, 2=Grey (design/legal), 3=Blue (corporate/banks), 4=Green (agro/medicine), 5=Orange (logistics/restaurants), 6=Red (cars/entertainment). Strictly 0-6. |
| default_permissions | integer | – | 0 = public, 1 = registered users only, 3 = a group |
| name | string | yes | Portal name |
| theme | integer | – | Theme: 0=Standard/Minimalist, 1=Professional, 3=Professional Opened (CRM/ERP), 4=Professional Wide, 9=Fullscreen, 11=Carbon (dark), 13=Right List, 15=Jalousie. Do NOT use theme:2. |
No output schema declared.
No examples provided.
create_portal_group ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| is_default | boolean | – | true = this group is the default one for new sign-ups in the portal |
| name | string | yes | Group name |
| portal_id | string | yes | Portal ID (from create_portal) |
| tables_permissions | array | – | Access rights on tables/reports. They need not be passed here; they can be added later through set_table_permission with portal_group_id |
No output schema declared.
No examples provided.
create_portal_page ~159
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_item for it. For a page that shows the project's forms or tables use generate_ai_site instead.
| Name | Type | Req | Description |
|---|---|---|---|
| add_to_menu | boolean | – | false = create it without a menu item (default true) |
| app_id | string | yes | Project ID (from list_projects) |
| html | string | yes | The page's content: headings, paragraphs, lists (or a whole HTML document) |
| name | string | yes | Display name |
| portal_id | string | – | From list_portals; may be left out when the project has one portal |
No output schema declared.
No examples provided.
create_project ~85
Create a new project (database) with its first form. After creating it, add fields through create_field.
| Name | Type | Req | Description |
|---|---|---|---|
| form_name | string | – | Name of the first form (default 'Main') |
| name | string | yes | A short project name (2-4 words, not the idea, not a description). Examples: 'Family budget', 'Client CRM', 'Stock tracking'. |
No output schema declared.
No examples provided.
create_record ~488
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 is LEFT OUT — also for a field marked required: the row is made without it and the answer names it in left_empty; never ask for such values before making the rows and never invent them. The answer's 'linked' says which row each link of the new record points at, in that row's own words — read it: when it is not the row you meant, correct the link with update_record. IF the parent record is already known (the person says 'add a record to this child form from this record' / 'create a Registro for this Commessa') — pass the link to the parent AT ONCE through 'rels' in THIS call. Do NOT create an empty record and do NOT switch fields' visibility hoping the link fills itself in — it will not.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| data | object | – | The record's fields: { key: value }. A key is the field's id (e.g. "a5tfWHm8jcW47cVcSbW6Sy"), its name or its html_name, as describe_project or get_form_fields show them. |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| rels | object | – | Rel fields (links): { "rel field's field_id": "ID of the record to link to" }. The key is the rel field's ID, the value is the linked record's ID. |
| subforms | object | – | Subform fields: { "subform field's field_id": { "form_id": "subform ID", "records": [{"field_id": "value"}] } }. NOTE: records must be an array of OBJECTS (hashes), not an array of numbers or IDs! |
| values | object | – | Alias for data — can be used instead of data (as in update_record) |
No output schema declared.
No examples provided.
create_record_template ~246
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 specification. Do not miss it: such a request often stands in the FIRST description and gets lost among the entities and fields. Put a field's 'html_name' into body WITHOUT any brackets (e.g. Full Name). Get html_name through get_form_fields. If this form already has a template with this name, it returns an error — use update_record_template.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| body | string | yes | The template's HTML body (use the fields' html_name as plain text, without brackets) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| name | string | yes | Template name |
No output schema declared.
No examples provided.
create_reminder ~636
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 = after it) — or REPEATING (repeat: every_day, every_week, every_month, every_year). every_day goes out every day for EVERY record the reminder reads, whatever the date, and is REFUSED without a report: for «every day until it is done» or «every day during the notice period» first make a report of the table whose filter keeps exactly the records that are due (create_report: the tick not set, the date within the next N days) and pass it as report_id — a record that leaves the report stops getting the mail. WHO GETS IT is one of three: recipients (written addresses), email_field (the address is read from a field of each record: an e-mail field, a linked column that shows one, a link whose shown column is an e-mail), or neither = the record's owner. An address kept in ANOTHER table the record links to (the client's, the company's): add a linked column that shows it to this table first, then pass that column as email_field. The answer says in words who gets it, when and for which records — tell the person that.
| Name | Type | Req | Description |
|---|---|---|---|
| all_records | boolean | – | Only with repeat every_day and no report: true = the person asked for EVERY record of the table, every day |
| app_id | string | yes | Project ID (from list_projects) |
| beside_existing | boolean | – | Only after the tool answered that the table already has a reminder repeating this way: true = the person wants one MORE beside it. To change the one they have, use update_reminder |
| date_field | string | yes | The date field's name or id — a date field of THIS table (entity_id). A date kept in another table: make the reminder on that table |
| days_before | integer | – | How many days before the date (0 = on the day, negative = after it); not read by repeat every_day |
| email_field | string | – | A field of the table (name or id) each record's address is read from |
| email_template_id | string | – | – |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| recipients | array | – | Written e-mail addresses — or email_field, not both. The word "me" = the address of the person you are talking to («remind me», «write to me»): never ask them for it |
| repeat | string | – | every_day | every_week | every_month | every_year; leave out for once per record |
| report_id | string | – | A report of the table (id or name): only its records are read; leave out for the whole table. repeat every_day is refused without it |
| run_time | string | – | HH:MM, 24 hours (default 08:00) |
| time_zone | string | – | – |
No output schema declared.
No examples provided.
create_report ~640
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| asc | boolean | – | true = ascending (default), false = descending. Applies to sort_by. |
| average_by_group | integer | – | 1 = show the average of a number field for each group. average_by_group_column_id must be given. |
| average_by_group_column_id | string | – | ID or name of the number field whose average per group is counted. |
| criterias | array | – | Filter conditions. For dates: yesterday, today, today_or_later, before_today, last_7_days, last_30_days, last_60_days, this_week, this_month, next_7_days, next_30_days, next_60_days, next_90_days, ne… |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| group_field_ids | array | – | IDs of the fields to group by (GROUP BY). For example, group by status. |
| name | string | yes | Report name |
| no_data_text | string | – | The text the owner sees when NO record matches the report's filters. ⚠️ ALWAYS write it for reports with a filter — a new project has no records yet, so this report is first shown empty. In the user'… |
| only_groupname_and_count | integer | – | 1 = show only the group's name and its number of records (no details) |
| order | string | – | asc or desc — the sort direction of the GROUPS (only when group_field_ids is given). This is NOT a sort field — use sort_by for that. |
| per_page | integer | – | Records per page (default 10) |
| property_ids | array | – | IDs or names of the fields shown (empty = all) |
| sort_by | string | – | ID or name of the field to sort the records by (used together with asc). |
| total_by_group | integer | – | 1 = show the sum of a number field for each group. total_by_group_column_id must be given. |
| total_by_group_column_id | string | – | ID or name of the number field whose sum per group is counted. |
No output schema declared.
No examples provided.
create_saved_view ~160
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_report). Do not call the result a report and do not offer it as a way to save the workspace's look/layout.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| filters | array | – | Array of filter conditions |
| name | string | yes | Display name |
| order_asc | boolean | – | true=ASC (default), false=DESC |
| sort_by | string | – | field_name or field_id to sort by |
No output schema declared.
No examples provided.
create_schedule ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| day | string | – | Monday … Sunday, or Daily (default) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| file_type | string | – | xls (default) | csv |
| name | string | – | The file's name (default: the table's name) |
| recipients | array | yes | Email addresses the file is mailed to |
| report_id | string | – | A report of this table — only its rows are sent |
| run_time | string | – | HH:MM, 24 hours (default 08:00) |
| time_zone | string | – | e.g. UTC+02 |
No output schema declared.
No examples provided.
create_sms_template ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| body | string | yes | SMS text (use the fields' html_name without brackets) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| name | string | yes | Display name |
No output schema declared.
No examples provided.
create_team_group ~212
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).
| Name | Type | Req | Description |
|---|---|---|---|
| access_to_only_own_files | boolean | – | – |
| app_id | string | yes | Project ID (from list_projects) |
| can_create_calendars | boolean | – | – |
| can_create_charts | boolean | – | – |
| can_create_maps | boolean | – | – |
| can_create_newsletters | boolean | – | – |
| can_create_portals | boolean | – | – |
| can_delete_files | boolean | – | – |
| can_upload_files | boolean | – | – |
| files_enabled | boolean | – | Access to files |
| has_access_to_team | boolean | – | – |
| name | string | yes | Group name |
| tables_permissions | array | – | Rights on forms/reports |
No output schema declared.
No examples provided.
create_telegram_template ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| body | string | yes | Message text (use the fields' html_name without brackets) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| name | string | yes | Display name |
No output schema declared.
No examples provided.
create_webhook ~325
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 automation of this table that calls it (list_action_rules; create_action_rule first for a new one: when it runs and its conditions). It sends ONLY what params lists: each a name and a field of the table, or a fixed text. The answer says who calls it, when, and what goes out.
| Name | Type | Req | Description |
|---|---|---|---|
| action_id | string | yes | The automation that calls this webhook — from list_action_rules or create_action_rule. One webhook per automation. |
| app_id | string | yes | Project ID (from list_projects) |
| auth_type | string | – | none (default), basic or bearer |
| basic_login | string | – | – |
| basic_password | string | – | – |
| bearer_token | string | – | – |
| content_type | string | – | json (default), form_data, form_urlencoded |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| headers | array | – | [{name, value}] |
| method | string | – | GET, POST (default), PUT, PATCH, DELETE |
| params | array | yes | What the call sends: [{name, property_id}] for a field's value (its id or name), [{name, custom_value}] for a fixed text. Nothing listed = an empty call. |
| url | string | yes | Where the call goes: starts with http:// or https:// |
No output schema declared.
No examples provided.
create_whatsapp_template ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| body | string | yes | Message text (use the fields' html_name without brackets) |
| channel_id | string | – | ID of the WhatsApp channel (q_channel). If not given, the project's first connected channel is used. |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| language_code | string | – | Language code, e.g. en_US, uk |
| message_type | string | – | WhatsApp template type |
| name | string | yes | Display name |
No output schema declared.
No examples provided.
delete_action_rule ~83
Remove an automation (an action rule) from a table. Cannot be undone. Ids come from list_action_rules.
| Name | Type | Req | Description |
|---|---|---|---|
| action_id | string | yes | The rule id from list_action_rules, as a string |
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
No output schema declared.
No examples provided.
delete_calendar ~58
Remove a calendar from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_calendars.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| calendar_id | string | yes | – |
No output schema declared.
No examples provided.
delete_chart ~57
Remove a chart from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_charts.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| chart_id | string | yes | – |
No output schema declared.
No examples provided.
delete_dashboard_item ~177
Remove cards (widgets) from a portal's dashboard — one or SEVERAL in ONE call: pass every card that goes in item_ids (all of them when the person asks for all; every card not kept when they keep only some). The person confirms them all on one card; nothing is removed before that. Every card must be on that dashboard, or nothing is removed and the answer names its cards. Only the cards go; the tables, reports and charts they showed stay.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| item_id | string | – | One card, from list_dashboard_items (item_ids takes several) |
| item_ids | array | – | Every card that goes, ids from list_dashboard_items |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
No output schema declared.
No examples provided.
delete_few_records ~62
Delete several records in one request
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| record_ids | array | yes | Array of record IDs to delete |
No output schema declared.
No examples provided.
delete_field ~127
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 one table or of several, or «keep only these fields» — call delete_fields ONCE with all of them instead: the person confirms them all at once.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID |
| entity_id | string | yes | Form ID |
| field_id | string | – | Field ID |
| field_name | string | – | Field name (takes priority over field_id) |
No output schema declared.
No examples provided.
delete_field_rule ~122
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. Asked to stop showing, hiding or filling a field «when…», find the rule in list_field_rules and remove that one — never several for one request. A rule cannot be changed: remove it and make it again (set_field_visibility_rule).
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| rule_id | integer | yes | From list_field_rules |
No output schema declared.
No examples provided.
delete_fields ~135
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). The fields may be of one table or of several. The person confirms them all on one card; nothing is removed before that. Every field must exist, or nothing is removed and the answer names the table's real fields. Irreversible — the data in these fields is lost.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID |
| fields | array | yes | Each field that goes: its table and the field by name or by its full id |
No output schema declared.
No examples provided.
delete_form ~58
Delete a form and all its records. Cannot be undone. The only form cannot be deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
No output schema declared.
No examples provided.
delete_formatting ~47
Remove a formatting rule. The person confirms it first.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| formatting_id | string | yes | From list_formattings |
No output schema declared.
No examples provided.
delete_map ~56
Remove a map from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_maps.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| map_id | string | yes | – |
No output schema declared.
No examples provided.
delete_portal ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| portal_id | string | yes | From list_portals |
No output schema declared.
No examples provided.
How do I install the QuintaDB MCP server?
QuintaDB is a hosted endpoint at https://quintadb.com.ua/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · quintadb.com.ua
claude mcp add --transport http ua-com-quintadb-mcp 'https://quintadb.com.ua/mcp'
What is the QuintaDB MCP server?
QuintaDB is an MCP server listed in the public MCP registry as ua.com.quintadb/mcp. No-code databases, forms, portals and AI sites. Manage records and automation via natural language. This page covers its hosted endpoint (https://quintadb.com.ua/mcp).
Is the QuintaDB MCP server safe to use?
QuintaDB scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the QuintaDB MCP server expose?
QuintaDB exposes 159 tools: list_projects, list_forms, get_form_fields, get_records, get_record, and 154 more. Their descriptions and schemas cost roughly 31,150 tokens of context every time the server is loaded.
Does the QuintaDB MCP server require authentication?
No. We connected to QuintaDB without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QuintaDB MCP server still maintained?
QuintaDB is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.