Log inSubmit server
T

Teable

Work with Teable tables and records from AI assistants through a remote Streamable HTTP MCP endpoint.

InstallWebsite
Get support Full README Compare alternatives Embed widget Claim this listing

Install Teable

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.teable.ai/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 3d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 3d ago · Nov 10, 2026, 19:15 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.teable.ai/mcp

Overview

The Teable MCP server connects AI assistants to Teable projects, tables, and records through Streamable HTTP. It uses OAuth or a Teable personal access token for authentication and requires an account with access to the target project. Reach for it when an agent needs to work with structured business data stored in Teable.

Use cases

  • Read Teable records through an AI assistant
  • Work with tables in an accessible Teable project
  • Connect an MCP client to remote Teable data
  • Authenticate access with OAuth or a personal access token

Key features

  • Remote Streamable HTTP MCP endpoint
  • Access to Teable tables and records
  • OAuth authentication
  • Teable personal access token authentication
  • Project-level access control

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

6/6 checks healthy over the last 23d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

MaintenanceActively maintainedStatus declared by the project or listing owner.
Availability100%Our rolling endpoint + install checks that succeeded.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Teable works

What the Teable MCP server does

The Teable MCP server connects AI assistants to Teable, an AI spreadsheet that combines a collaborative spreadsheet interface with a structured database. It gives assistants access to Teable tables and records through the Model Context Protocol.

This setup is intended for work involving data already stored in Teable projects. An assistant can connect to the remote service and operate in the context of projects the authenticated account is allowed to access. The available scope is tied to Teable access rather than to a local database installation.

How it works

The Teable MCP server is hosted remotely and exposes a Streamable HTTP endpoint at https://mcp.teable.ai/mcp. An MCP-compatible client connects to that endpoint instead of starting a local process from a checked-out repository.

Authentication is handled with either OAuth or a Teable personal access token. The account used for authentication must have access to the project containing the tables or records the assistant needs to use. If the account cannot access the target project, the connection does not provide access to that project’s data.

The official MCP Registry identifier is ai.teable/teable.

Setup and configuration

Configure an MCP-compatible AI assistant to use the remote endpoint:

  • Endpoint: https://mcp.teable.ai/mcp
  • Authentication: OAuth or a Teable personal access token
  • Access requirement: an account with permission to the target Teable project

Follow the client’s process for adding a Streamable HTTP MCP server and complete the selected authentication flow.

Tools and capabilities

The Teable MCP server provides agent access to Teable tables and records. This makes it suitable for assistants that need to work with structured information maintained in Teable’s spreadsheet-style interface and database model.

Treat the documented capability as access to Teable tables and records rather than assuming a particular set of CRUD or query tools.

Limitations and notes

Access depends on the authenticated Teable account and its permissions. The server does not grant access to projects that the account cannot already reach. It is a remote service, so use the published Streamable HTTP endpoint and configure authentication in the MCP client.

These details should be confirmed with Teable before building a workflow that depends on them.

Read the full README

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Teable

Teable is an MCP server that connects AI assistants to Teable, a collaborative spreadsheet and structured database, through Streamable HTTP. Its main capability is working with Teable tables and records. It requires authentication through OAuth or a Teable personal access token and access to the target project.

Configure the client for Streamable HTTP, then authenticate with OAuth or a Teable personal access token.

Authenticate with OAuth or a Teable personal access token. The account must also have access to the Teable project containing the tables or records you want the assistant to use.

It can work with Teable tables and records in projects the authenticated account can access.

Related MCP servers

All in Databases All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTeable AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/teable?style=directory)](https://allmcps.com/mcp/teable)
HTML Embed
<a href="https://allmcps.com/mcp/teable"><img src="https://allmcps.com/api/badge/teable?style=directory" alt="Teable on AllMCPs" /></a>