Integration

FilePost integration

FilePost turns a file into a permanent public CDN URL. Upload a stored file, Base64 data or a copy of a public file URL, then list, inspect, delete, or change the filename visibility of the files on your account. Every uploaded file is public to anyone holding its URL, so do not upload confidential material. Account sign-up and settings, key rotation, plan and trial changes, account usage, intake links and webhooks are not exposed. Authentication is the FilePost API key (it starts with fh_), sent in the X-API-Key header.

Connect FilePost How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with FilePost

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.

bulk_delete_filesBulk delete filesPOSTPermanently deletes up to 100 files in one call (Starter and Pro plans only): like delete_file, each deleted file's public URL stops working. Unknown ids and ids owned by another account are not deleted and come back in not_deleted_file_ids.
delete_fileDelete fileDELETEPermanently deletes an uploaded file: its stored copy is removed and its public URL stops working. This cannot be undone.
get_fileGet fileGETReturns one uploaded file's metadata: its public URL, name, size in bytes, MIME type, creation and expiry times and filename mode.
list_filesList filesGETLists the files uploaded to the FilePost account, newest first: each file's id, public URL, name, size, MIME type, creation and expiry times. Paginated with page (from 1) and per_page (1 to 100, default 50).
set_file_filename_modeSet file filename modePATCHChooses whether a file's name appears in its public URL (public) or not (download). Hiding it revokes the previous filename-visible URL; showing it keeps the previous opaque URL working. The file is unchanged.
upload_base64_fileUpload base64 filePOSTUploads Base64-encoded file bytes (a data URL also works) under the given filename and returns the permanent public CDN URL and file_id. Use it when the content exists only as Base64 text; anyone with the URL can open it.
upload_fileUpload filePOSTUploads a stored file to FilePost and returns its permanent public CDN URL and file_id. Anyone with the URL can open the file. Optionally auto-delete it later (expires_in) and choose whether the filename appears in the URL.
upload_file_from_urlUpload file from urlPOSTCopies a public http or https file URL (an expiring attachment link, for example) into FilePost and returns a permanent public CDN URL and file_id. Anyone with the new URL can open the file. Needs an email-verified FilePost account.

Use FilePost from Claude Code, Cursor or Codex

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

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