List your agent

QuintaDB

MCP server● Hosted · onlinev1.0.1

No-code databases, forms, portals and AI sites. Manage records and automation via natural language

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: query databases in plain language.
All AI agents to query databases in plain language, ranked →

Similar tools

Listed for the same task: query databases in plain language

Reviews

No review yet. Used QuintaDB? Be the first to help others choose.

What it does

QuintaDB is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: sql querying. That makes it a candidate for tasks such as query databases in plain language or build data pipelines.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.1
PriceNot in the registry
First seen26 Sept 2026
Last checked16h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)

Hosted endpoint

  • https://quintadb.ru/mcp streamable-http

In Claude Code: claude mcp add --transport http quintadb-1 https://quintadb.ru/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "quintadb-1": {
      "url": "https://quintadb.ru/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 2d ago

ONLINE QuintaDB answered an MCP connection on 14 Nov 2026 and introduced itself as quintadb 1.0.0 (MCP protocol 2025-06-18).

159 tools offered to AI assistants

  • list_projects · List all projects (databases) in the QuintaDB account
  • list_forms · List all forms (tables) in a project. List all forms, tables, entities in a project.
  • get_form_fields · The form's fields with names and types. ALWAYS call it before create_record and before building a newsletter, to know the exact names and html_name of the fields. A link field (rel) also says how many rows of this form hold a link (rows_lin
  • get_records · Get records of a form. Supports search and pagination
  • get_record · Get one record by ID
  • get_rel_id · Get the numeric rel_id for a field of type 'rel' (a link). Needed before create/update record when a rel field must be filled in. Pass the form's entity_id and the link field's property_id.
  • create_record · Create a new record in a form (insert row, add entry, new record). FIRST read the form's fields with describe_project or get_form_fields; the keys of 'data' are a field's id, its name or its html_name — any of the three those tools show; an
  • update_record · Change ONE existing record. Link fields go in 'rels', subform fields in 'subforms'. The answer says each cell's change — `changed` (was → now) and `unchanged`. A row holds one value per field: a second call on the SAME record_id replaces wh
  • delete_record · Delete a record
  • delete_few_records · Delete several records in one request
  • bulk_update_records · Update a field (or fields) in many records at once. Instead of N update_record calls for 'set status Processed on all of today's orders'. Records can be chosen by a list of IDs, by a filter (field = value), by a report, or all records of th
  • update_cell · Update the value of one field in a record without overwriting the other fields. ALWAYS use the field's ID, not its name.
Show 88 more
  • upload_file_to_record · Upload a file or image to a record's field. Takes the file's content in base64. Saves the file and attaches it to the given field. For multiple-file fields it adds to the existing files.
  • attach_media_to_record · Attach a file from the MyFile library to a field of type file or image of a specific record. Use it for attached_files instead of update_record when the field is of type file/image.
  • import_records · Import records in bulk from CSV or an array of objects. For the 'records' array ALWAYS use field IDs as keys.
  • search_records · Search/filter records (filter records, find entries, query data). Operators: is, is_not, contains, not_contains, starts_with, ends_with, is_empty, is_not_empty, gt, lt
  • get_column_total · The sum (or another aggregate) of a number field, as a number for your reply: it answers «how much is it in all». It puts nothing into the table — when the person wants a total SHOWN under the column, that is the field's own setting: update
  • get_metric · Get a real number from the database and return it to the user in the chat. metric_type: count (number of records), sum (sum of a number field), average (average), new_today (records added today), updated_today (records updated today), growt
  • run_action · Run an automation (action rule) for a record — send an email, trigger a webhook and so on. action_id is the ID of the action button field
  • get_reports · The project's reports (saved views of a table: filters, grouping, totals). Without entity_id: EVERY report of every table, each with its id and the table it belongs to — use this when the person names a report and not its table; never guess
  • get_report_data · Get the data of a specific report
  • seed_records · Seed a form with initial records in bulk. Use it to fill a form with test or reference data. For one record create_record is better. Supports subforms through subforms.
  • remove_example_records · Remove the sample records that project generation added — what the person calls «the examples», «les exemples», «приклади», «примеры», sample, demo or test data. Deletes ONLY the records the generator registered as examples; records the per
  • create_record_template · Create a RECORD template for printing/export (PDF/HTML) — that is, set HOW a record looks on paper or in a file: a blank to fill in by hand, a form, a delivery note, an act, a log, a checklist. 🚨 Call it when the user asks for a printed loo
  • update_record_template · Update an existing PDF/HTML record template (its name and/or body). Use this, not create_record_template, when the user asks to 'change'/'update' an existing print template — it keeps the template's ties to print buttons and the payment flo
  • list_record_templates · The record templates of a project or one table — the layouts ONE record is shown or printed with: each with its name, whether it is a record's page or a tile, and where it is in use now. Call it before update_record_template / delete_record
  • delete_record_template · Remove ONE record template, by its template_id from list_record_templates. The pages that showed a record with it go back to the standard layout; the answer says which. The records themselves are not touched.
  • create_email_template · Create an email template for mailing from a form. Put a field's 'html_name' into body and subject WITHOUT any brackets (just as text, for example: Hello, Full Name). Never use {{}} or []. Get html_name through get_form_fields.
  • create_sms_template · Create an SMS template for mailing. Put a field's 'html_name' into body WITHOUT any brackets (e.g. Full Name). Get html_name through get_form_fields.
  • create_telegram_template · Create a Telegram message template. Put a field's 'html_name' into body WITHOUT any brackets (e.g. Full Name). Get html_name through get_form_fields.
  • create_whatsapp_template · Create a WhatsApp message template. Put a field's 'html_name' into body WITHOUT any brackets (e.g. Full Name). Get html_name through get_form_fields.
  • create_formatting · Style a table's or report's columns: font size (px), font family, text and background colour, bold, italic, underline, strike — for the chosen fields (property_ids; empty = all columns), on every row (all=true) or only on rows that match co
  • create_team_group · Creates a team group (the internal back office) with rights on forms and reports. tables_permissions gives access at creation: an array of table (the id or name of a form or report), role (the numbers are in its own description), only_own_r
  • list_team_groups · List back-office team groups (roles, members, permissions). (get team groups, show staff groups)
  • add_user_to_team_group · Add a person to a team group by email. An account is created when there is none. The new account gets a password of its own, which only the invitation letter shows (with a one-time link that signs the person in); the answer's `invitation` s
  • remove_user_from_team_group · Remove a user from a team group. Pass user_id or email.
  • update_team_group · Change a team group's POWERS (and its name). These are not rights on tables — those are set_table_permission. Here is what a person may DO in the project: manage the team (can_add_users / can_edit_access_rights / can_delete_users), create p
  • delete_team_group · Delete a team group together with all its rights and members.
  • list_portal_groups · List a portal's user groups: members, and for each table or report the group has rights on — its role and whether the group sees only its own records (`tables`). Read it before changing who sees what: the group you need usually exists alrea
  • add_user_to_portal_group · Add a person to a portal group by email. An account in the portal is created when there is none. The new account gets a password of its own, which only the invitation letter shows (with a one-time link that signs the person in); the answer'
  • remove_user_from_portal_group · Remove a user from a portal group. Pass user_id or email.
  • delete_portal_group · Delete a portal group together with its rights and members.
  • set_table_permission · What a group (team or portal) may do on a table or report, and whether its people see ONLY THEIR OWN records there. For a group that already has rights on the table pass ONLY what the person asked to change: «technicians see only their own
  • create_action_rule · Create an automation (action rule) of a form. It runs on_create / on_update and does: send_email, send_sms, update_record, redirect, show_message — or, with do_not_send_data_if_criteria_matches, REFUSES the record. It can carry conditions a
  • create_report · Create a report (filter/view) for a form. Supports filter conditions, grouping, the sum/average per group, visible columns, sorting. For dates: yesterday, today, last_7_days, last_30_days, this_month, this_week, between (+ from/to), before,
  • create_project · Create a new project (database) with its first form. After creating it, add fields through create_field.
  • create_form · Create a new, EMPTY form (table) in an existing project; add its fields with create_field after it. A table made of what a column already holds — a dropdown's options, the stages, suppliers or categories named on the rows, the parents a lis
  • create_field · Add a field to a form. Types: text, textarea, integer, float, date, datetime, email, phone, url, select, checkbox, radio, file, image, location, autoincrement, yes_no, rel, formula, linked_column, linked_records, subform, map, action, divid
  • update_field · Change/rename a form field (rename field, edit property, update column). Name, description, position, options for select/radio, default value, required, sizes, uniqueness. Does not change the field's type.
  • get_field_types · The full reference of QuintaDB field types with descriptions of their parameters. Call it before create_field when a formula, linked_column, rel or any non-standard type is needed. Returns all 40+ types and the detailed specification of for
  • get_quickstart_guide · QuintaDB domain knowledge guide. Call this at the start of a session to learn field types, rel/linked_column rules, validation syntax, portal theme/color codes, and the correct workflow for building or modifying a project. Essential for ext
  • describe_project · The project's whole schema: every form, its fields with types and choices, the number of records, and the portals. A link field (rel) names the table it links to (links_to) and how many rows hold a link (rows_linked), and, when there are an
  • create_portal_group · Create a group of portal users and set its access rights on forms/reports. Use it after create_portal. Call set_table_permission with portal_group_id for rights on a particular table, or pass tables_permissions right here.
  • configure_chat · Set up the contact buttons (chat widget) in a portal — WhatsApp, Telegram, email, phone, Instagram and so on. Pass channels as an object {whatsapp: '+380...', telegram: '@mybot', email: 'info@...', phone: '+380...'}.
  • create_portal · Create a new portal for the project. A portal is the client-facing interface with a menu, a dashboard and access rights.
  • add_portal_menu_item · Add a portal menu entry. Top-level: module_ai_id + module_id. A submenu group: module_ai_id='submenu' + name (no module_id). An entry inside it: parent_section_id + module_ai_id + module_id. module_ai_id kinds: form_ID/table_ID = a form, re
  • list_portal_menu_items · The portal's menu: its top-level items, each with the items inside it (`submenu_items`) — a top-level item may open a table AND hold items. `position` is the place in the list, 0 = first. Call it before a rename, a move, a delete or a modul
  • update_portal_menu_item · Update a portal menu item: rename it, change its module, icon, place or URL. Give section_id (a top-level item) or item_id (an item inside a section) from list_portal_menu_items. To MOVE an item, give `position`: the place it must stand at
  • delete_portal_menu_item · Delete a portal menu item. section_id for a top-level item, item_id for a submenu item.
  • list_dashboard_items · List the widgets of the portal's dashboard (id, name, type, position, icon). Needed to find a widget's id before update_dashboard_item — for example when translating the project's interface into another language.
  • update_dashboard_item · Change the NAME (the card's caption), the icon or the position of a dashboard widget. ⚠️ Dashboard captions are separate from table names: renaming forms does NOT touch them, so when the project's interface is translated the dashboard must
  • add_dashboard_item · Add a card to a portal's dashboard. Types (module_type): 2=a chart, 3=a map, 4=a calendar (module_id: its id); 9=a table or report; 10=the sum of a field; 11=the average of a field; 12=the number of records; 13=records added today; 14=recor
  • create_dashboard_charts · Make several charts at once and put each on a portal's dashboard as a card: «make me a dashboard», «a chart for each metric». ONE call for all of them. Each chart: a name, a type, its table, the field along the X axis (a date or a number fi
  • list_portal_users · List of the portal's users (clients registered in the portal)
  • invite_portal_user · Invite a new person into a portal: creates their account and mails the portal's invitation letter. The new account gets a password of its own, which only the invitation letter shows (with a one-time link that signs the person in); the answe
  • update_portal_user · Change a person's account in a portal: their email address, login, first name, last name or phone. Pass only what the person asked to change; nothing else is touched. The answer says CHANGED (was → now) / UNCHANGED per item. A password is N
  • send_portal_user_password_letter · Mail a person in a portal the portal's own letter with a link where they set a new password themselves (the link works for one day; their present password keeps working until then). For «reset X's password», «X forgot the password», «X cann
  • delete_portal_user · Remove a user from a portal
  • list_charts · The project's charts, each with the series it shows and their ids (for update_chart)
  • create_chart · Create ONE chart. type_code: line, bar, column, pie, doughnut, area, scatter. The X axis comes from a field of the table (property_id): axis_l mth puts each record's value of that field along it (a date, a number, a name — not «by month»),
  • update_chart · Change a chart: its name, its type (pie, doughnut, line, area, bar, column, scatter) or the title of its vertical axis. Pass only what changes. `add_data_sources` adds series and `remove_data_source_ids` removes series by the ids list_chart
  • delete_chart · Remove a chart from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_charts.
  • update_map · Change a map: its name, where it is centred (center_type 1 = an address, 2 = coordinates, 3 = the first record) and its zoom. Pass only what changes. `add_data_sources` adds sources of markers and `remove_data_source_ids` removes sources by
  • delete_map · Remove a map from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_maps.
  • update_calendar · Change a calendar: its name, or whether it shows Saturdays and Sundays (weekends). Pass only what changes. `add_data_sources` adds sources of events and `remove_data_source_ids` removes sources by the ids list_calendars shows (798); every o
  • delete_calendar · Remove a calendar from the project and from every portal menu that shows it. Cannot be undone. Ids come from list_calendars.
  • update_report · Change a report: its name, its filters, the columns it shows, how it is sorted, how many records a page holds. Pass only what changes. `criterias` REPLACES all the report's filters. `group_field_ids` REPLACES its grouping (798): an empty li
  • delete_report · Remove a report from its table and from every portal menu that shows it. The table and its records stay. Cannot be undone. Ids come from get_reports.
  • delete_action_rule · Remove an automation (an action rule) from a table. Cannot be undone. Ids come from list_action_rules.
  • list_maps · The project's maps, each with its sources of markers and their ids (for update_map)
  • create_map · Create a Google Maps map with data sources (markers from forms). center_type: 1 = address, 2 = coordinates, 3 = first record.
  • list_calendars · The project's calendars, each with its sources of events and their ids (for update_calendar)
  • create_calendar · Create a calendar with data sources (events from forms). date_title_type: 0=fixed text, 1=from a field. info_window_type: 0=fixed text, 1=from a field.
  • list_portal_pages · List of the portal's HTML pages (landing pages, AI pages). Shows which one is the default.
  • get_portal_page · Get the HTML content of a portal page. If page_id is not passed, the portal's default page is used; if it cannot be told for sure, call list_portal_pages first. The HTML is cut so as not to overload the context.
  • generate_ai_site · Generate or update the portal's AI landing page. An asynchronous operation — check the status through check_ai_site_status. For a redesign pass existing_html from get_portal_page.
  • check_ai_site_status · Check the status of an AI site generation. Call it every 10-15 s after generate_ai_site. Returns: pending / success / error.
  • generate_ai_project · Generate a whole project with forms and reports from a text description
  • delete_field · Delete ONE field (column, property) from a form. Irreversible — all data in this field will be lost. (remove field, drop column) To remove SEVERAL fields — of one table or of several, or «keep only these fields» — call delete_fields ONCE wi
  • delete_fields · Delete SEVERAL fields in ONE call — whenever the person asks to remove more than one field, or to keep only some fields of a table (pass every field that goes). The fields may be of one table or of several. The person confirms them all on o
  • list_action_rules · Return all automation rules of a form with their conditions and update fields (update_fields). id is a string; pass it to update_action_rule as it is.
  • update_action_rule · Change an existing automation rule of a form: the trigger (on_create/on_update), the actions (send_email/update_record/…), the email, and above all the CONDITIONS and the UPDATE FIELDS (update_fields). A conditions/update_fields list that i
  • delete_records_by_filter · Delete records in bulk by a filter, a list of IDs, or all records of the form. Cannot be undone.
  • update_form · Change a form's name, description or settings.
  • delete_form · Delete a form and all its records. Cannot be undone. The only form cannot be deleted.
  • duplicate_form · Copy a form with its fields, settings and records. An asynchronous operation (~10 s).
  • split_column_into_table · Move what a column repeats into a table of its own: ONE record of a new table per different value of the column (a supplier, a client, a category named on many rows), made from the values the table already holds — never invented — and a lin
  • export_records · Export a form's records to XLSX or PDF and send them by email.
  • list_record_comments · The comments on one record, oldest first: each with its id, its text, who wrote it and `yours` — whether the person you are talking to wrote it (only then can it be changed or removed).
  • add_record_comment · Add a comment to a record.

The first 100 are shown.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://quintadb.ru/mcpDECLAREDSRC-001 Official MCP Registry16h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry16h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry16h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry16h ago
Version1.0.1DECLAREDSRC-001 Official MCP Registry16h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry16h ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run QuintaDB? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor QuintaDBLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of QuintaDB?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/quintadb-1?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/quintadb-1/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about QuintaDB

How do I connect QuintaDB?

Use the hosted endpoint https://quintadb.ru/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does QuintaDB offer?

When Electra Index connected on 14 Nov 2026, it listed 159 tools: list_projects, list_forms, get_form_fields, get_records, get_record, get_rel_id, create_record, update_record and more. The full list is in "Live check" above.

Is QuintaDB online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.

What can I use QuintaDB for?

Based on its description, it is most relevant to: query databases in plain language, build data pipelines.