Rollbar

Connect Rollbar to CloudThinker for error triage, top-error tracking, and deployment-correlated investigation

Connect your Rollbar projects to enable CloudThinker agents to triage errors, rank top issues, review deployments, pull session-replay context, and update items across one or many projects. Rollbar authenticates with project access tokens — a read-scoped token covers investigation; a write-scoped token adds approval-gated item updates.

Prerequisites

• A Rollbar account with access to the projects you want CloudThinker to see.
• A project access token for each project (read scope is enough for investigation).
• A write-scoped token only if you want agents to update item status (approval-gated).

Rollbar tokens are scoped per project. CloudThinker supports multiple projects in one connection — supply one token per project you want to include.

Setup

1. Create a project access token

   In Rollbar, open the project and create (or copy) a project access token with read scope. Add a write-scoped token if you want agents to update items. See Rollbar’s MCP Server Setup for token and configuration details.

2. Add connection in CloudThinker

   Navigate to Connections → Rollbar and enter:

   • Project config (JSON): a projects array, one entry per Rollbar project, each with its name and token.

   Click Connect. CloudThinker verifies the credentials and shows a Connected status.

Connection details

Field	Description	Example
ROLLBAR_CONFIG_JSON	A projects array mapping each Rollbar project to its access token. Each entry has a name and a token.	see below

{
  "projects": [
    { "name": "backend",  "token": "tok_abc123" },
    { "name": "frontend", "token": "tok_xyz789" }
  ]
}

The token field is token (not access_token), and projects is an array. Format matches Rollbar’s MCP multi-project configuration.

Required permissions

Read operations (project list, items, top errors, deployments, versions, replay) work with a read-scoped project access token. Item updates additionally require a write-scoped token and explicit approval in CloudThinker.

Follow least privilege: use read-scoped tokens for investigation, and only add a write-scoped token for projects where agents should update items.

Agent capabilities

Once connected, agents can investigate and act on errors across your configured projects.

Read capabilities

Category	What the agent can do
Projects	List configured Rollbar projects and auto-scope to a single project
Error items	List current and active items, inspect item details and occurrence signals
Top errors	Surface the highest-impact errors and current production error posture
Deployments	Review recent deployments per project
Releases & versions	Pull version context and correlate releases with error activity
Session replay	Fetch replay context for items that have a recorded replay

Write capabilities

Category	What the agent can do
Item updates	Change an item’s status (e.g. resolve, mute) — requires approval

Item updates require explicit user approval before execution, and you must name the project, item, and desired change.

Verify the connection

@alex list my Rollbar projects and show the current top errors

Example prompts

@alex triage current Rollbar items and rank them by impact #recommend
@alex show the top errors that appeared after the latest deployment
@alex review recent deployments and correlate them with new error activity

Troubleshooting

Auth fails or queries come back empty

The pasted project config is invalid JSON, does not include the requested project name, or maps the project to an expired token. List your configured projects first before treating a missing item or deployment as “no data”.

Agent asks which project to use

This happens when several projects are configured. Name the project in your prompt (e.g. “for my-app”) so the agent can scope the query.

No replay available for an item

Session replay context only exists for items that have a recorded replay. Items without replays will not return replay data — this is expected, not an error.

Item update is blocked

Updates are approval-gated and need a write-scoped token. Confirm the token for that project has write scope, then approve the action when prompted.

Security

• Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
• Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
• Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
• Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.

• Least-privilege tokens — use read-scoped project tokens for investigation; add write scope only when agents need to update item status.
• Rotation — rotate project access tokens regularly and update them in CloudThinker.

Related

Datadog Connection

Logs, metrics, and incident investigation

Approval

How approval-gated actions work