> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 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).

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

## Setup

<Steps>
  <Step title="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](https://docs.rollbar.com/docs/mcp-server-setup#configuration) for token and configuration details.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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 |

```json theme={null}
{
  "projects": [
    { "name": "backend",  "token": "tok_abc123" },
    { "name": "frontend", "token": "tok_xyz789" }
  ]
}
```

<Info>
  The token field is `token` (not `access_token`), and `projects` is an array. Format matches Rollbar's [MCP multi-project configuration](https://docs.rollbar.com/docs/mcp-server-setup#configuration).
</Info>

## 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](/guide/approval) in CloudThinker.

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

## 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** |

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

### Verify the connection

```text theme={null}
@alex list my Rollbar projects and show the current top errors
```

### Example prompts

```text theme={null}
@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

<Accordion title="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".
</Accordion>

<Accordion title="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.
</Accordion>

<Accordion title="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.
</Accordion>

<Accordion title="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.
</Accordion>

## 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

<CardGroup cols={2}>
  <Card title="Datadog Connection" icon="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" href="/guide/connections/datadog" width="24" height="24" data-path="images/icons/datadog.svg">
    Logs, metrics, and incident investigation
  </Card>

  <Card title="Approval" icon="shield-check" href="/guide/approval">
    How approval-gated actions work
  </Card>
</CardGroup>