Integration

Merge File Storage integration

Merge File Storage is Merge's unified API for cloud file storage: one call shape reads whichever service (Google Drive, OneDrive, SharePoint, Box, Dropbox) a Merge Linked Account connects. List and read drives, folders and files with their names, sizes, MIME types, links and permissions, download a file's content through Merge (Google Workspace documents exported to a chosen format), list the users and groups of the account, create folders, and read which fields a folder creation needs. Not exposed: file upload (how the content is sent is not documented on the reference), the direct-download request metadata (it returns the end user's own access token), raw third-party records (remote data), passthrough requests and Linked Account, key, webhook, field mapping, scope and sync administration. Calls go to Merge's US region (api.merge.dev). Authentication is a Merge API key (Authorization: Bearer) plus one Linked Account's account token (X-Account-Token), so one connection reads one storage account.

Connect Merge File Storage How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Merge File Storage.Built from the 16 Merge File Storage tools below, on the connection you add once.

What you can do with Merge File 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.

Folder, 3 operations

create_folderCreate folderPOSTCreates a folder in the connected storage service, inside parent_folder or a drive (public beta). Call get_folder_create_metadata first: required fields vary by service.
get_folderGet folderGETReturns a `Folder` object with the given `id`.
list_foldersList foldersGETReturns a list of `Folder` objects.

Drive, 2 operations

get_driveGet driveGETReturns a `Drive` object with the given `id`.
list_drivesList drivesGETReturns a list of `Drive` objects.

File, 2 operations

get_fileGet fileGETReturns a `File` object with the given `id`.
list_filesList filesGETReturns a list of `File` objects.

Group, 2 operations

get_groupGet groupGETReturns a `Group` object with the given `id`.
list_groupsList groupsGETReturns a list of `Group` objects.

User, 2 operations

get_userGet userGETReturns a `User` object with the given `id`.
list_usersList usersGETReturns a list of `User` objects.

Account detail, 1 operation

get_account_detailsGet account detailsGETReturns the Linked Account behind the connection: integration name and slug, category, status, end user organization and email, and account type.

Available action, 1 operation

get_available_actionsGet available actionsGETReturns the integration behind the Linked Account and, per Common Model, the operations it supports (FETCH, CREATE...), the fields it fills and the parameters a create must send.

Download, 1 operation

download_fileDownload fileGETDownloads the content of a file through Merge and stores it as a file. mime_type exports a Google Drive document (Docs, Sheets, Slides, Drawings) to another format; other files download as stored.

Post, 1 operation

get_folder_create_metadataGet folder create metadataGETReturns the request schema the connected file storage system accepts to create a folder: fields, required ones and integration-specific parameters. Call it before the write.

Sync status, 1 operation

get_sync_statusGet sync statusGETReturns the sync state of each Common Model for the Linked Account: last and next sync start, last result and finish time. Data read through the other tools is as fresh as the last sync.

Use Merge File Storage from Claude Code, Cursor or Codex

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

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