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

# Ambient

> Shared team brain for meetings, Slack, and email.

Ambient keeps a searchable record of your team's meetings, Slack conversations, and email threads. Your agents can pull meeting summaries, transcripts, action items, and project context on demand.

## What the agent can do

<CardGroup cols={2}>
  <Card title="Search meeting summaries" icon="magnifying-glass">
    Query past meetings by topic, participant, or date range and get a concise summary of what was discussed.
  </Card>

  <Card title="Retrieve transcripts" icon="file-lines">
    Pull the full transcript for any recorded meeting so the agent can answer follow-up questions or extract specific details.
  </Card>

  <Card title="Surface action items" icon="list-check">
    Find open action items from any meeting and bring them into whatever workflow the agent is running.
  </Card>

  <Card title="Access project context" icon="folder-open">
    Read project-level meeting history so your agents have the background they need to work on a task without you having to re-explain it.
  </Card>
</CardGroup>

## Example agent tasks

```text theme={null}
Summarize what was discussed in last week's product review meeting.
```

```text theme={null}
Find all action items assigned to me from meetings in the past month.
```

```text theme={null}
Pull the transcript from yesterday's customer call and list the key concerns raised.
```

## What you share

Connecting grants your agents read-only access to your Ambient workspace. They can read meetings, summaries, transcripts, and projects but cannot create or modify anything. See [Permissioning](/docs/integrations/permissions).

## Connecting

<Tabs>
  <Tab title="MCP server">
    Connect Ambient over MCP for direct access to meeting summaries, transcripts, projects, and insights. This is the recommended path once your Ambient account has API access enabled.

    <Steps>
      <Step title="Enable API access">
        Ambient API access is not on by default. Open Account Settings in your Ambient workspace and look for the Ambient API section. If it is not there, email [support@ambient.us](mailto:support@ambient.us) to request access.
      </Step>

      <Step title="Add the connection">
        From the agent's tools, add Ambient. A connect card appears.
      </Step>

      <Step title="Authorize">
        Approve Ambient when prompted. The platform handles the OAuth handshake.
      </Step>

      <Step title="The agent gets to work">
        Your agents can now search meetings, retrieve transcripts, and pull project context from your Ambient workspace.
      </Step>
    </Steps>
  </Tab>

  <Tab title="API key">
    Connect Ambient REST with a Bearer API key from Account Settings. Use this if your Ambient account does not yet have MCP OAuth available.

    <Steps>
      <Step title="Enable API access">
        Ambient API access is not on by default. Open Account Settings in your Ambient workspace and look for the Ambient API section. If it is not there, email [support@ambient.us](mailto:support@ambient.us) to request access.
      </Step>

      <Step title="Create an API key">
        In Account Settings, open the Ambient API section and create a new API key. Copy it right away; Ambient only shows it once.
      </Step>

      <Step title="Add the Ambient connection">
        From the agent's connections, choose Ambient. Paste your API key when prompted.
      </Step>

      <Step title="The agent gets to work">
        Your agents can now search meetings, retrieve transcripts, and pull project context from your Ambient workspace.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Learn more

<CardGroup cols={2}>
  <Card title="Ambient help center" icon="arrow-up-right-from-square" href="https://app.ambient.us/help">
    Documentation and guides for Ambient.
  </Card>

  <Card title="How credentials stay safe" icon="shield-halved" href="/docs/integrations/permissions">
    The proxy model that keeps tokens out of the agent's reach.
  </Card>
</CardGroup>