Integration

Bump.sh Portal integration

Read any public API documentation portal hosted on Bump.sh (a documentation, a hub or an organization portal) as structured content: search its pages by keyword, browse its page tree, fetch up to 10 pages at once as Markdown with their code, request and response examples, and read its changelog of API changes. Useful to feed an API's documentation to an agent or to watch an API for changes. Only public documentation is reachable; every tool names the portal in Portal-Url, and an unknown portal answers 404. No authentication: the API takes no key.

Connect Bump.sh Portal How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Bump.sh Portal

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.

Documentation page, 2 operations

fetch_pagesFetch pagesGETGet the full content of 1 to 10 pages of a Bump.sh portal as Markdown. Operation pages also carry their code samples, request examples and response examples with status codes.
search_pagesSearch pagesGETSearch the pages of a Bump.sh portal by keyword (titles, content, metadata). Returns at most 20 matches with no paging (metadata.total gives the full count): narrow with url or type. Read a page with fetch_pages.

List, 2 operations

list_changesList changesGETList the public changelog of a hub, an API documentation or one version on a Bump.sh portal: each change with its title, date, public URL and the diff in Markdown. Up to 20 changes per page.
list_pagesList pagesGETList the child pages under a page of a Bump.sh portal (URL, title, type and a short description). Leave url out to start from the portal's top level, then pass a returned URL to go deeper.

Documentation change, 1 operation

get_changeGet changeGETGet one change from the public changelog of a Bump.sh portal: title, date, public URL and the diff in Markdown.

Use Bump.sh Portal from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Bump.sh Portal once
Bump.sh Portal needs no credential, so its tools work immediately.
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.