Skip to main content
Connect your Rollbar projects to enable CloudThinker agents to triage errors, rank top issues, review deployments and releases, pull session-replay context, and update items — across one or many projects. Rollbar authenticates with project access tokens. A read-scoped token lets agents query items, deployments, and versions; a write-scoped token additionally allows 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

FieldDescriptionExample
ROLLBAR_CONFIG_JSONA 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" }
  ]
}
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.

​
Agent Capabilities

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

​
Read Capabilities

CategoryWhat the agent can do
ProjectsList configured Rollbar projects and auto-scope to a single project
Error ItemsList current and active items, inspect item details and occurrence signals
Top ErrorsSurface the highest-impact errors and current production error posture
DeploymentsReview recent deployments per project
Releases & VersionsPull version context and correlate releases with error activity
Session ReplayFetch replay context for items that have a recorded replay

​
Write Capabilities

CategoryWhat the agent can do
Item UpdatesChange 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 #flag
@alex review recent deployments and correlate them with new error activity
@alex pull the session replay context for the top error if one exists
@alex mark Rollbar item 1787741271 as resolved

​
Troubleshooting

  • 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”.
  • 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.
  • 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.
  • 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 Best Practices

  • Least privilege — use read-scoped tokens for investigation; only add a write-scoped token for projects where agents should update items.
  • Approval for controls — keep item updates approval-gated.
  • Rotation — rotate project access tokens regularly and update them in CloudThinker.
  • Revoke when unused — delete the token in Rollbar if you disconnect a project.
https://mintcdn.com/cloudthinker/aLd-ttc-SCW-aFky/images/icons/datadog.svg?fit=max&auto=format&n=aLd-ttc-SCW-aFky&q=85&s=e8382167f2a1eb1e00971b5f4d703d48

Datadog Connection

Logs, metrics, and incident investigation

Approval

How approval-gated actions work