Integration

Bump.sh integration

Bump.sh hosts API documentation built from OpenAPI and AsyncAPI files. Deploy a new version of a documentation (on a branch, or as a temporary version), validate or preview a definition, compare two definitions and read the change summary with its breaking changes, release or unrelease a version, manage documentation branches, and list hubs with the APIs they contain. Deploying a version, releasing, unreleasing, promoting a branch and deleting a branch change what readers of the public documentation see, and diffs and previews are readable by anyone with their public URL, so a definition sent to any of them must hold no secrets. Deploying workflow documents to MCP servers is not exposed (those workflows run with the server's stored secrets), and the documentation change webhook is set up in the Bump.sh dashboard. Plans: branches and unrelease need the Pro plan and manual release a custom plan; a plan without the feature answers 400 with an upgrade message. Rate limits, per IP address: 30 requests per minute on diffs and previews, 100 per minute and 300 per 5 minutes overall. Authentication is a Bump.sh API key sent as Authorization: Token <key>; a key belongs to one documentation, one hub or the whole organization, and listing hubs needs an organization key.

Connect Bump.sh How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Bump.sh.Built from the 16 Bump.sh tools below, on the connection you add once.

What you can do with Bump.sh

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.

Version, 4 operations

deploy_versionDeploy versionPOSTDeploy a definition as the new current version of a documentation, for real: its readers see it unless manual release is on, so never send a definition holding secrets. Answers 204 with no body when nothing changed. Follow its state with get_version.
get_versionGet versionGETGet a documentation version: its state (enqueued, deploying, pending_search, deployed, releasing, released or errored), public URLs and the change summary against the previous version. Answers 202 with no body while still processing.
release_versionRelease versionPOSTRelease a deployed version for real: it becomes publicly visible in the documentation. Its state moves to releasing, then released; follow it with get_version. Needs a plan with manual release, else 400.
unrelease_versionUnrelease versionPOSTUnrelease a released version for real: it is no longer publicly visible and its changelog entry is removed. Its state moves to releasing, then deployed; follow it with get_version. Pro plan, else 400.

Branch, 3 operations

create_branchCreate branchPOSTCreate an empty branch in a documentation; deploy_version with branch_name fills it. The branch name appears in the public documentation URL. Answers 204 with no body when the branch already exists. Pro plan.
delete_branchDelete branchDELETEDelete a branch of a documentation for real. The default branch cannot be deleted (422). Answers 204 with no body on success. Pro plan.
list_branchesList branchesGETList the branches of a documentation: name, slug (used in its public URL and by delete_branch and set_default_branch) and whether it is the default branch. Branches need the Pro plan.

Diff, 2 operations

create_diffCreate diffPOSTCompare two API definitions (OpenAPI 2.x, 3.x, AsyncAPI 2.x), as content or URLs; returns the diff id for get_diff. Anyone with the diff's public URL can read both definitions: send no secrets. 30 per minute.
get_diffGet diffGETGet the result of a diff started with create_diff: breaking flag, public URL and the change summary in the formats asked. While the diff is still being processed it answers HTTP 202 with no body: call again a little later.

Hub, 2 operations

get_hubGet hubGETGet a hub with the list of APIs it contains (name, slug, version, public documentation URL, tags), in the APIs.json format.
list_hubsList hubsGETList the hubs of the organization (id, name, description, public URL, dates). Needs an organization-level API key.

Preview, 2 operations

create_previewCreate previewPOSTRender a definition (content or URL) on a temporary public preview URL that anyone with the link can open, for 30 minutes: send no secrets. Nothing is deployed. update_preview refreshes it. 30 per minute.
update_previewUpdate previewPUTReplace the content of a preview made by create_preview with a new definition (content or URL), shown on its public URL to anyone with the link; the preview then stays active for 30 minutes after this update. 30 requests per minute.

Api status, 1 operation

pingPingGETCheck that the Bump.sh API is up. Answers a pong sentence; it does not check the API key.

Definition, 1 operation

validate_definitionValidate definitionPOSTCheck that a definition (content or URL) is a valid OpenAPI or AsyncAPI file for a documentation, without deploying anything. Returns the detected specification; an invalid file answers 422 with the errors.

Set default, 1 operation

set_default_branchSet default branchPATCHMake a branch the default one: readers of the public documentation then see that branch by default. Acts for real. Answers 204 when done, 200 when it already was the default, 422 when the branch has no deployed version.

Use Bump.sh from Claude Code, Cursor or Codex

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

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