Skip to main content
Connect Rollbar to let CloudThinker agents rank your top errors, tie new errors to recent deployments and versions, pull session replay context, and change an item’s status through your Approvals. You paste one JSON config that maps each Rollbar project to its project access token, so one connection can cover many projects.

​
Prerequisites

  • A Rollbar account with access to each project you want agents to read.
  • A project access token for each of those projects. Rollbar tokens are per project, so one token can’t cover two projects.

​
Setup

1

Create a project access token

In Rollbar, open the project and go to Settings → Project Access Tokens. Click Create new access token, check read, and add write only if you want agents to change item status. Leave post_server_item and post_client_item unchecked: they send errors into Rollbar, which CloudThinker never does. Repeat for each project.
2

Write the project config

Build a JSON object with a projects array, one entry per project. Each entry has a name and a token. The name is your own label for prompts, so it doesn’t have to match the Rollbar project name. Short names like backend are easiest to type.
3

Add the connection

In the sidebar, click More → Workspace settings → Connections, then on the Builtin Connections tab select Rollbar, paste the JSON into ROLLBAR_CONFIG_JSON, and click Connect.Success state: the connection shows Connected. Connect doesn’t call Rollbar with each token, so a bad token only shows up on the first request. Run the prompt in Verify the connection in a new chat right away.

​
Connection details

The format matches Rollbar’s MCP server multi-project configuration.

​
Required permissions

Start with read-only tokens. Add the write scope only on the projects where you want agents to resolve or mute items.

​
Agent capabilities

Agents never change an item while triaging, reviewing deploys, or reading replays. An update runs only when you ask for it in the conversation, and it goes through your Approvals. Every change an agent makes goes through your workspace’s Approvals first. On the default Auto · Rules + AI · Ask me mode, AI judgment can let a safe change run without asking — and an Allow Rule can too, once CloudThinker turns on Rule enforcement for your workspace. Choose Manual to approve every change yourself.

​
Verify the connection

Ask CloudThinker in a new chat:
Expect every project name from your config, each with its highest-impact items, their level, and occurrence counts. A missing project means it isn’t in the JSON you pasted.

​
Example prompts

With several projects configured, name the project in your prompt. Otherwise the agent asks you which one to use. For item numbers, use the # number Rollbar shows on the item.

​
Troubleshooting

The pasted config is invalid JSON, doesn’t include the project you named, or holds a token that was revoked, disabled, or rate-limited in Rollbar. Ask the agent to list your configured projects, then edit the connection and fix the JSON or token.
More than one project is configured and your prompt didn’t name one. Add the project name from your config, for example “in backend”.
Replay context exists only for items with a recorded session replay. Items without one return no replay data. That’s expected, not an error.
The token for that project lacks the write scope, or you declined the approval. Add write scope to the token in Rollbar, update the connection, and ask again.

​
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.
  • Temporary config file: tokens are stored encrypted. When an agent uses Rollbar, its Rollbar process reads them from a temporary file only that process can read, and the file is deleted when the process stops.
  • Rotation and new projects: the saved JSON isn’t shown when you edit the connection. Paste the full JSON again, with every project, whenever you rotate a token or add a project.

Sentry

Issues, events, and traces through OAuth.

Approvals

How CloudThinker asks before an item update runs.