Bump.sh MCP server and API connector for AI agents

Q: How do I connect Bump.sh to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-bumpsh.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-bumpsh.connectorbay.com/v1/tools/ ; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-bumpsh.json.

Try asking

Real questions, and the tools your agent calls to answer them.

Is the Bump.sh API reachable?

Tools called

get_api_status

Which documentation hubs does my Bump.sh organization have?

Tools called

list_hubs

What APIs are listed in my Bump.sh hub docs-hub?

Tools called

get_hub

What branches does my Bump.sh documentation pets have?

Tools called

list_branches

Did my last Bump.sh deployment break anything?

Tools called

get_version

Is Bump.sh diff 3f2a1b0c breaking?

Tools called

get_diff

About

Bump.sh (BYOK) lets an AI assistant read your own Bump.sh data through the Bump.sh API with a key you supply (Bump.sh documentation or organization API token). Read-only: 6 tools (get_api_status, list_hubs, get_hub, list_branches, get_version, get_diff). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to bump.sh. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bump.sh. Bump.sh and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Bump.sh API (bump.sh) with a BYOK key; documentation: https://developers.bump.sh/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

Privacy policy Terms

What it can do

6 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI

Read your data6 tools

Get api statusCheck that the Bump.sh API is up.
List hubsList the documentation hubs of your Bump.sh organization.
Get hubGet one Bump.sh hub by id or slug, including the APIs it contains (name, slug, version, URLs, tags).
List branchesList the branches of one Bump.sh documentation with name, slug and whether it is the default branch.
Get versionGet one deployed Bump.sh documentation version: deployment state, change summary and whether the change is breaking.
Get diffGet one stored Bump.sh API change diff: title, public URL and whether it contains breaking changes.

Information

PublisherUnify Dynamics LLC

CategoryDeveloper tools

LanguagesEnglish

Built forWorldwide

CompatibilityAny MCP client · any agent · REST

Version0.1.0

MCP endpointhttps://byok-bumpsh.connectorbay.com/mcp

REST APIopenapi.json

SupportGet help · Status

CountryWorldwide

FunctionOther

LayerDeep connectors

Connect it to your agent

Three ways in, the same 6 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-bumpsh.connectorbay.com/mcp

RESTPOST https://byok-bumpsh.connectorbay.com/v1/tools/<tool>

OpenAI function callinghttps://connectorbay.com/openai/byok-bumpsh.json

OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works

Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
Key: send your Bump.sh documentation or organization API token in the X-Upstream-Key header (get one at docs.bump.sh).
Ask a question; the agent picks the right tool and answers from the live data.

Bump.sh connector: questions and answers

What is the Bump.sh connector?

Bump.sh (BYOK) lets an AI assistant read your own Bump.sh data through the Bump.sh API with a key you supply (Bump.sh documentation or… It is a hosted MCP server with 6 tools such as Get api status, List hubs, Get hub, List branches, Get version, Get diff, published by Unify Dynamics LLC. It is independent and not affiliated with Bump.sh.

How do I connect Bump.sh to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-bumpsh.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-bumpsh.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-bumpsh.json.

Do I need a Bump.sh account or API key?

Yes: this is a bring-your-own-key connector. Create a Bump.sh documentation or organization API token at https://docs.bump.sh/help/continuous-integration/api/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Bump.sh read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Bump.sh connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

GitHub Repo Insights (BYOK)

Read GitHub repository traffic, clone counts, referrers, commit activity, contributor statistics, languages and community health with your own personal access token

Live · MCP + REST12 tools

GitHub Rulesets (BYOK)

Read GitHub repository and organization rulesets, rule evaluation history and the rules that apply to a branch with your own token

Live · MCP + REST9 tools

GitHub Search (BYOK)

Search GitHub code, commits, users, topics and labels with qualifiers using your own personal access token

Live · MCP + REST5 tools

GitHub Secret Scanning (BYOK)

Read GitHub secret scanning alerts across an organization, alert locations, scan history and custom patterns with your own personal access token; secret values are never returned

Live · MCP + REST7 tools

GitHub Supply Chain (BYOK)

Read GitHub artifact attestations, artifact storage and deployment records and immutable release settings of an organization with your own token

Live · MCP + REST7 tools

GitHub Teams (BYOK)

Read GitHub team hierarchy, your team and organization memberships, team invitations and organization role teams with your own personal access token

Live · MCP + REST8 tools

Documentation

Back to top

Bump.sh (BYOK) — connector documentation

MCP endpoint: https://byok-bumpsh.connectorbay.com/mcp
REST API: POST https://byok-bumpsh.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-bumpsh.connectorbay.com/openapi.json
Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
Authentication: your own Bump.sh Bump.sh documentation or organization API token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
Health: https://byok-bumpsh.connectorbay.com/health · Tool schemas: https://byok-bumpsh.connectorbay.com/tools.json
Publisher: Unify Dynamics LLC · connectorbay.com/byok-bumpsh · agent@connectorbay.com

What Bump.sh (BYOK) is for

Bump.sh (BYOK) lets an AI assistant read your own Bump.sh data through the Bump.sh API with a key you supply (Bump.sh documentation or organization API token). Read-only: 6 tools (get_api_status, list_hubs, get_hub, list_branches, get_version, get_diff). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to bump.sh. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bump.sh. Bump.sh and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

"Is the Bump.sh API reachable?"
"Which documentation hubs does my Bump.sh organization have?"
"What APIs are listed in my Bump.sh hub docs-hub?"
"What branches does my Bump.sh documentation pets have?"
"Did my last Bump.sh deployment break anything?"
"Is Bump.sh diff 3f2a1b0c breaking?"

What it does

get_api_status: Check that the Bump.sh API is up.
list_hubs: List the documentation hubs of your Bump.sh organization. Needs an organization-level token.
get_hub: Get one Bump.sh hub by id or slug, including the APIs it contains (name, slug, version, URLs, tags).
list_branches: List the branches of one Bump.sh documentation with name, slug and whether it is the default branch.
get_version: Get one deployed Bump.sh documentation version: deployment state, change summary and whether the change is breaking.
get_diff: Get one stored Bump.sh API change diff: title, public URL and whether it contains breaking changes.

BYOK key

You bring your own Bump.sh Bump.sh documentation or organization API token (https://docs.bump.sh/help/continuous-integration/api/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to bump.sh over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

https://developers.bump.sh/ (the API this connector calls, with a BYOK key)

Live from the Bump.sh API (bump.sh) with a BYOK key; documentation: https://developers.bump.sh/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bump.sh. Bump.sh and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Bump.sh account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Bump.sh (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Bump.sh (BYOK) is. Bump.sh (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Bump.sh data: Read your Bump.sh API documentation hubs, branches, deployed versions and API change diffs with your own token. You bring your own Bump.sh Bump.sh documentation or organization API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Bump.sh call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to bump.sh, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Bump.sh rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Bump.sh receives. The request we make on your behalf, including the key and the arguments, under Bump.sh's own terms and privacy policy. Bump.sh acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Bump.sh gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Bump.sh data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Bump.sh (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Bump.sh at any time to end all access.

Children. Bump.sh (BYOK) is a general-audience service operated by the adult using the assistant, under Bump.sh's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Bump.sh (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Bump.sh (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

The Service. Bump.sh (BYOK) provides: Read your Bump.sh API documentation hubs, branches, deployed versions and API change diffs with your own token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
Your own key, your own account. You must use your own Bump.sh credentials and only access data you are allowed to access. Bump.sh's terms apply to your use of Bump.sh; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bump.sh. Bump.sh and its logos are trademarks of their owners and are used only to say which service the connector works with.
No advice, no guarantees. Output is the data Bump.sh returns, lightly trimmed; it may be incomplete, delayed or changed by Bump.sh. Check important facts at the source.
Read-only. The Service does not create, change, send or delete anything in your Bump.sh account.
Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Bump.sh's controls, or to attack any system.
Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Bump.sh may change or end its API at any time.
Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Bump.sh key.
Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Bump.sh takes on your account. Our total liability is limited to US $100.
Governing law. California law; venue in San Mateo County, California.
Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-bumpsh

Support

Back to top

Bump.sh (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

MCP endpoint: https://byok-bumpsh.connectorbay.com/mcp
REST API: https://byok-bumpsh.connectorbay.com/openapi.json
Live status: https://byok-bumpsh.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Bump.sh (BYOK) never asks for them.