Teable Mcp Sse
What is Teable Mcp Sse
teable-mcp-sse is a containerized server that serves the Teable API using the MCP protocol over Server-Sent Events (SSE) transport. It runs the OpenAPI MCP Server in a Docker environment, facilitating HTTP/SSE communication.
Use cases
Use cases for teable-mcp-sse include building real-time dashboards, integrating with client-side applications that require live updates, and developing services that need to communicate with the MCP server over HTTP/SSE.
How to use
To use teable-mcp-sse, set your API token as an environment variable named OPENAPI_TOKEN, then build and start the Docker container using ‘docker-compose up --build’. The MCP server will be accessible at http://localhost:8080/sse.
Key features
Key features include the ability to expose the MCP server over HTTP/SSE, pre-loaded OpenAPI definitions, and support for Bearer token authentication for API requests.
Where to use
teable-mcp-sse can be used in various fields such as web application development, real-time data streaming, and any scenario requiring API access through SSE.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Overview
What is Teable Mcp Sse
teable-mcp-sse is a containerized server that serves the Teable API using the MCP protocol over Server-Sent Events (SSE) transport. It runs the OpenAPI MCP Server in a Docker environment, facilitating HTTP/SSE communication.
Use cases
Use cases for teable-mcp-sse include building real-time dashboards, integrating with client-side applications that require live updates, and developing services that need to communicate with the MCP server over HTTP/SSE.
How to use
To use teable-mcp-sse, set your API token as an environment variable named OPENAPI_TOKEN, then build and start the Docker container using ‘docker-compose up --build’. The MCP server will be accessible at http://localhost:8080/sse.
Key features
Key features include the ability to expose the MCP server over HTTP/SSE, pre-loaded OpenAPI definitions, and support for Bearer token authentication for API requests.
Where to use
teable-mcp-sse can be used in various fields such as web application development, real-time data streaming, and any scenario requiring API access through SSE.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Content
Teable MCP Server
This setup runs the OpenAPI MCP Server (https://github.com/snaggle-ai/openapi-mcp-server) in Docker with mcp-proxy (https://github.com/sparfenyuk/mcp-proxy) to expose the MCP server over HTTP/SSE.
It’s pre-loaded with teable openapi definition and contains the most used functions.
Setup
- Set your API token as an environment variable:
export OPENAPI_TOKEN=your_token_here
- Build and start the Docker container:
docker-compose up --build
Usage
Once running, the MCP server is available at:
http://localhost:8080/sse
The server will use the token from the OPENAPI_TOKEN environment variable passed at build time as the Bearer token for API requests.
Configuration
- The OpenAPI definition is mounted from
./teable-openapi.jsonto/app/teable-openapi.jsonin the container - The server listens on port 8080
- Authorization headers are set using the OPENAPI_TOKEN environment variable
Architecture
Client ⟷ HTTP/SSE ⟷ mcp-proxy ⟷ stdio ⟷ openapi-mcp-server
The mcp-proxy converts between HTTP/SSE and stdio protocols, allowing the openapi-mcp-server (which only supports stdio) to be accessible over HTTP.
Dev Tools Supporting MCP
The following are the main code editors that support the Model Context Protocol. Click the link to visit the official website for more information.
