Teable MCP Server Terms and Privacy
Last updated: October 23, 2026
These terms apply to your use of the Teable MCP (Model Context Protocol) server at https://mcp.teable.ai/mcp, which lets AI apps such as Claude, ChatGPT, Codex and Cursor work with your Teable data.
They supplement Teable's Terms of Service and Privacy Policy, which remain the controlling agreements. Where this page is more specific about the MCP server, this page applies.
Part A. Terms of use
1. What the MCP server does
The MCP server lets an AI app you connect (your "AI client") read and change data in your Teable account. It runs the tool calls your AI client decides to make, as you: it can access exactly what you can access in Teable, nothing more. Depending on the permissions you approve, that can include creating, updating and deleting records, tables, fields, views and automations.
2. Connecting and disconnecting
You connect an AI client by signing in to Teable and approving the permissions it asks for, or by giving it a personal access token. You can see your connected AI clients and disconnect any of them at any time in Settings → MCP; disconnecting revokes its access immediately. Personal access tokens are managed in Settings → Personal access tokens.
3. You're responsible for what your AI client does
Actions your AI client takes through your connection count as your actions, including changes and deletions. AI clients make mistakes: review what they propose, use the confirmation prompts your AI client offers before it changes data, and only connect AI clients you trust. Deleted data can be restored from the trash for the periods described in our Privacy Policy.
4. AI clients are third-party services
Your AI client is provided by someone else, such as Anthropic, OpenAI or Cursor, under their own terms and privacy policy. Teable does not control how it behaves, which model it uses, or what it does with the data it receives, and its provider may charge you for it.
5. Fair use
Our Acceptable Use Policy and AI usage rules apply to everything done through the MCP server. Don't use it to get around permissions, rate limits or plan limits, to overload the Service, or to give anyone access to Teable's AI capabilities or other people's data they aren't entitled to. We apply rate and size limits to requests and responses.
6. Availability and changes
The MCP server is part of the Service and is provided "as is" and "as available," under the disclaimers and limitations of liability in our Terms of Service. We may add, change or remove tools, or change or discontinue the MCP server, at any time. We may suspend or disconnect an AI client or connection that breaks these terms or puts the Service or other users at risk.
Part B. Privacy
7. What we process
- AI client registration. When an AI client registers with Teable, we keep what it tells us: its name, its website, and the addresses Teable may send you back to after sign-in.
- Your approval. Which account approved the AI client, the permissions granted, when you approved it and when it was last used, plus the tokens it presents on each request.
- Requests. The name of each tool your AI client calls and the arguments it sends, such as a table ID, a search query or the values of records to create. We don't receive your conversation with the AI client, its other tools or the files on your device, unless the AI client puts them in a request.
- Technical information. IP address, the AI client's user agent, timestamps, response status and error details, as for any other request to the Service.
8. How we use it
To sign AI clients in, run their requests, enforce your permissions and plan limits, show you which AI clients are connected and when they were last used, record changes in your audit history (marked as made through AI), fix errors and prevent abuse. We don't use MCP requests or the data returned to AI clients for advertising or to train AI models, and we don't sell them.
9. Where your data goes
Your AI client. The MCP server returns the data each request asks for, such as records, table and field definitions or query results, to the AI client that made it. From there, the AI client's provider handles it under its own terms and privacy policy, and may send it to the AI model it uses. Only connect AI clients you're comfortable sharing that data with.
Your collaborators. Changes made through the MCP server show up in your spaces like any other change, for the collaborators who can see them.
Our service providers. Our hosting, logging and monitoring providers process MCP requests to run the Service, as described in section 4 of our Privacy Policy. MCP requests are not sent to Teable's AI providers; if a request triggers an AI feature in your workspace, such as an AI field, that feature works as described in section 2 of our Privacy Policy.
10. How long we keep it
| Information | How long we keep it |
|---|---|
| An AI client that registered but never completed sign-in | Removed automatically after 7 days. |
| Your connected AI clients and the permissions you granted | Until you disconnect the AI client or delete your account. |
| Access and refresh tokens | Access tokens are short-lived; refresh tokens expire after a period without use. Both stop working as soon as you disconnect the AI client. |
| Server logs and request traces | Up to 30 days. |
| Security and audit logs, including changes made through MCP | Up to one year. |
Records and other content created or changed through the MCP server are part of your workspace and are kept as described in our Privacy Policy. Your other privacy rights, and how to use them, are in section 9 of our Privacy Policy.
11. Changes and contact
We may update this page as the MCP server changes. We'll post the new version here and update the date above; significant changes are notified as described in our Privacy Policy. Questions? Email support@teable.ai.
