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

# Integrations

> Over 3,000 built-in apps, plus any HTTP API or MCP server.

Connections are how Quaso reaches your apps. There are over 3,000 built-in integrations, plus the ability to call any HTTP API or MCP server. If a service has no API at all, Quaso can still [use it through the browser](/docs/features/browsing).

## How connections work

1. **You authorize access.** Say "Connect my Gmail" and Quaso opens a secure login flow; you sign in directly with the service.
2. **You choose what to grant.** Each connection unlocks specific tools (send email, create ticket). Quaso asks before activating anything new.
3. **The tools become available.** From then on Quaso can use them to complete work for you.

## Popular integrations

<CardGroup cols={4}>
  <Card title="Slack" icon="slack" href="/docs/integrations/slack" />

  <Card title="Gmail" icon="mail" href="/docs/integrations/gmail" />

  <Card title="Google Calendar" icon="calendar" href="/docs/integrations/google-calendar" />

  <Card title="Google Drive" icon="hard-drive" href="/docs/integrations/google-drive" />

  <Card title="Notion" icon="notebook-text" href="/docs/integrations/notion" />

  <Card title="GitHub" icon="github" href="/docs/integrations/github" />

  <Card title="HubSpot" icon="chart-no-axes-combined" href="/docs/integrations/hubspot" />

  <Card title="Custom APIs & MCP" icon="plug" href="/docs/integrations/custom-apis-mcp" />
</CardGroup>

Discord, Microsoft Teams, Google Sheets, Airtable, Linear, Jira, Asana, Stripe, Salesforce, and thousands more are in the catalog too.

## Custom APIs and MCP servers

Quaso connects to any HTTP API or MCP server. Register a custom Streamable-HTTP MCP server under **Settings → MCP servers**: paste its URL, add a bearer token or header if it needs one, and hit Test connection. Tokens are encrypted at rest and never shown to the model. See [Custom APIs & MCP](/docs/integrations/custom-apis-mcp).

## Security

* Credentials are encrypted at rest; Quaso never sees your password.
* OAuth is used wherever the service supports it.
* You can revoke access anytime from **Settings → Connections**.
* After approving an app, you control exactly which tools Quaso can use.