Integration

Ceramic integration

Ceramic Network is a decentralized data network for composable Web3 applications. Store, manage, and query mutable data streams on a global, decentralized network. Build with verifiable, tamper-proof data using DIDs (Decentralized Identifiers) and blockchain anchoring. Supports TileDocuments, Caip10Links, Models, and ModelInstanceDocuments.

Connect Ceramic How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common Ceramic use cases

node administration
health monitoring
node configuration
ComposeDB administration
node configuration cleanup
index monitoring
ComposeDB deployment
ComposeDB management
admin pin audit
admin stream cleanup

What you can do with Ceramic

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.

Admin, 8 operations

get_admin_codeGet admin codeGETGenerates a one-time admin code for authenticating admin API requests. Code expires after 1 minute.
get_indexed_model_dataGet indexed model dataGETReturns indexed models and their configurations. Requires admin DID authorization.
get_indexed_modelsGet indexed modelsGETReturns all model StreamIDs indexed by the node. Requires admin DID authorization.
get_node_statusGet node statusGETRetrieves Ceramic node status including network, version, anchor config, and sync state. Requires admin DID authorization.
start_indexing_model_dataStart indexing model dataPOSTStarts indexing models on the node. Requires admin DID authorization with JWS-signed payload.
start_indexing_modelsStart indexing modelsPOSTStarts indexing models by StreamID. Requires admin DID authorization with JWS-signed payload.
stop_indexing_model_dataStop indexing model dataDELETEStops indexing models on the node. Requires admin DID authorization with JWS-signed payload.
stop_indexing_modelsStop indexing modelsDELETEStops indexing models by StreamID. Requires admin DID authorization with JWS-signed payload.

Pin, 7 operations

admin_list_pinsAdmin list pinsGETLists pinned streams or checks a specific pin via the admin API. Requires admin DID authorization.
admin_pin_streamAdmin pin streamPOSTPins a stream via the admin API. Requires admin DID authorization.
admin_unpin_streamAdmin unpin streamDELETERemoves a pin from a stream via the admin API. Requires admin DID authorization.
check_pinCheck pinGETChecks if a specific stream is pinned on the local Ceramic node.
list_pinsList pinsGETLists all pinned streams on the local Ceramic node. Returns StreamIDs of all persisted streams.
pin_streamPin streamPOSTPins a Ceramic stream to the local node for persistent storage and automatic synchronization.
unpin_streamUnpin streamDELETERemoves a pin from a Ceramic stream. The stream may be garbage collected from local storage.

Stream, 6 operations

apply_commitApply commitPOSTApplies a signed commit to update a Ceramic stream. Maintains full version history with cryptographic verification.
create_streamCreate streamPOSTCreates a new mutable data stream on Ceramic Network. Supports TileDocuments, Caip10Links, Models, and ModelInstanceDocuments.
get_streamGet streamGETRetrieves a Ceramic stream by its unique StreamID. Returns current content, metadata, controllers, and anchoring status.
get_stream_contentGet stream contentGETRetrieves only the JSON content of a Ceramic stream, without the full state envelope.
multiquery_streamsMultiquery streamsPOSTQueries multiple Ceramic streams at once. Supports following links between streams using JSON paths.
request_anchorRequest anchorPOSTRequests blockchain anchoring for a Ceramic stream to create a timestamp proof.

Collection, 2 operations

count_collectionCount collectionPOSTReturns the count of documents in a ComposeDB collection matching query criteria.
query_collectionQuery collectionPOSTQueries a ComposeDB collection of ModelInstanceDocuments with cursor-based pagination.

Node, 2 operations

get_healthcheckGet healthcheckGETChecks the health and availability of the Ceramic node. Returns 'Alive!' or 'Insufficient resources'.
get_supported_chainsGet supported chainsGETReturns all CAIP-2 chain IDs supported by the Ceramic node for blockchain anchoring.

Commit, 1 operation

get_commitsGet commitsGETRetrieves the complete commit history for a Ceramic stream. Returns all versions from genesis to current state.

Feed, 1 operation

get_documents_feedGet documents feedGETReturns a Server-Sent Events stream of aggregation documents for building custom indexers.

Use Ceramic from Claude Code, Cursor or Codex

Connect Ceramic in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ceramic 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 Ceramic

Create your workspace
Sign up free. Nothing to install.
Connect Ceramic once
Add your Ceramic connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.

Ceramic integration FAQ

What can you do with the Ceramic integration?

LiveContext exposes 27 operations on Ceramic, covering admin, pin, stream and collection. Common uses include node administration, health monitoring and node configuration.