Rollbar Occurrences (BYOK) — connector documentation

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

What Rollbar Occurrences (BYOK) is for

Rollbar Occurrences (BYOK) lets an AI assistant read your own Rollbar Occurrences data through the Rollbar Occurrences API with a key you supply (read-scope access token). Read-only: 5 tools (get_occurrence, get_occurrence_counts, get_activated_item_counts, list_team_projects, list_project_teams). 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 api.rollbar.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Rollbar Occurrences. Rollbar Occurrences 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:

"Show Rollbar occurrence 1234567890"
"How many errors did my Rollbar project get per day?"
"How many new or reactivated Rollbar items appeared per day?"
"Which Rollbar projects does team 272686 have?"
"Which Rollbar teams are assigned to project 12345?"

What it does

get_occurrence: Works with a project access token or an account access token (read scope). Get one occurrence by id: item, time, environment, level, language, framework and code version. Request, person and stack details in the payload are not returned.
get_occurrence_counts: Works with a project access token or an account access token (read scope). Get counts of occurrences per time bucket (minute, hour or day), optionally for one item, environments and a level range. The answer is the raw report from Rollbar.
get_activated_item_counts: Works with a project access token or an account access token (read scope). Get the number of new and reactivated items per day for a project. The answer is the raw report from Rollbar.
list_team_projects: Needs an account access token with read scope. List the projects a team is assigned to, as team and project id pairs.
list_project_teams: Needs an account access token with read scope. List the teams assigned to a project, as team and project id pairs.

BYOK key

You bring your own Rollbar Occurrences read-scope access token (https://docs.rollbar.com/docs/access-tokens). 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 api.rollbar.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://docs.rollbar.com/reference/get_api-1-instances (the API this connector calls, with a BYOK key)

Live from the Rollbar Occurrences API (api.rollbar.com) with a BYOK key; documentation: https://docs.rollbar.com/reference/get_api-1-instances. 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 Rollbar Occurrences. Rollbar Occurrences 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 Rollbar Occurrences account.

Built for: Worldwide. Languages: English.