# SeaTable > SeaTable is a database of typed rows in tables and bases, sold as a cloud service hosted in Germany and as server software. Agents reach it through a REST API with per-base tokens and an official MCP server. - Canonical: https://www.anchorterminal.com/tools/seatable - Markdown: https://www.anchorterminal.com/tools/seatable.md (~8,500 tokens) - Slim: https://www.anchorterminal.com/tools/seatable.min.md (~2,030 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/seatable.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade B · 66.3/100 · rank #241 of 722 · #5 in Spreadsheets & operational tables · not agent-ready · confidence medium** ## Assessment API tokens are limited to one base and to read-only or read-write, and the official MCP server marks every tool as read-only or destructive. The Free plan allows 3,000 API calls a month in total, and base calls are capped at 200 a minute. The status page showed the base API degraded for 0.77 per cent of 30 days. ## Facts | Field | Value | | --- | --- | | Vendor | SeaTable GmbH (https://seatable.com) | | Kind | HTTP API | | Category | Spreadsheets & operational tables (https://www.anchorterminal.com/categories/spreadsheets) | | Transport | HTTP, stdio | | Endpoint | `https://cloud.seatable.io` | | Auth | API key · Self-serve. A signed-in user creates an API token for one base, read-only or read-write, which never expires and can be deleted. Base calls need a Base-Token, a JWT valid for 3 days, obtained from the API token at `/api/v2.1/dtable/app-access-token/`. Account calls (bases, groups, webhooks, sharing) need an Account-Token obtained with the username and password, which never expires and carries the user's full access. The hosted MCP server takes the API token as a Bearer header, or runs an OAuth flow with PKCE and dynamic client registration in which the user enters the API token and the server issues a one-hour access token. The OAuth flow has no scopes. | | Pricing | Freemium (Freemium) · Free cloud plan for up to 25 users with 10,000 rows, 2 GB of files and 3,000 API calls a month for the team, with no card at signup, so an agent can start without a contract. Plus is €7 a user a month billed yearly (€9 monthly) with 10,000 API calls per user, and Enterprise €14 (€18 monthly) with 50,000. Dedicated is sold through sales from 100 users with unlimited calls. Prices are in euros before VAT and aren't converted here. The MCP server is free to use and there is no separate sandbox (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API reference, the OpenAPI files, the MCP server's README or the pricing page (checked 2026-10-08). | | Licence | Proprietary cloud service under the Terms of Service for SeaTable Cloud. The MCP server is MIT. SeaTable Server Enterprise Edition is licensed under an EULA | | Tools exposed | 21 | | Packages | npm: `@seatable/mcp-seatable`; pypi: `seatable-api`; npm: `seatable-api` | | MCP registry name | `io.github.seatable/seatable` | | Source | https://github.com/seatable/seatable-mcp | | Docs | https://api.seatable.com/ | | llms.txt | https://api.seatable.com/llms.txt | | Last release | 2026-09-04 | | npm downloads / week | 103 | | PyPI downloads / week | 1,657 | | Surfaces graded | SeaTable Cloud's REST API at https://cloud.seatable.io and the hosted MCP server at https://mcp.seatable.com/mcp. The same API and MCP server run against a self-hosted SeaTable Server | | Free tier | Free plan for up to 25 users with 10,000 rows, 2 GB of files and 3,000 API calls a month for the team. The registration page says no credit card is required | | Rate limits | SeaTable Cloud allows 200 base calls a minute counted per base, 1,000 account calls a minute and 60 Account-Token requests a minute. Dedicated and Server default to 500 and 3,000. The hosted MCP server adds 60 requests a minute per token and 20 concurrent connections | | Monthly API quota | 3,000 calls for a Free team, 10,000 per user on Plus, 50,000 per user on Enterprise, unlimited on Dedicated, reset each month | | Batch size | List, append and update up to 1,000 rows a call and delete up to 10,000. SQL SELECT returns up to 10,000 rows. MCP write tools take up to 100 rows a call | | Auth and scopes | API-Token per base, read-only (`r`) or read-write (`rw`), permanent until deleted, or a temporary one valid for one hour. Base-Token (JWT, 3 days) for base calls. Account-Token from username and password for account calls, permanent | | Read and write | With a Base-Token, rows, links, tables, views, columns, select options, comments, snapshots, the activity log and SQL. With an Account-Token, bases, groups, sharing, webhooks, automations and import or export | | Filtering | `start`, `limit`, `view_name` and `convert_keys` on list rows, and SQL with WHERE, ORDER BY, GROUP BY and LIMIT at `/api-gateway/api/v2/dtables/{base_uuid}/sql/` | | MCP server | `@seatable/mcp-seatable` 1.6.4, MIT. 21 tools on the hosted endpoint, among them list_tables, get_schema, list_rows, find_rows, search_rows, query_sql, append_rows, update_rows, upsert_rows, delete_rows, link_rows, upload_file and create_snapshot. Streamable HTTP when hosted, stdio by `npx` for self-hosted servers | | Change events | Webhooks per base, created with an Account-Token at `/api/v2.1/workspace/{workspace_id}/dtable/{base_name}/webhooks/` | | SDKs | Python `seatable-api` 4.0.0 on PyPI (17 July 2026), JavaScript `seatable-api` 1.0.46 on npm (22 May 2026) and a PHP client generated from the OpenAPI files | | Deprecations | No deprecation policy found. Breaking changes are marked in the API changelog entry for each server version | | Certifications | None for SeaTable, per its security page. The hosting provider Exoscale's data centres are ISO 27001 certified. Penetration test of SeaTable Server in September 2024 by SRC Security Research & Consulting | | SLA | No SLA text found. The pricing page lists optional corporate support and SLAs for Dedicated, sold through sales with a minimum of 100 users | | Data location | Exoscale data centres in Frankfurt and Munich for all user data except subscription and payment data, per the security page. Hetzner in Germany is also on the sub-processor list | | Open source | The MCP server is MIT. SeaTable Cloud is a closed service, and SeaTable Server Enterprise Edition is licensed under an EULA | | Capabilities | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | | Tags | official, hosted, self-hosted, mcp, free-tier, api-key, openapi, llms-txt, webhooks, status-page, python, javascript, php, eu-hosted | | JSON | https://www.anchorterminal.com/api/v1/tools/seatable.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 69 | 13.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 81 | 13.2 | | Agent ergonomics | 13% | 16.2 | 74 | 12.0 | | Security & auth | 14% | 17.5 | 59 | 10.3 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 76 | 6.7 | | Transparency & trust (editorial 65, provenance 85) | 7% | 8.8 | 75 | 6.6 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **66.3 → B** | ### Why each score - Reliability 69: Graded on SeaTable Cloud's REST API and hosted MCP server, with the hosted lines. Status page at status.seatable.com, a Gatus dashboard with 15 components and uptime per component for up to 365 days (20). It publishes no incident reports. The base operations API shows 99.23 per cent over 30 days and 99.38 per cent over 365, the account API 99.95 per cent and the MCP server 99.98 per cent over 30 days. The failed checks we could read, from 5 to 8 October 2026, answered HTTP 200 with a body status of degraded, the longest stretch 34 minutes on 8 October. That is frequent degradation with no outage established, so 15 of 30 as a judgement call. Rate limits are published with numbers, 200 base calls and 1,000 account calls a minute on the cloud, plus monthly quotas (15). The docs recommend exponential backoff and base calls return `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset` headers, but a 429 has no body, no Retry-After header is documented and there are no idempotency keys. The MCP server retries a 429 three times with backoff (9 of 15). No SLA text found. The pricing page names optional SLAs for Dedicated only (0). The REST API is generally available and the MCP server is at 1.6.4 (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 81: Public OpenAPI 3.0 files for version 6.2, 404 operations in 8 files, and every MCP tool has a JSON Schema generated from a Zod model (25). `llms.txt`, `llms-full.txt` and Markdown copies of the reference pages are served at api.seatable.com (10). MCP tool descriptions say which tool to use for which job, and `query_sql` lists its syntax limits and tells the caller to switch tools after a failure. REST descriptions are specific but uneven (16 of 20). Parameters are typed, with a UUID pattern on `base_uuid`, 67 enums in the base operations file and column types as a oneOf, but row bodies are free-form objects keyed by column name and SQL is one string (9 of 15). The base operations file has 136 examples. Most operations document only a 200 response, and the status codes page is a generic table (8 of 15). The API changelog has an entry per server version with breaking changes marked, the spec repository has a branch per version, and paths carry `v2` or `v2.1`. No changelog file was found in the MCP repository (13 of 15). - Agent ergonomics 74: The hosted MCP server registers 21 tools, in the 11 to 30 band, and leaves out table and column changes by design. REST list calls take `start` and `limit`, and SQL can select columns (17 of 25). List rows pages by `start` and `limit` up to 1,000 and reads a saved view, SQL takes WHERE, ORDER BY and LIMIT up to 10,000 rows, and MCP has `page` and `page_size` (20). The reference lists status codes and says most 4xx answers carry an error code, but a 429 has no body and few operations document an error response. The MCP README maps common error messages to causes (11 of 20). No idempotency keys on the REST API. Every MCP tool carries readOnlyHint, destructiveHint and idempotentHint, and `upsert_rows` writes by key columns (14 of 20). Official clients for Python, JavaScript and PHP. A REST caller has to exchange the API token for a Base-Token and renew it every 3 days, which the clients and the MCP server do for it (12 of 15). - Security & auth 59: API tokens are limited to one base, set to read-only or read-write, named, deletable and listed with their last access time. They never expire unless the one-hour temporary kind is used, and can't be limited to a table. The Account-Token comes from the username and password, never expires and carries the whole account. The MCP server's OAuth flow has PKCE and dynamic client registration but no scopes, and wraps the same API token. No secret in a query string was found (25 of 30). Read-only tokens per base, and the MCP server leaves out schema changes and marks destructive tools, but `query_sql` accepts UPDATE and DELETE and there is no confirmation step (13 of 20). Rows and comments can hold text written by others, and no prompt-injection guidance was found. Write tools reject unknown columns (3 of 15). Tokens show last access time, each base has an activity log and row history, and team admins get operation and login logs. No per-call log for a token was found (10 of 15). The security page gives security@seatable.com, links the management report of a September 2024 penetration test, says SeaTable has no certification and that a bug bounty is under construction. No security.txt and no published advisory found (8 of 20). - Payments & pricing 30: Graded on the hosted cloud. No x402, MPP or L402 found (0). Plan prices are public in euros, Plus at €7 and Enterprise at €14 a user a month billed yearly, each with a monthly API call quota and no per-call price (10). A permanent Free plan with 3,000 API calls a month, and the registration page says no credit card is required. We didn't complete a signup (20). Access starts with registration in a browser, and the security page lists a captcha among access controls. API tokens can then be created by API with an Account-Token (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 76: The newest release we could date is MCP server 1.6.4 on 4 September 2026, 34 days before the check. SeaTable Cloud reported server version 6.2.13, whose date we didn't find. The product changelog gives 6.2.12 on 17 July 2026 (20 of 30). Five MCP server releases since 25 August 2026 and the API changelog entry for version 6.2 on 21 July (20). The forum's latest topics each had replies within a few days, in English and German. We didn't read who replied, and GitHub's API refused us, so issue reply times are unread (14 of 25). The MCP server is in the official MCP registry as `io.github.seatable/seatable` at 1.6.4, and the Python client had release 4.0.0 on 17 July 2026 (15). The MCP repository's CI runs lint, a type check and tests before each publish, and the OpenAPI repository has an API test suite. We didn't read the current CI result (7 of 10). - Transparency & trust 75: SeaTable Cloud is a closed service with clear terms, and the MCP server and its tool definitions are MIT (18 of 30). The privacy policy (version 1.3.0, 5 February 2026), a public data processing agreement and a page of technical and organisational measures agree on hosting in German data centres. Server logs are deleted within 180 days and deleted bases after 30 days in the recycle bin, but account data is removed 'after a few days' with no figure. The 2022 terms name only Frankfurt and say processor agreements are available on request, while the security page adds Munich and the agreement is public (23 of 30). No deprecation policy found. Breaking changes are marked in the API changelog at release, and the terms say they may be updated without prior notice (6 of 20). A sub-processor list (version 1.1.5, 16 October 2025) gives six companies with addresses and roles, and the security page names the two data centres (18 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/seatable.md (JSON https://www.anchorterminal.com/fixes/seatable.json) ### What we couldn't check - unchecked: incident history before 5 October 2026. The status page keeps only the last 50 events per component and publishes no incident reports, so the record rests on its uptime percentages - unchecked: GitHub stars, issue reply times and the current CI result. GitHub's API answered with a rate limit, so `githubStars` is empty - unchecked: the hosted MCP server's live tool list. The 21 tools come from the source at tag release-v1.6.4, and the endpoint answered 401 without a token - unchecked: whether signup asks for email confirmation or a captcha. We didn't create an account. The registration page says no credit card is required - unchecked: the release date of server version 6.2.13, which SeaTable Cloud reported. The product changelog page lists 6.2.12 on 17 July 2026 - unchecked: the registration record of seatable.io, the domain the REST API answers on - unchecked: the rendered API reference pages. api.seatable.com answered 429 to our later requests, so limits, authentication, status codes and the changelog were read from the Markdown sources in the OpenAPI repository and from `llms-full.txt` - No SLA text, security.txt, bug bounty, certification, deprecation policy, Retry-After header, idempotency key or prompt-injection guidance was found in the reviewed pages - The limits page gives 200 base calls a minute for SeaTable Cloud, and the MCP server's README gives a default of 500 per base, which is the figure for Dedicated and Server - The pricing page lists prices in euros only, so `unitPrices` is empty and the figures are in `pricingNotes` - The lead was right on vendor, URL and the REST interface. It missed the official MCP server, hosted at mcp.seatable.com and listed in the official MCP registry. API tokens are per base and read-only or read-write, with no finer scope, and base calls need a 3-day Base-Token generated from them ### Sources - API reference index for agents: (seen 2026-10-08) - full API reference text: (seen 2026-10-08) - API limits: (seen 2026-10-08) - API authentication: (seen 2026-10-08) - API status codes: (seen 2026-10-08) - API changelog: (seen 2026-10-08) - OpenAPI repository (cloned at commit c6d0ad9, branch v6.2): (seen 2026-10-08) - MCP server repository (cloned at commit d69d9b6, tag release-v1.6.4): (seen 2026-10-08) - MCP tool definitions in source: (seen 2026-10-08) - hosted MCP server's OAuth metadata: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - status page: (seen 2026-10-08) - status feed (components, events and uptime): (seen 2026-10-08) - server version on SeaTable Cloud: (seen 2026-10-08) - pricing: (seen 2026-10-08) - registration page: (seen 2026-10-08) - terms of service for SeaTable Cloud: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - data processing agreement: (seen 2026-10-08) - sub-processors: (seen 2026-10-08) - security page: (seen 2026-10-08) - legal documents index: (seen 2026-10-08) - imprint: (seen 2026-10-08) - product changelog: (seen 2026-10-08) - developer manual (client libraries): (seen 2026-10-08) - community forum, latest topics: (seen 2026-10-08) - npm package for the MCP server: (seen 2026-10-08) - PyPI package seatable-api: (seen 2026-10-08) - security.txt (404): (seen 2026-10-08) - RDAP for seatable.com: (seen 2026-10-08) ## Who's behind it (provenance 85/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | SeaTable GmbH | 20/20 | | Domain age | seatable.com, registered 2010-03-12 (16 years) | 15/15 | | Endpoint on the vendor's domain | cloud.seatable.io | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 | | Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 | | Status page | status.seatable.com | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The imprint names SeaTable GmbH, 117er Ehrenhof 5, 55118 Mainz, Germany, District Court Mainz, commercial register number HRB 49723. The Terms of Service for SeaTable Cloud are version 1.0.1, published on 14 April 2022. The German original is binding and the English page is a convenience translation. The privacy policy is version 1.3.0, published on 5 February 2026, and covers registration and the cloud service as well as the website. A data processing agreement (version 1.1.6, 16 October 2024) and a sub-processor list (version 1.1.5, 16 October 2025) are separate public pages. The MCP server answers at mcp.seatable.com and the API reference at api.seatable.com. The REST API answers at cloud.seatable.io, a second domain the vendor's site links for login. We didn't check the registration record of seatable.io. seatable.com/.well-known/security.txt and cloud.seatable.io/.well-known/security.txt return 404. The security page gives security@seatable.com for vulnerability reports. RDAP for seatable.com gives a registration date of 2010-03-12. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://seatable.com/terms-of-service/), read 2026-10-08, gives no date, states 5 of the 7 things a reader expects. - To know. Says the terms or the service can change without notice (costs points). "The Terms may be updated by us without prior notice." - To know. Says access can be ended without notice or for any reason. "We reserve the right to unilaterally terminate your access or restrict your access at any time without prior notice to you." - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. The law of Federal Republic of Germany. - Says how changes to the terms are announced. Says it gives notice of a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). SeaTable may use the names, logos and marks of corporate customers on its website and in marketing materials as reference customers. "We reserve the right to use the name, logo and marks of corporate customers on the seatable.io website and other marketing materials as reference customers." - Also in the text (2026-10-08). The user must make their own backups of their files at least every 24 hours. "The user has to carry out backups and other security measures of his files independently at least every 24 hours." - Also in the text (2026-10-08). Once a termination takes effect at the end of the subscription period, data generally cannot be restored, and a restore may be attempted for a fee in justified exceptional cases. "Once the termination takes effect at the end of the subscription period, it is generally not possible to restore data." **Privacy policy** (https://seatable.com/data-privacy/), read 2026-10-08, gives no date, states 6 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Not found in the text. Says whether personal data is sold or shared for advertising. - Also in the text (2026-10-08). SeaTable says the AI functions in its cloud services run on a self-hosted model and that no personal data is sent outside Europe for them. "This applies in particular to the use of AI functions in our cloud services. These use a self-hosted AI model (see hoster)." - Also in the text (2026-10-08). SeaTable says it does not control how third-party applications, including AI services connected through its API or MCP, process the data they retrieve. "SeaTable does not control how third-party applications process data retrieved through these interfaces." ## Live (updated 2026-10-08 21:53 UTC) - Right now: up, HTTP 200, 96 ms, checked 2026-10-08 21:53 UTC (get on `https://cloud.seatable.io`) - Uptime 24h 100.0% (28 probes) · 30 days 100.0% (28 probes) · p50 371 ms · p95 411 ms - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/seatable.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - API tokens are limited to one base, set to read-only or read-write, named per app and deletable, and the token list shows each token's last access time - Official MCP server, MIT-licensed, hosted at `https://mcp.seatable.com/mcp` and listed in the official MCP registry as `io.github.seatable/seatable` at version 1.6.4 - All 21 hosted MCP tools carry readOnlyHint, destructiveHint and idempotentHint annotations, and the tool set leaves out table and column changes - Public OpenAPI 3.0 files with 404 operations, plus `llms.txt`, `llms-full.txt` and Markdown copies of the reference pages - Sub-processor list, data processing agreement and security measures are public, and the security page places all user data in Frankfurt and Munich ## Weaknesses - Monthly API call quotas by plan, 3,000 for a whole Free team, 10,000 per user on Plus and 50,000 per user on Enterprise - A 429 response has no body and no Retry-After header is documented, and the REST API has no idempotency keys - Tokens can't be limited to a table, and the MCP tool `query_sql` accepts UPDATE and DELETE statements with no confirmation step - The security page says SeaTable holds no certification, and its bug bounty, expected in 2025, is still described as under construction - No SLA text is published. The pricing page names optional SLAs for Dedicated only, and the terms exclude liability for uninterrupted availability ## Before you call it (notes for agents) 1. Create an API token for the one base with read-only permission unless writes are needed, then exchange it at `/api/v2.1/dtable/app-access-token/` for a Base-Token 2. Renew the Base-Token before it expires after 3 days, and send it as `Authorization: Bearer` to `/api-gateway/api/v2/dtables/{base_uuid}/` 3. Read `x-ratelimit-remaining` and `x-ratelimit-reset` on every base call. SeaTable Cloud allows 200 base calls a minute and answers 429 with no body 4. Batch writes to save the monthly quota. One call appends or updates up to 1,000 rows over REST and 100 over MCP 5. Over MCP, prefer `update_rows` and `delete_rows` to `query_sql`, which can run UPDATE and DELETE, and call `get_schema` before writing ## Connect Install: ```bash npx -y @seatable/mcp-seatable ``` First request: ```bash curl -H "Authorization: Bearer YOUR_API_TOKEN" "https://cloud.seatable.io/api/v2.1/dtable/app-access-token/" ``` MCP client configuration: ```json { "mcpServers": { "seatable": { "headers": { "Authorization": "Bearer your-api-token" }, "type": "streamable-http", "url": "https://mcp.seatable.com/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/seatable. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | NocoDB | BB | 75.7 | 37 | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/nocodb.md | | Airtable | BB | 70.9 | 124 | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/airtable.md | | Coda (Superhuman Docs) | B | 64.8 | 270 | sheets.read, sheets.write, sheets.tables, sheets.records, sheets.formulas | no | https://www.anchorterminal.com/tools/coda.md | | Baserow | B | 63.6 | 306 | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/baserow.md | | Teable | C | 61 | 379 | sheets.read, sheets.write, sheets.records, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/teable.md | | Grist | D | 50.1 | 597 | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/grist.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The official MCP server is hosted for SeaTable Cloud at https://mcp.seatable.com/mcp over Streamable HTTP, with a Bearer API token or an OAuth flow with PKCE and dynamic client registration (source: ) - The MCP server registers 21 tools on the hosted endpoint, 22 in multi-base mode, and its README says it leaves out creating or deleting tables and columns on purpose (source: ) - An API token belongs to one base, is read-only or read-write and never expires. Base calls need a Base-Token, a JWT valid for 3 days, generated from it (source: ) - SeaTable Cloud limits base operations to 200 calls a minute and account operations to 1,000, and has had monthly API quotas by plan since summer 2025 (source: ) - The OpenAPI 3.0 files for version 6.2 hold 404 operations in 8 files, 54 of them base operations (source: ) - API changelog entry for version 6.2 is dated 21 July 2026 and marks one breaking change, a renamed response field on Get Team Info (source: ) - The status page reports the base operations API at 99.23 per cent over 30 days and 99.38 per cent over 365, the account API at 99.95 per cent and the MCP server at 99.98 per cent over 30 days (source: ) - The security page says there is no certification for SeaTable, that a penetration test of SeaTable Server was done in September 2024, and that a bug bounty is under construction (source: ) ## Compare - [Coda (Superhuman Docs) vs SeaTable](https://www.anchorterminal.com/compare/coda-vs-seatable.md): B 64.8 vs B 66.3 - [Google Sheets API vs SeaTable](https://www.anchorterminal.com/compare/google-sheets-api-vs-seatable.md): BB 76.3 vs B 66.3 - [Microsoft Excel (Microsoft Graph workbook API) vs SeaTable](https://www.anchorterminal.com/compare/microsoft-excel-graph-vs-seatable.md): C 58.5 vs B 66.3 - [Airtable vs SeaTable](https://www.anchorterminal.com/compare/airtable-vs-seatable.md): BB 70.9 vs B 66.3 - [Baserow vs SeaTable](https://www.anchorterminal.com/compare/baserow-vs-seatable.md): B 63.6 vs B 66.3 - [Grist vs SeaTable](https://www.anchorterminal.com/compare/grist-vs-seatable.md): D 50.1 vs B 66.3 - [NocoDB vs SeaTable](https://www.anchorterminal.com/compare/nocodb-vs-seatable.md): BB 75.7 vs B 66.3 - [SeaTable vs Smartsheet API + MCP](https://www.anchorterminal.com/compare/seatable-vs-smartsheet.md): B 66.3 vs B 67.6 - [SeaTable vs Teable](https://www.anchorterminal.com/compare/seatable-vs-teable.md): B 66.3 vs C 61 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on seatable.com or one of its subdomains, or the README of github.com/seatable/seatable-mcp. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "seatable", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html SeaTable on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![SeaTable on Anchor Terminal](https://www.anchorterminal.com/badges/seatable.svg)](https://www.anchorterminal.com/tools/seatable) ``` Plain link: ```html SeaTable on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say SeaTable is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/seatable-dark.png - Light: https://www.anchorterminal.com/assets/share/seatable-light.png