Create Dapta databases and tables from the MCP server

Dapta databases are where your automations keep their state between runs, such as how many attempts a lead has had or when to call next. Through the Dapta MCP server, an assistant like Claude could already read them. Now it can also build one from scratch: create the database, create its tables, and add, update, upsert or delete rows.

How it works

1. Connect your assistant to the Dapta MCP server. If it is already connected, the new tools show up on their own.
2. Ask in plain words, for example: "Create a Dapta database called Campaign State" or "Create a table for call attempts with phone, attempts and next call date".
3. Check the preview the assistant shows you: the database or table and its columns, or exactly which rows will be added, changed or removed.
4. Confirm, and the change is committed. After a row change, the assistant reads the rows back so you can see what was written.

Upsert means adding rows by a column that identifies each one, such as a phone number: a row whose value is already in the table updates that row instead of adding a second copy, and a row with no match is added. You can add up to 100 rows at a time.

More in the same release

• Archive a flow, or a whole folder, from your assistant. Archived flows go to the Trash in Flow Studio, where you can restore them.
• Flows the assistant creates have their nodes laid out, so they no longer open as a stack of cards.
• Link knowledge bases to a voice agent. A knowledge base that is not ready yet is refused.

Good to know

• Every write is previewed first and only happens after you confirm.
• Creating a database or a table adds new data and changes nothing that already exists. Updating and deleting rows change existing data.
• For an upsert, the key column must point to exactly one row: the change is refused if a value matches more than one existing row, if two new rows share a value, or if a row has no value in that column.