Tabidoo MCP server

With the Tabidoo MCP server, AI assistants such as Claude or ChatGPT can work with your Tabidoo applications. They can find and analyze your data, create and change records, and even build and change whole applications – always only within the rights of the API token you give them.

What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI assistants connect to other systems. Once you connect Tabidoo, you can simply ask your assistant, for example:

• "What tables do I have in Tabidoo?"
• "Show me the open orders over 10,000 from last month."
• "Which customer had the most invoices this year?"
• "Create a table Projects with a name, an owner, a deadline, and a status."
• "When an order is set to Done, fill in the completion date automatically."

Server URL and authentication

Create an API token

1. Open your account settings – click your avatar in the top right corner – and go to API.
2. Create a new token. We recommend a Shared API Token.
3. Assign the token a role in each application the assistant should work with.
4. Copy the token and use it when you connect your assistant.

Shared or personal token?

• Shared API Token (recommended) – has only the roles you assign to it in each application. Give it only the rights the assistant really needs – for example, a read-only role if the assistant should only analyze data.
• Personal token – has the same rights as your user account. Everything you can do, the assistant can do too.

Keep your token private, like a password. If someone else gets it, deactivate it and create a new one.

What the assistant can do

What the assistant can really do always depends on the roles of the token.

• Find and read data – search and filter records, find "my" records or duplicates, read linked records.
• Analyze data – counts, sums, averages, minimum and maximum, grouping by a field or by year, month, week, or day, joining linked tables.
• Change data – create, update, and delete records, also many at once; create or update records by the import key; attach files.
• Work with documents – read a document you give the assistant in the chat (for example an invoice) and save the information from it into Tabidoo.
• Build and change applications – applications, tables, fields, dropdown options, links between tables, modules, and extensions; calculated fields; field rules such as required or unique; conditional formatting; the layout of the record form; form scripts.
• Automate – create and change workflows with any trigger, with steps as boxes (Send email, Send notification, Workflow condition, Foreach loop, …) or as scripts.
• Dashboards – charts, metrics, lists, pivot tables, and free HTML widgets.
• Users and roles – give users access, change their roles and rights (applications with the Users and roles extension).
• Check consumption – how much of your plan limits you have used.

What the assistant cannot do

Not available over MCP yet:

• views and saved filters; form behaviors (the assistant can only read them),
• reading the content of a file stored in Tabidoo – the assistant gets only a download link, valid for 24 hours,
• publishing a form or a dashboard; changing the owner of an application,
• your own profile, billing, and notifications.

Done only in the Tabidoo application:

• table inheritance, restoring a snapshot, templates, running a workflow on demand,
• API tokens, the AI/MCP read-only setting, encrypted scripts,
• the Tabidoo AI chat and AI agents,
• branding – the application logo, favicon, and tile picture.

Before the assistant changes your data

• Limit what it can do. Use a Shared API Token with only the roles it needs. To allow only reading in an application, open the Advanced settings of the application and, on the Basics tab, check Restrict AI/MCP to read-only access. With this setting, AI and MCP can only read data in the application, whatever rights the token has.
• Every change runs your workflows. When the assistant saves a record, the When record changed workflows of the table run – exactly as if you saved it yourself. They may send e-mails or change other records. A bulk write by the assistant is not an import, so When records imported workflows do not run.
• Deleted records cannot be restored. The assistant is instructed to count the records and ask you before it deletes them – always check what it is about to delete.
• Check the result. After the assistant changes an application, a workflow, or a script, check the result in Tabidoo.
• Use a current model. Changes of the application structure, workflows, and scripts need the latest model of your assistant. Older or smaller models often send invalid requests or repeat a wrong one.

Limits

• Every call of the assistant counts against the API rate limits of the application owner (requests per minute and per hour). If you see Too many requests, wait at least a minute.
• Data the assistant loads counts into Loaded data – see Data Transfer Limit.
• Data usage (click your avatar) shows the number of MCP calls.
• MCP does not use your Tabidoo AI credits. The work of the assistant itself is covered by your Claude or ChatGPT plan.

All limits are in Limits in Tabidoo.

Connect your AI assistant

• Connect Tabidoo to Claude using MCP
• Connect Tabidoo to ChatGPT using MCP

Other assistants that support remote MCP servers can connect with the same URL and token.

Troubleshooting

See also

• API
• Limits in Tabidoo
• AI Introduction