Integration

Tableland integration

Tableland is a decentralized SQL database built on blockchain. Create, write, and read data using familiar SQL syntax while benefiting from blockchain-based ownership, access control, and data provenance. Tables are NFTs owned by Ethereum addresses, enabling permissionless data composability. Perfect for Web3 applications requiring structured data storage, gaming, DAOs, and decentralized data marketplaces.

Connect Tableland How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Tableland.Built from the 5 Tableland tools below, on the connection you add once.

Common Tableland use cases

health monitoring
version verification
fetching leaderboard data
verifying table ownership
confirming writes completed
node diagnostics
status dashboards
querying DAO proposals
inspecting table schema
debugging failed operations

What you can do with Tableland

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Table, 2 operations

get_table_infoGet table infoGETRetrieves table metadata including owner address, schema definition, creation block, and table name.
read_tableRead tableGETQueries Tableland tables using SQL SELECT statements. Reading is permissionless with support for JOINs, aggregations, and complex queries.

Health, 1 operation

get_healthGet healthGETChecks the health and availability of the Tableland network. Returns status of validators and supported chains.

Receipt, 1 operation

get_receiptGet receiptGETRetrieves the transaction receipt for a Tableland write operation. Returns confirmation status and any errors.

Version, 1 operation

get_versionGet versionGETReturns version information about the Tableland validator daemon.

Use Tableland from Claude Code, Cursor or Codex

Connect Tableland in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Tableland operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Tableland

Create your workspace
Sign up free. Nothing to install.
Connect Tableland once
Tableland needs no credential, so its tools work immediately.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Tableland integration FAQ

What can you do with the Tableland integration?

LiveContext exposes 5 operations on Tableland, covering table, health, receipt and version. Common uses include health monitoring, version verification and fetching leaderboard data.