REST & MCP API
Everything you can do in the CloudTable UI is available programmatically, in two ways:
- REST API — HTTP endpoints for reading and writing records, tables, and bases.
- MCP server — the same capabilities exposed as tools for AI clients that speak the Model Context Protocol.
Reference
Section titled “Reference”The complete, always-current endpoint reference — every path, parameter, schema, and response — is generated from the OpenAPI spec and lives right here in the docs:
- API Reference → — browse all endpoints in the sidebar.
- OpenAPI spec: api.cloudtable.insurge.io/api/v1/openapi.json
Base URL & authentication
Section titled “Base URL & authentication”The REST API is served from the API origin:
https://api.cloudtable.insurge.io/api/v1Authenticate with an API key as a bearer token:
curl https://api.cloudtable.insurge.io/api/v1/... \ -H "Authorization: Bearer <your-api-key>"API keys are scoped (for example records:read, schema:write) so you can grant only what an integration needs. Create and manage keys from your account settings in the app.
Reading & writing records
Section titled “Reading & writing records”The REST layer covers listing and CRUD for records, plus table and base structure. Computed fields — formula, template, and code — are returned like any other field, but are read-only: writes that target a computed field are rejected.
See the API Reference for the exact endpoints, request bodies, and response shapes.
The MCP server exposes your bases as tools so AI clients (and agents) can query and modify data with your permission. It’s available at:
https://api.cloudtable.insurge.io/mcpPoint an MCP-capable client at that URL and authenticate with an API key (or OAuth, where the client supports it). The available tools mirror the REST surface — listing tables, reading and writing records, and managing structure.
Related
Section titled “Related”- Field types — the types you’ll read and write.
- Formula · Template · Code — computed, read-only fields.