DebugBear (BYOK)

DebugBear (BYOK) — connector documentation

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

What DebugBear (BYOK) is for

DebugBear (BYOK) lets an AI assistant read your own DebugBear data through the DebugBear API with a key you supply (DebugBear admin API key (read-only keys work for reads)). Read-only: 6 tools (list_projects, get_project, get_project_page_metrics, get_page_metrics, get_analysis, get_experiment). 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 www.debugbear.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by DebugBear. DebugBear 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:

• "Which pages does DebugBear monitor for me?"
• "Which pages are in this DebugBear project?"
• "What are the latest performance scores of all my DebugBear pages?"
• "How did the performance score of this DebugBear page change in September?"
• "What were the results of DebugBear analysis 5556667778?"
• "Has my DebugBear experiment finished and how did the variant do?"

What it does

• list_projects: List all projects of the DebugBear account with their monitored pages (id, name, URL, region, test schedules and device). Needs an admin API key.
• get_project: Get one project with its monitored pages, test schedules and devices. Needs an admin API key.
• get_project_page_metrics: Get the recent results of all pages in a project: for each page the latest metrics such as performance.score and seo.score. Optionally only results before a date. The provider documents the metric keys only by example.
• get_page_metrics: Export the metric history of one monitored page between two dates (keys such as performance.score). The provider documents the metric keys only by example.
• get_analysis: Get an existing analysis (test result) without starting a new test: status, metrics, build and commit information. The provider documents the fields only loosely, so the full answer is returned.
• get_experiment: Get a DebugBear experiment; baselineMetrics and variantMetrics appear once hasFinished is true.

BYOK key

You bring your own DebugBear DebugBear admin API key (read-only keys work for reads) (https://www.debugbear.com/docs/getting-started-api-cli). 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 www.debugbear.com 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://www.debugbear.com/docs/api (the API this connector calls, with a BYOK key)

Live from the DebugBear API (www.debugbear.com) with a BYOK key; documentation: https://www.debugbear.com/docs/api. 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 DebugBear. DebugBear 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 DebugBear account.

Built for: Worldwide. Languages: English.

DebugBear (BYOK) — Privacy Policy

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

What DebugBear (BYOK) is. DebugBear (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own DebugBear data: Read your DebugBear web performance projects, monitored pages, stored test results, Lighthouse-based metrics and experiments with your own API key. You bring your own DebugBear DebugBear admin API key (read-only keys work for reads); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one DebugBear 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 www.debugbear.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If DebugBear 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 DebugBear receives. The request we make on your behalf, including the key and the arguments, under DebugBear's own terms and privacy policy. DebugBear acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer DebugBear 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 DebugBear 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. DebugBear (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 DebugBear at any time to end all access.

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

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

DebugBear (BYOK) — Terms of Service

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

1. The Service. DebugBear (BYOK) provides: Read your DebugBear web performance projects, monitored pages, stored test results, Lighthouse-based metrics and experiments with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own DebugBear credentials and only access data you are allowed to access. DebugBear's terms apply to your use of DebugBear; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by DebugBear. DebugBear and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data DebugBear returns, lightly trimmed; it may be incomplete, delayed or changed by DebugBear. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your DebugBear account.
6. 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 DebugBear's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; DebugBear may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your DebugBear key.
10. 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 DebugBear takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-debugbear

DebugBear (BYOK) support

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

• MCP endpoint: https://byok-debugbear.connectorbay.com/mcp
• REST API: https://byok-debugbear.connectorbay.com/openapi.json
• Live status: https://byok-debugbear.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. DebugBear (BYOK) never asks for them.