Teable MCP server
Teable in any MCP client, through Memtro: Teable does not publish this server. Memtro's Teable connector reads Teable through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Teable no-code database: spaces, projects (bases), tables, their fields with types and options, records in a table or view, single records and record comments; when you ask, can create, update, upsert, archive, duplicate or delete records and add or delete comments.
Reads
teable_list_spacesTeable spaces the token can see, with your role in each.teable_list_basesTeable projects (bases): in one space, or every project the token can reach when no space is given (that needs the base|read_all scope).teable_list_tablesTables in a Teable project (base): id, name, description, default view, last change.teable_list_fieldsFields (columns) of a Teable table: id, name, type, whether primary, description, and the choices of a select field.teable_list_recordsRecords in a Teable table, keyed by field name: give a view_id to use that view's filter and sort, otherwise the table in creation order.teable_get_recordOne Teable record with every visible field, keyed by field name.teable_list_commentsComments on one Teable record: text (mentions as @name), author name, time.
Acts, when you ask
These change something in Teable. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
teable_create_recordsCreates records in a Teable table, visible to everyone with access; automations configured in the project may run.teable_update_recordsChanges fields on Teable records by id; only the fields given change and null clears one.teable_upsert_recordsCreates Teable records, or for records whose value in match_field_id…teable_delete_recordsPermanently deletes the given Teable records by id, for everyone.teable_archive_recordsMoves the given Teable records out of the table into its archive, where they are read-only and can be restored.teable_duplicate_recordMakes a copy of a Teable record, placed just after the original in the given view.teable_add_commentComments on a Teable record as the token's user, visible to everyone with access; users mentioned by id are notified.teable_delete_commentPermanently deletes a comment on a Teable record.
Connect it
First connect Teable on Dashboard → Connections, then add Memtro to your client once. The Teable tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Teable connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What is in the Deals table in the Won view?
- › What fields does the Projects table have?
- › What comments are on the Northwind deal record?
- › Which tables are in the Sales project?
- › Archive the test records in the Leads table.
Questions
- Is this an official Teable MCP server?
- No. It is Memtro's MCP server with Memtro's Teable connector behind it: the connector reads Teable through its API with the credentials you connect on Dashboard → Connections, and Teable publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Teable?
- Only when you ask, and only what it has been granted: create records in a table; update records; create or update records matched on a unique field; delete records (permanent); archive records; duplicate a record; comment on a record; delete a comment. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.