Integration

Web3.Storage integration

[DEPRECATED - shut down January 9, 2024] The web3.storage REST API at api.web3.storage was shut down on January 9, 2024 and the repository is archived; no new uploads are accepted. The successor service is Storacha (storacha.network) using the w3up UCAN protocol, which is not a drop-in REST replacement (see https://github.com/web3-storage/w3up). Web3.Storage provides simple APIs for storing and retrieving data on IPFS and Filecoin. Built on the decentralized web stack, it offers content-addressed storage with cryptographic verification, automatic Filecoin deals for long-term persistence, and global CDN access through IPFS gateways. Perfect for NFTs, dApps, archival storage, and any application requiring verifiable, decentralized data storage.

Connect Web3.Storage How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Web3.Storage.Built from the 11 Web3.Storage tools below, on the connection you add once.

Common Web3.Storage use cases

Organize uploads
Check API version
large file uploads
storing NFT assets
managing storage quota
downloading stored files
monitoring storage usage
verifying content exists
managing uploaded content
verifying storage success

What you can do with Web3.Storage

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.

Upload, 4 operations

delete_uploadDelete uploadDELETERemoves an upload from your Web3.Storage account. Content may persist on IPFS/Filecoin but is no longer tracked or counted against your storage.
get_uploadGet uploadGETRetrieves metadata for a single upload by CID from your Web3.Storage account.
list_uploadsList uploadsGETLists all uploads in your Web3.Storage account. Supports pagination, date filtering, and sorting for easy content management.
rename_uploadRename uploadPOSTRenames an upload in your Web3.Storage account by CID.

Object, 2 operations

get_infoGet infoHEADRetrieves metadata about stored content including size and type without downloading. Quick way to verify content existence.
retrieveRetrieveGETDownloads content from Web3.Storage by CID. Access files directly or navigate directories with path suffixes.

Account, 1 operation

get_accountGet accountGETRetrieves your Web3.Storage account details including storage usage, limits, and plan information.

Car, 1 operation

upload_carUpload carPOSTUploads a CAR (Content Addressable aRchive) file to Web3.Storage. Ideal for large uploads or when you need to control the exact DAG structure.

File, 1 operation

uploadUploadPOSTUploads files to IPFS via Web3.Storage with automatic Filecoin backup. Returns the root CID for accessing your content on the decentralized web.

Status, 1 operation

get_statusGet statusGETRetrieves detailed status for stored content including IPFS pinning status and Filecoin storage deals. Track the lifecycle of your uploaded data.

Version, 1 operation

get_versionGet versionGETReturns version information about the Web3.Storage API deployment.

Use Web3.Storage from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Web3.Storage once
Add your Web3.Storage 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.

Web3.Storage integration FAQ

What can you do with the Web3.Storage integration?

LiveContext exposes 11 operations on Web3.Storage, covering upload, object, account and car. Common uses include Organize uploads, Check API version and large file uploads.