Buildkite Agents (BYOK)
Read your Buildkite agents, clusters and cluster queues with your own API access token (read_agents and read_clusters scopes)
Read your Budibase Cloud apps, tables, rows, users and saved queries with your own API key and app id
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
search_appsget_appsearch_tablesget_tablelist_rowsget_rowBudibase (BYOK) lets an AI assistant read your own Budibase data through the Budibase API with a key you supply (Budibase API key). Read-only: 9 tools (search_apps, get_app, search_tables, get_table, list_rows, get_row, search_users, get_user, search_queries). 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 budibase.app. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Budibase. Budibase and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Budibase API (budibase.app) with a BYOK key; documentation: https://docs.budibase.com/docs/public-api. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
9 tools, grouped by job. Every one is read-only or compute-only.
https://byok-budibase.connectorbay.com/mcpThree ways in, the same 9 tools.
https://byok-budibase.connectorbay.com/mcpPOST https://byok-budibase.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-budibase.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at docs.budibase.com).Budibase (BYOK) lets an AI assistant read your own Budibase data through the Budibase API with a key you supply (Budibase API key). It is a hosted MCP server with 9 tools such as Search apps, Get app, Search tables, Get table, List rows, Get row, published by Unify Dynamics LLC. It is independent and not affiliated with Budibase.
Add the MCP endpoint https://byok-budibase.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-budibase.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-budibase.json.
Yes: this is a bring-your-own-key connector. Create a Budibase API key at https://docs.budibase.com/docs/public-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.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Buildkite agents, clusters and cluster queues with your own API access token (read_agents and read_clusters scopes)
Read your Buildkite pipeline templates, build schedules, teams and access rules with your own API access token
Read your Buildkite Test Engine suites, test runs and failed test executions with your own API access token (read_suites scope)
Read your Bump.sh API documentation hubs, branches, deployed versions and API change diffs with your own token
Search German Bundestag proceedings, printed papers, plenary protocols, parliamentary activities and members through the DIP API with your own key
Read your bunny.net pull zones, storage zones, DNS zones and records, video libraries, statistics and billing summary with BYOK
https://byok-budibase.connectorbay.com/mcpPOST https://byok-budibase.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-budibase.connectorbay.com/openapi.jsonX-Upstream-Key header and the Budibase app id (app_... for the published app, app_dev_... for the draft) in X-Upstream-Key-2 of every request (never stored, logged or cached)https://byok-budibase.connectorbay.com/health · Tool schemas: https://byok-budibase.connectorbay.com/tools.jsonBudibase (BYOK) lets an AI assistant read your own Budibase data through the Budibase API with a key you supply (Budibase API key). Read-only: 9 tools (search_apps, get_app, search_tables, get_table, list_rows, get_row, search_users, get_user, search_queries). 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 budibase.app. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Budibase. Budibase 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:
search_apps: Search Budibase apps by name prefix; returns id, name, status (development or published), url and update time.get_app: Get one Budibase app by id: name, status, url and timestamps.search_tables: Search tables of the configured app by name prefix; returns id, name, primary display column and schema.get_table: Get one Budibase table of the configured app, with its column schema.list_rows: List rows of a Budibase table (no filter), optionally paginated with a bookmark; limit is capped at 1000 for internal tables.get_row: Get one Budibase row by id, with related rows expanded.search_users: Search Budibase users by name prefix; returns email, name, roles and status. Passwords are never kept in the answer.get_user: Get one Budibase user by id: email, name, roles and status.search_queries: Search saved queries of the configured app by name prefix (listing only; queries are not executed).You bring your own Budibase Budibase API key (https://docs.budibase.com/docs/public-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 budibase.app 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.
Live from the Budibase API (budibase.app) with a BYOK key; documentation: https://docs.budibase.com/docs/public-api. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Budibase. Budibase 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 Budibase account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Budibase (BYOK) is. Budibase (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Budibase data: Read your Budibase Cloud apps, tables, rows, users and saved queries with your own API key and app id. You bring your own Budibase Budibase API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Budibase 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 budibase.app, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Budibase 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 Budibase receives. The request we make on your behalf, including the key and the arguments, under Budibase's own terms and privacy policy. Budibase acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Budibase 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 Budibase 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. Budibase (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 Budibase at any time to end all access.
Children. Budibase (BYOK) is a general-audience service operated by the adult using the assistant, under Budibase's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Budibase (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-budibase.connectorbay.com/mcphttps://byok-budibase.connectorbay.com/openapi.jsonWhen 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. Budibase (BYOK) never asks for them.