Seatable Mcp

Created By
brianmoney8 months ago
A comprehensive Model Context Protocol (MCP) server for SeaTable that exposes end‑to‑end database capabilities (schema introspection, CRUD, querying, linking, select option management, and file attachment stubs) through 18+ rigorously defined tools. You can run it: - As a local CLI (stdio) MCP server - As an HTTP SSE server for local or remote IDEs - As a globally distributed Cloudflare Worker (dual transport: `/sse` + `/mcp`) Version 1.0.3 introduces fully explicit Zod schemas for every tool in the Cloudflare Worker path, eliminating earlier adapter ambiguity and ensuring reliable argument delivery across hosts.
Overview

What is Seatable MCP?

Seatable MCP is a comprehensive Model Context Protocol (MCP) server designed for SeaTable, providing end-to-end database capabilities such as schema introspection, CRUD operations, querying, linking, and file attachment management through a set of rigorously defined tools.

How to use Seatable MCP?

You can run Seatable MCP in various ways: as a local CLI server, an HTTP SSE server for local or remote IDEs, or as a globally distributed Cloudflare Worker. Deployment involves cloning the repository, installing dependencies, and using the provided commands to start the server.

Key features of Seatable MCP?

  • Complete CRUD operations for database management.
  • Advanced querying capabilities with client-side filtering and raw SQL support.
  • Schema management for creating, modifying, and deleting tables and columns.
  • Real-time health monitoring and connection status tracking.
  • Support for both local and cloud deployments with session persistence.

Use cases of Seatable MCP?

  1. Managing SeaTable databases in production environments.
  2. Developing and testing applications that require real-time database interactions.
  3. Integrating with IDEs for seamless database operations.

FAQ from Seatable MCP?

  • Is Seatable MCP suitable for production use?
    Yes, it is designed to be production-ready with comprehensive error handling and logging.

  • Can I run Seatable MCP locally?
    Yes, you can run it as a local SSE server for development and testing.

  • What are the environment variables required?
    You need to set SEATABLE_SERVER_URL, SEATABLE_API_TOKEN, and SEATABLE_BASE_UUID for proper configuration.

Server Config

{
  "mcpServers": {
    "seatable": {
      "command": "npx",
      "args": [
        "-y",
        "@aspereo/mcp-seatable"
      ],
      "env": {
        "SEATABLE_SERVER_URL": "https://your-seatable-server.com",
        "SEATABLE_API_TOKEN": "your-api-token",
        "SEATABLE_BASE_UUID": "your-base-uuid"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
6 months ago
Author Name
brianmoney
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

8 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago