Assistant Tools

Let the in-app AI assistant reach your other tools through MCP connectors

MCP connectorsOAuthPer-workspace

Overview

What are Assistant Tools?

RoleDream's built-in AI assistant already has access to your workspace. Assistant Tools extend its reach: add a connector and the assistant can also call an external tool over the Model Context Protocol (MCP) — pulling issues from Linear, pages from Notion, tickets from Intercom, and more — right inside the chat.

Manage connectors from Assistant Tools under Integrations. Each connector is enabled or disabled individually; only enabled connectors are offered to the assistant.

Availability

The AI assistant and its connectors are a gated feature and may not be enabled for every workspace. If you don't see the assistant or the Assistant Tools page, it isn't turned on for your company yet.

Two ways to connect

Connector types

Manual (static credentials)

Point the assistant at any MCP server URL and choose how it authenticates:

None — no credentials
Bearer token
API key header
Custom headers

The secret is stored in your browser and sent with your chat requests. It is private to your account in this workspace — not shared with teammates.

OAuth

Connect a branded integration by authorizing it with the provider. No token or secret is kept in your browser — the connection is held by the RoleDream backend for your workspace.

Pick a curated provider or set one up manually, then click Connect with OAuth. See the flow below.

Important distinction

Where your credentials live

The two connector types custody credentials differently. The connectors page shows an honesty banner for each so you always know where a secret is held.

Manual connectors — browser-held

Secret stored in your browser (this device)
Sent with each chat request
Private to your account in this workspace
Not shared with teammates

OAuth connections — backend-held

You authorize access with the provider
The token is held by the RoleDream backend for this workspace
The browser never holds the token
Disconnecting revokes access with the provider

How it works

Connecting with OAuth

Choose an integration Pick from the curated grid — Linear, Notion, Atlassian, GitHub, Intercom, HubSpot, Dovetail, PostHog, Slack, Replit, Lovable, Miro, Figma — or choose Custom / Advanced to enter your own MCP server URL.

Provide a client, if required Most providers self-register automatically. A few (Slack, GitHub, HubSpot, Dovetail) need a one-time OAuth client ID and secret entered in the modal. These are sent once to start the connection and are never stored in your browser.

Authorize with the provider Click Connect with OAuth. Your browser is redirected to the provider to approve access. RoleDream's backend completes the token exchange, and you return to the connectors page connected.

Managing

Managing OAuth connections

Each OAuth connection shows its current status and the actions available to it.

Status

Pending, Connected, Expired, Error, or Revoked.

Reconnect

Available when a connection is expired, errored, or revoked — re-runs the authorization to restore access.

Disconnect

Removes the connection and revokes access with the provider. The assistant can no longer use it.

Enabled toggle

Finish connecting before enabling. Only enabled connectors are sent to the assistant.

Your credentials, your account

Manual connector secrets are stored in your browser and sent with your chat requests — private to your account in this workspace, not shared with teammates. OAuth connections are authorized with the provider and held by the RoleDream backend for this workspace; no token is stored in your browser.

Connectors are not a shared vault and are not company-wide. Disconnecting an OAuth integration revokes its access with the provider.