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

# Connecting Tools and Integrations

> Configure credentials for expert tools and fix common setup issues.

Experts can only use tools they are configured for. This page explains what users see in **Configure**, what each auth type means, and how to fix common failures.

## When You Need This

You need tool configuration when:

* The expert shows a **Configure** or **Reconfigure** button.
* A warning badge appears on the expert page.
* The expert says it cannot access a connected service.

## Configuration Flow

1. Open the expert page.
2. Click **Configure**.
3. Complete each service in the left sidebar until all show checkmarks.
4. Save and test in chat.

## Credential Types

| Type                        | What You Enter                         | Best For                         | Common Pitfall                               |
| --------------------------- | -------------------------------------- | -------------------------------- | -------------------------------------------- |
| **Connect Account (OAuth)** | Sign in + approve permissions          | Google, Notion, other OAuth apps | Popup blocked or wrong account selected      |
| **API Key**                 | Key from provider dashboard            | Service APIs with static keys    | Expired/revoked key                          |
| **Bearer Token**            | Token string                           | Services issuing scoped tokens   | Token TTL expired                            |
| **Basic Auth**              | Username + password                    | Legacy/internal services         | Credentials rotated but not updated          |
| **Environment Variables**   | Field values defined by expert creator | Custom tool settings             | Missing required field or wrong value format |

## Quick Decision Guide

* If you see **Connect Account**, use that first (preferred for end users).
* If provider gives you a key string, use **API Key**.
* If provider gives short-lived auth tokens, use **Bearer Token**.
* Use **Environment Variables** exactly as labeled by the expert creator.

## MCP Servers (for Expert Builders)

If you are creating/editing an expert and adding custom MCP servers:

* Set **Name**, **URL**, and **Transport**.
* Click **Verify** before saving.
* Use MCP only when built-in hives are insufficient.

<Tip>
  For first versions, start with built-in hives only. Add MCP later if a real use case requires it.
</Tip>

## Security and Isolation

* Credentials are encrypted.
* Each user's credentials are isolated.
* If two users hire the same expert, each user configures their own credentials.

## Reconfiguring Later

Reconfigure whenever:

* OAuth access was revoked.
* API keys/tokens rotated.
* New tools were added to the expert.

## Troubleshooting

| Problem                                 | What to Check             | Fix                                          |
| --------------------------------------- | ------------------------- | -------------------------------------------- |
| OAuth popup does not open               | Browser popup settings    | Allow popups for Braintrust domain and retry |
| Connected but tool still fails          | Correct account/tenant    | Reconnect with the intended account          |
| API key rejected                        | Key scope and expiry      | Generate a new key with required scope       |
| Missing env field context               | Field labels from creator | Ask expert owner for expected value format   |
| Configure completed but warnings remain | Unsaved step in wizard    | Open each service and confirm saved state    |

## Next Steps

<CardGroup cols={2}>
  <Card title="Hiring Your First Expert" icon="user-plus" href="/experts/hiring-your-first-agent">
    End-to-end hiring flow with screenshots.
  </Card>

  <Card title="Expert Fields Reference" icon="list-check" href="/experts/expert-fields-reference">
    Field-by-field guidance for expert builders.
  </Card>

  <Card title="Triggers" icon="bolt" href="/automation/triggers">
    Run experts on a schedule or from calendar events.
  </Card>
</CardGroup>