Skip to content
CloudTable Docs

Overview

CloudTable API 1.0.0

Section titled “CloudTable API 1.0.0”

Programmatic access to your CloudTable bases, tables, and records — over both a REST API and an MCP server. REST and MCP share one data layer, so results match. Records use the Airtable-parity shape { id, createdTime, fields }.

Authentication

Create a key in the app: Account menu → API keys. Pick its scopes, copy it once, then send it on every request as either header:

  • x-api-key: <your-key>
  • Authorization: Bearer <your-key>

Scopes: data:read / data:write (records), schema:read / schema:write (bases, tables, fields, views), members:read / members:manage, and mcp:tools (use the MCP server).

MCP server

Endpoint (Streamable HTTP): https://api.cloudtable.insurge.io/mcp

It exposes the same operations as this REST API as MCP tools (list_bases, describe_base, query_records, create_records, update_records, delete_records, create_table, create_field, create_view, set_public_share, …), each with an input and output schema.

Programmatic clients (Claude Desktop, Cursor, n8n, scripts) — API key

Point the client at https://api.cloudtable.insurge.io/mcp and send your API key as a bearer token: Authorization: Bearer <your-key> (the key needs mcp:tools plus the data:* / schema:* scopes for the tools you’ll call). Clients that use a custom header can send x-api-key instead.

ChatGPT, Grok & other web clients — OAuth (no API key)

These connect with OAuth 2.1 — you don’t paste a key. Add a custom connector / MCP server and give it the endpoint:

https://api.cloudtable.insurge.io/mcp

The client then does everything automatically:

  1. Discovers the authorization server via /.well-known/oauth-protected-resource → /.well-known/oauth-authorization-server.
  2. Registers itself with Dynamic Client Registration (RFC 7591) — no manual client setup.
  3. Opens CloudTable’s sign-in + consent screen (PKCE S256).
  4. Receives an access token and calls the tools.

You’ll be prompted to sign in to CloudTable and approve the requested scopes. That’s it.

n8n

Use the HTTP Request node with Header Auth — header x-api-key, base URL https://api.cloudtable.insurge.io/api/v1.

Information

  • OpenAPI version: 3.1.0

Operations

Section titled “Operations”
GET
/api/v1/me
GET
/api/v1/bases
POST
/api/v1/bases
GET
/api/v1/bases/{baseId}
DELETE
/api/v1/bases/{baseId}
PATCH
/api/v1/bases/{baseId}
GET
/api/v1/bases/{baseId}/tables
POST
/api/v1/bases/{baseId}/tables
GET
/api/v1/tables/{tableId}/fields
POST
/api/v1/tables/{tableId}/fields
GET
/api/v1/tables/{tableId}/views
POST
/api/v1/tables/{tableId}/views
DELETE
/api/v1/tables/{tableId}
PATCH
/api/v1/tables/{tableId}
DELETE
/api/v1/fields/{fieldId}
PATCH
/api/v1/fields/{fieldId}
DELETE
/api/v1/views/{viewId}
PATCH
/api/v1/views/{viewId}
GET
/api/v1/tables/{tableId}/records
POST
/api/v1/tables/{tableId}/records
DELETE
/api/v1/tables/{tableId}/records
PATCH
/api/v1/tables/{tableId}/records
GET
/api/v1/tables/{tableId}/records/search
GET
/api/v1/records/{recordId}
DELETE
/api/v1/records/{recordId}
PATCH
/api/v1/records/{recordId}
GET
/api/v1/orgs/{orgId}/workspaces
POST
/api/v1/workspaces
DELETE
/api/v1/workspaces/{workspaceId}
PATCH
/api/v1/workspaces/{workspaceId}
GET
/api/v1/bases/{baseId}/share
PUT
/api/v1/bases/{baseId}/share
DELETE
/api/v1/bases/{baseId}/share

Authentication

Section titled “Authentication”

ApiKeyAuth

Section titled “ApiKeyAuth”

Security scheme type: apiKey

Header parameter name: x-api-key