Integration

Brault integration

Brault is a creative file management platform (a digital asset library for creative teams). Organize libraries, folders and files, import files from public URLs, search them by keyword or natural language, convert media, build ZIP downloads, manage versions, comments and replies, boards with custom properties, brandspace-wide properties, pages, shared links and expiring transfer links, and webhook endpoints. Not exposed: the presigned upload flow (file bytes go straight to a storage URL that cannot take the connection's key; use import_file_from_url instead), transfers with uploads, and rolling a webhook signing secret. Authentication is a Brault API key (bsk_...) created in Settings > Developers > API keys (Lite plan or higher), sent as a Bearer token; it acts as the member who created it, limited to its scopes. Content calls go to the US regional host (us.api.brault.app, the only region today) and the account, member and usage calls to api.brault.app.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Brault

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Property, 12 operations

  • create_board_propertyCreate board propertyPOSTAgents: ask firstCreates a property on a board: status, person, date, checkbox, text or multi_tag. options seeds a status property; a multi_tag property starts with one default option.
  • create_brandspace_propertyCreate brandspace propertyPOSTAgents: ask firstCreates a brandspace-wide file property: tag, text, date, checkbox or person (tag properties allow single or multiple selection). Visible on every file of the brandspace.
  • delete_board_propertyDelete board propertyDELETEAgents: ask firstPermanently deletes a board property with its options and every value files hold for it.
  • delete_brandspace_propertyDelete brandspace propertyDELETEAgents: ask firstPermanently deletes a brandspace property with its options and every value files hold for it.
  • get_board_propertyGet board propertyGETAgents: ask firstReturns one board property with its type, selection mode and options.
  • get_brandspace_propertyGet brandspace propertyGETAgents: ask firstReturns one brandspace property with its type, selection mode and options.
  • list_board_propertiesList board propertiesGETAgents: ask firstLists a board's properties in position order, each with its options. Paged with cursor and next_cursor.
  • list_brandspace_propertiesList brandspace propertiesGETAgents: ask firstLists the brandspace-wide properties (the metadata schema shared by all files) in position order, each with its options. Paged with cursor.
  • set_board_file_valueSet board file valuePUTAgents: ask firstSets a file's value for one board property. Send exactly one field, the one named after the property's type (status, person, date, checkbox, text or multi_tag). Returns the file's board entry with its values.
  • set_file_property_valueSet file property valuePUTAgents: ask firstSets a file's value for one brandspace property. Send exactly one field, the one named after the property's type: tag (add and remove option ids), text, date, checkbox or person.
  • update_board_propertyUpdate board propertyPATCHAgents: ask firstRenames a board property. The name is the only editable field: a property's type and position are fixed.
  • update_brandspace_propertyUpdate brandspace propertyPATCHAgents: ask firstRenames a brandspace property or changes the selection mode of a tag property. Only the fields sent change.

Board, 6 operations

  • create_boardCreate boardPOSTAgents: ask firstCreates a board, a collection that groups files with custom properties independently of their folders. default_property_type seeds one property (status seeds To Do, In Progress, Done). Members of the board see it.
  • delete_boardDelete boardDELETEAgents: ask firstPermanently deletes a board (boards have no trash) with its properties, options, memberships and values. The files themselves are untouched.
  • get_boardGet boardGETAgents: ask firstReturns one board with its properties and their options (property and option ids are what set_board_file_value and query_board_files take).
  • list_boardsList boardsGETAgents: ask firstLists the boards the key's creator can see (all of them when their role manages all boards), pinned first. Paged: pass next_cursor back as cursor while has_more is true.
  • list_file_boardsList file boardsGETAgents: ask firstLists the boards a file is on, limited to boards the key's creator can see. Single page.
  • update_boardUpdate boardPATCHAgents: ask firstUpdates a board's name, color, emoji or pinned flag. Only the fields sent change; leave a field out to keep its current value.

File, 6 operations

  • add_board_filesAdd board filesPOSTAgents: ask firstAdds files to a board. Each id comes back as added or already on the board; one id the key cannot reach fails the whole call (404) before anything is added. Needs edit rights on each file's library or folder.
  • delete_fileDelete fileDELETEAgents: ask firstMoves a file to the trash (restore_file brings it back). permanent=true deletes the file and all its versions irreversibly.
  • get_fileGet fileGETAgents: ask firstReturns a file's full metadata: kind, size, status, location, tags, version info, property values and rendition URLs signed for 15 minutes. The original file is not included: use get_file_download_url.
  • list_filesList filesGETAgents: ask firstLists the files the key's creator can see (folders never included), filtered by library, folder, keyword or natural-language query, extension, kind, dates, uploader, size or a property filter. Paged with cursor.
  • remove_board_fileRemove board fileDELETEAgents: ask firstRemoves a file from a board, with this board's property values for it. The file itself stays where it lives; a file not on the board answers 404.
  • update_fileUpdate filePATCHAgents: ask firstRenames a file, replaces its whole tag set, or points a link file at a new URL. Every field is optional; leave one out to keep its current value.

Option, 6 operations

  • create_board_property_optionCreate board property optionPOSTAgents: ask firstAdds an option to a status or multi_tag board property, with a label and an optional hex color.
  • create_brandspace_property_optionCreate brandspace property optionPOSTAgents: ask firstAdds an option to a tag brandspace property, with a label and an optional hex color.
  • delete_board_property_optionDelete board property optionDELETEAgents: ask firstDeletes an option of a board property and clears it from every file: a status value pointing at it becomes unset, a multi_tag value loses that tag.
  • delete_brandspace_property_optionDelete brandspace property optionDELETEAgents: ask firstDeletes an option of a brandspace tag property; files that carried it lose that tag.
  • update_board_property_optionUpdate board property optionPATCHAgents: ask firstUpdates an option of a board property: label, color or hidden (a hidden option stays a valid value, the web app folds it away). Only the fields sent change.
  • update_brandspace_property_optionUpdate brandspace property optionPATCHAgents: ask firstUpdates an option of a brandspace property: label, color or hidden. Only the fields sent change.

Comment, 5 operations

  • create_file_commentCreate file commentPOSTAgents: ask firstPosts a comment on a file (or page), optionally anchored to a time in a video or audio, to annotations or to one version. Visible to everyone with access to the file; a [@user_id] token mentions and notifies a member.
  • delete_commentDelete commentDELETEAgents: ask firstPermanently deletes a comment and its replies. Allowed for its author or a brandspace owner or admin.
  • get_commentGet commentGETAgents: ask firstReturns one comment on a file: text, author, mentions, anchors, resolved state and timestamps.
  • list_file_commentsList file commentsGETAgents: ask firstLists a file's comments, oldest first, with author, text, mentions, time anchor and annotations. Filter by resolved or version_id. Comment authors are people: names are personal data.
  • update_commentUpdate commentPATCHAgents: ask firstReplaces a comment's text. Only its author may edit it; anyone else gets 404.

Folder, 5 operations

  • create_folderCreate folderPOSTAgents: ask firstCreates a folder at the root of a library (library_id) or inside another folder (folder_id). Give exactly one of the two.
  • delete_folderDelete folderDELETEAgents: ask firstMoves a folder to the trash with its contents (restore_folder brings it back). permanent=true deletes it and everything in it irreversibly.
  • get_folderGet folderGETAgents: ask firstReturns one folder: name, color, library, parent folder and timestamps.
  • list_foldersList foldersGETAgents: ask firstLists the folders the key's creator can see, filtered by library or parent folder, direct children only unless recursive is true. Paged with cursor.
  • update_folderUpdate folderPATCHAgents: ask firstRenames or recolors a folder. Only the fields sent change.

Library, 5 operations

  • create_libraryCreate libraryPOSTAgents: ask firstCreates a library, the top-level container for folders and files, with a name and an optional description and emoji.
  • delete_libraryDelete libraryDELETEAgents: ask firstDeletes a library IMMEDIATELY with every folder and file it contains: libraries have no trash step and this cannot be undone. List its contents first if unsure.
  • get_libraryGet libraryGETAgents: ask firstReturns one library with its file count, folder count and total size in bytes.
  • list_librariesList librariesGETAgents: ask firstLists the libraries (top-level containers) the key's creator can see. Paged with cursor.
  • update_libraryUpdate libraryPATCHAgents: ask firstRenames a library or changes its description. Only the fields sent change.

Shared link, 5 operations

  • create_shared_linkCreate shared linkPOSTAgents: ask firstCreates a public shared link to a file, folder, library or board, with view, download, review or upload access, an optional password and expiry. The returned url gives that access to anyone who has it.
  • delete_shared_linkDelete shared linkDELETEAgents: ask firstPermanently deletes a shared link: visitors holding the URL lose access at once.
  • get_shared_linkGet shared linkGETAgents: ask firstReturns one shared link: its url (a capability link), target, access level, password and expiry state, display settings and view count.
  • list_shared_linksList shared linksGETAgents: ask firstLists the brandspace's shared links, newest first (file-scoped links are not included). Each url is a capability link: anyone holding it gets the access it grants.
  • update_shared_linkUpdate shared linkPATCHAgents: ask firstChanges a shared link's access, password, expiry, comments, display or board views. Fields apply in order and stop at the first failure; re-read the link with get_shared_link to see its state.

Transfer, 5 operations

  • create_transferCreate transferPOSTAgents: ask firstPackages Brault files and folders into one expiring public download link (default 7 days) and returns its url, a capability link anyone can open. The zip builds in the background: poll get_transfer for status ready.
  • expire_transferExpire transferDELETEAgents: ask firstExpires a transfer immediately: recipients lose access at once and it is deleted for good.
  • get_transferGet transferGETAgents: ask firstReturns a transfer with its files and folders, its url (a capability link) and, once status is ready, a freshly signed zip_url for the whole package.
  • list_transfersList transfersGETAgents: ask firstLists the brandspace's transfers (expiring download links), newest first. Each url is a capability link anyone can open. Paged with cursor.
  • update_transferUpdate transferPATCHAgents: ask firstSets or changes a transfer's password, or moves its expiry (days counted from today; the expiry can be moved once). Only the fields sent change.

Webhook, 5 operations

  • create_webhookCreate webhookPOSTAgents: ask firstRegisters a webhook endpoint that receives Brault events. The url must be public https on port 443 or 8443 and answer 2xx quickly. The signing secret is withheld here, so deliveries to it cannot be verified.
  • delete_webhookDelete webhookDELETEAgents: ask firstDeletes a webhook endpoint: pending deliveries are cancelled and it stops receiving events at once.
  • get_webhookGet webhookGETAgents: ask firstReturns one webhook endpoint: url, events, status, disabled reason, failure counter and last delivery times.
  • list_webhooksList webhooksGETAgents: ask firstLists the brandspace's webhook endpoints, newest first, with url, subscribed events, status and delivery health.
  • update_webhookUpdate webhookPATCHAgents: ask firstChanges a webhook endpoint's url, name, events (replaces the list) or status (active or paused). Setting active again resumes a disabled endpoint. Only the fields sent change.

Page, 4 operations

  • create_pageCreate pagePOSTAgents: ask firstCreates a page (a structured document) in a library, a folder or the brandspace root, optionally with initial content blocks. It stays private until publish_page.
  • delete_pageDelete pageDELETEAgents: ask firstMoves a page to the trash. permanent=true deletes it and its comments irreversibly.
  • get_pageGet pageGETAgents: ask firstReturns a page with its content, as the stored ProseMirror JSON (format=json) or rendered as Markdown (format=markdown), plus its published state and public_url.
  • list_pagesList pagesGETAgents: ask firstLists the pages (structured documents) the key's creator can see, newest first, by library or folder. Paged with cursor.

Reply, 4 operations

  • create_comment_replyCreate comment replyPOSTAgents: ask firstPosts a reply to a comment on a file, visible to everyone with access to the file; a [@user_id] token mentions and notifies a member.
  • delete_comment_replyDelete comment replyDELETEAgents: ask firstPermanently deletes a reply. Allowed for its author or a brandspace owner or admin.
  • list_comment_repliesList comment repliesGETAgents: ask firstLists the replies to a comment, oldest first, with author and mentions. Paged with cursor.
  • update_comment_replyUpdate comment replyPATCHAgents: ask firstReplaces a reply's text. Only its author may edit it; anyone else gets 404.

Conversion, 3 operations

  • cancel_conversionCancel conversionDELETEAgents: ask firstCancels a queued or running conversion started by this key. A canceled conversion still counts against the daily conversion quota.
  • convert_fileConvert filePOSTAgents: ask firstStarts (or returns the running) conversion of a file to another format, size or codec. Asynchronous: poll get_conversion until status is ready. Needs a plan with media conversion; counts against daily conversions.
  • get_conversionGet conversionGETAgents: ask firstReturns a conversion job: status, progress, ETA and, once status is ready, url (a download link valid 24 hours). Poll this after convert_file; fetching url does not count as a download.

Download, 3 operations

  • create_zip_downloadCreate zip downloadPOSTAgents: ask firstStarts building a ZIP of files and folders (original, preview or thumbnail renditions). Asynchronous: poll get_zip_download until status is ready, then use url. Counts against the daily download issuances.
  • get_file_download_urlGet file download urlGETAgents: ask firstReturns a signed download URL for a file, valid 15 minutes: the original, a preview or a thumbnail, or a custom image rendition. Counts against the plan's daily download issuances.
  • get_zip_downloadGet zip downloadGETAgents: ask firstReturns a ZIP download job started by create_zip_download: status, progress, object count, size and, once ready, url to download the archive.

Member, 3 operations

  • get_memberGet memberGETAgents: ask firstReturns one brandspace member: name, email, avatar, role and join date (personal data; needs members:read). Use it to resolve a user id from comments, boards or authorship.
  • list_board_membersList board membersGETAgents: ask firstLists the user ids that can access a board (explicit grants plus roles that manage all boards). Single page. Resolve a name or email with get_member.
  • list_membersList membersGETAgents: ask firstLists the brandspace's members with their name, email, avatar, role and join date (personal data; needs the members:read scope). Paged with cursor.

Delivery, 2 operations

  • get_webhook_deliveryGet webhook deliveryGETAgents: ask firstReturns one webhook delivery attempt: event, status, attempt number, HTTP status, duration, error code and an excerpt of the receiver's answer.
  • list_webhook_deliveriesList webhook deliveriesGETAgents: ask firstLists a webhook endpoint's deliveries, newest first, filterable by status: event, attempt, HTTP status, duration and an excerpt of the receiver's answer. Kept 30 days, at most 10,000.

Import, 2 operations

  • get_importGet importGETAgents: ask firstReturns a URL import started by import_file_from_url: status, bytes written, error code and, when done, the new file_id.
  • import_file_from_urlImport file from urlPOSTAgents: ask firstImports a file from a public http(s) URL into a library or folder (at most 5 GiB, 2 imports at a time per brandspace). Asynchronous: poll get_import until status is succeeded or failed, then read file_id.

Move, 2 operations

  • move_fileMove filePOSTAgents: ask firstMoves a file to a library, a folder, or the brandspace root (All files). Give exactly one of library_id, folder_id or to_root.
  • move_folderMove folderPOSTAgents: ask firstMoves a folder into another library (library_id) or under another folder (folder_id). Give exactly one; folders always belong to a library.

Restore, 2 operations

  • restore_fileRestore filePOSTAgents: ask firstRestores a file from the trash to where it was. Returns the file.
  • restore_folderRestore folderPOSTAgents: ask firstRestores a folder from the trash with its contents. Returns the folder.

Version, 2 operations

  • delete_file_versionDelete file versionDELETEAgents: ask firstPermanently deletes one version of a file, its bytes and every comment attached to it. Not a trash operation.
  • list_file_versionsList file versionsGETAgents: ask firstLists a file's versions, newest first: number, size, type, status, author and which one is active.

Activate, 1 operation

  • activate_file_versionActivate file versionPOSTAgents: ask firstMakes one version of a file the active (current) one. Returns the file.

Block, 1 operation

  • append_page_blocksAppend page blocksPOSTAgents: ask firstAppends content blocks (paragraphs, headings, lists, code, quotes, dividers) at the end of a page; open editors see them at once. Not idempotent: a retry appends the blocks again, so re-read the page first.

Brandspace, 1 operation

  • get_brandspaceGet brandspaceGETAgents: ask firstReturns the brandspace (workspace) the API key belongs to: id, name, username, region and creation date. Works with any key scope.

Copy, 1 operation

  • copy_fileCopy filePOSTAgents: ask firstCopies a file into a library, a folder, or the brandspace root (All files). Give exactly one of library_id, folder_id or to_root. Returns the new file.

Event, 1 operation

  • list_webhook_event_typesList webhook event typesGETAgents: ask firstLists every webhook event type (for example file.created) with its group, a one-line description and the object its payload carries. Put these tokens in a webhook's events, or the single element *.

Me, 1 operation

  • get_meGet meGETAgents: ask firstReturns what the API key is: its brandspace and region, the key's name, scopes and expiry, who created it, the plan, its rate limits and quotas, and the hosts to call. Call it first to check access.

Merge, 1 operation

  • merge_file_versionsMerge file versionsPOSTAgents: ask firstMoves every version of source_file_id into this file as its next versions, then PERMANENTLY deletes the source file with its boards and links. Both files must be the same media type. Cannot be undone.

Publish, 1 operation

  • publish_pagePublish pagePOSTAgents: ask firstPublishes a page: anyone holding its public_url can then read it, without an account. Returns the page with public_url.

Query, 1 operation

  • query_board_filesQuery board filesPOSTAgents: ask firstReads the files on a board (a read sent as POST because its filter is a JSON document), with this board's values for each and when it was added. Filter, keyword, sort and paging; trashed files are never listed.

Redeliver, 1 operation

  • redeliver_webhook_deliveryRedeliver webhook deliveryPOSTAgents: ask firstSends an event to the endpoint again as a NEW delivery (attempt 1). Allowed when the source delivery succeeded or was exhausted, the endpoint is active and the event is under 30 days old.

Reopen, 1 operation

  • reopen_commentReopen commentPOSTAgents: ask firstReopens a resolved comment (clears resolved and resolved_by_id). Returns the comment.

Replay, 1 operation

  • replay_webhook_eventsReplay webhook eventsPOSTAgents: ask firstRe-sends to the endpoint every event of a time window (at most 7 days, within the last 30) that it subscribes to, skipping events already delivered unless include_delivered is true. At most 10,000 events.

Resolve, 1 operation

  • resolve_commentResolve commentPOSTAgents: ask firstMarks a comment as resolved. Anyone who can view the file may do it. Returns the comment.

Role, 1 operation

  • list_rolesList rolesGETAgents: ask firstLists the brandspace's roles with their slug, description, default flag and permission list. Paged with cursor.

Search, 1 operation

  • search_filesSearch filesGETAgents: ask firstSearches files and folders by keyword, meaning or natural language across the brandspace, one library or one folder. Counts against the search rate limit on every call.

Similar, 1 operation

  • list_similar_filesList similar filesGETAgents: ask firstLists files visually similar to a file (nearest neighbours of its embedding). Counts against the search rate limit.

Test, 1 operation

  • send_webhook_testSend webhook testPOSTAgents: ask firstSends a synthetic webhook.test event to the endpoint right now and returns the delivery. One attempt, no retry, counters untouched; a failed test is a 200 whose delivery status is exhausted.

Unpublish, 1 operation

  • unpublish_pageUnpublish pagePOSTAgents: ask firstUnpublishes a page: its public URL stops working at once. Returns the page.

Usage, 1 operation

  • get_usageGet usageGETAgents: ask firstReturns the brandspace's current API usage against its limits: the per-minute window, the monthly quota, and the search, upload, download and conversion counters, each with used, remaining and reset time.

Use Brault from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Brault once

    Add your Brault connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Brault integration FAQ

What can you do with the Brault integration?

LiveContext exposes 106 operations on Brault, covering property, board, file and option.

Popular integrations

Browse the whole catalog