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

# Introduction

> Modus is the connecting tissue between all your data — it builds a live context layer across your sources so your AI assistants know exactly where to look.

## The problem

Modern AI assistants — Claude, Cursor, ChatGPT — are only as good as the context
they can reach. Wire up two or three connectors and an assistant works fine.
Connect dozens and it breaks down: the agent doesn't know where to look, silently
**skips the source that has the answer**, or explores for minutes before it finds
anything — and every conversation lands on something different.

Critical context is scattered across hundreds of sources — SQL and semantic
models, dashboards, tickets, docs, call transcripts, emails — with no map tying
them together. The result is slow, inconsistent, and expensive answers.

## What Modus does

Modus is the **connecting tissue** between all your data. It builds a live
**context layer** across every source — structured (Snowflake, BigQuery, Looker,
dbt) and unstructured (Notion, Teams, Confluence, Drive, email) — **without moving or
copying your data**.

When someone asks a question, Modus hands the AI a **brief** — a real-time
generated Markdown document with the relevant context for that specific prompt: a
dynamically composed map of exactly which sources, tables, and documents to use to
answer the request. Your assistant then does the work through your existing connectors — but
instead of dozens of exploratory tool calls, it takes a few. Minutes become
seconds, token spend drops, and answers become consistent and accurate.

<Note>
  Modus doesn't replace your warehouse or semantic models — it **uses** them, and
  makes them part of one context layer your whole organization can query with
  confidence, instead of a pile of MCPs scattered across the company.
</Note>

## The context layer

The context layer is the heart of Modus. A few things make it different from
wiring connectors straight into an AI assistant:

<CardGroup cols={2}>
  <Card title="A map, not a copy" icon="map">
    Modus **doesn't move or copy your data**. It builds a searchable index and a
    knowledge graph of *where things live and how they connect* — across systems —
    then fetches through your existing connectors on demand.
  </Card>

  <Card title="Built automatically, kept fresh" icon="arrows-rotate">
    The context layer is constructed automatically when you connect a source, and
    **updates itself** as things change — new tables, new documents — so you're not
    stuck maintaining it by hand.
  </Card>

  <Card title="Composed on the fly" icon="wand-magic-sparkles">
    For each question, Modus composes a **brief** — only the sources, tables, and
    documents relevant to that request — instead of dumping everything at the agent.
  </Card>

  <Card title="Structured + unstructured" icon="layer-group">
    It ties your warehouse and semantic models together with docs, tickets, chats,
    and transcripts, so an answer can span both worlds.
  </Card>
</CardGroup>

## Two ways to use Modus

Modus meets you where you already work. Both modes run on the same context layer —
pick either, or mix them.

<CardGroup cols={2}>
  <Card title="Use your own agent" icon="plug-circle-bolt">
    Keep using **Claude, Cursor, ChatGPT, or any MCP client**. Connect Modus as a
    single **MCP** server and your agent reaches your entire context layer through
    one connection — no juggling dozens of separate MCPs. Modus does the mapping
    and hands your agent the right context behind the scenes.
  </Card>

  <Card title="Use Modus" icon="robot">
    Work directly inside Modus. Chat on [Home](/guides/home), tag
    [scopes](/guides/scopes) for specialist help, and run
    [workflows](/guides/workflows) — a Modus-native experience on the same context.
  </Card>
</CardGroup>

You don't have to choose: publish a [scope](/guides/scopes) and expose *it* over
MCP, so your external agent gets a focused, governed slice of context instead of
everything. And because Modus is **API-, SDK- (Python & TypeScript), MCP-, and
CLI-first**, you can automate and build on any of this however you like.

## How it fits together

Modus is organized around five pages in the left sidebar, each building on the one
before it:

<CardGroup cols={2}>
  <Card title="Integrations" icon="plug" href="/guides/connect-apps">
    Connect your data sources (Snowflake, BigQuery, Postgres…) and apps (Slack,
    Teams, Notion…). This is where your data enters Modus.
  </Card>

  <Card title="Context" icon="book-open" href="/guides/context">
    The context layer Modus builds automatically from your sources — the metrics,
    tables, relationships, and documents your AI draws on, kept fresh as things change.
  </Card>

  <Card title="Scopes" icon="users" href="/guides/scopes">
    Specialist AI configurations. Each scope gets just the slice of context, tools,
    and access it needs — a focused expert instead of one bloated agent.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/guides/workflows">
    Triggered, multi-step pipelines that put scopes to work automatically — on a
    schedule, from a conversation, or via webhook.
  </Card>
</CardGroup>

And you actually work in one place:

<Card title="Home" icon="comments" href="/guides/home">
  The chat surface where you talk to Modus, tag scopes for specialist help, and
  run workflows — or connect the same context layer to Claude or Cursor.
</Card>

## The flow

**Integrations → Context → Scopes → Home (or your assistant)**

1. **Connect** your data and apps in Integrations.
2. Modus **builds and maintains context** from them automatically.
3. **Create scopes** — specialist AIs scoped to the right context and tools (optional, but sharper).
4. **Work on Home** — or from Claude, Cursor, the API, SDK, or CLI — grounded in your data.

<Tip>
  New to Modus? Start with [Connecting apps](/guides/connect-apps) or a
  [data integration](/guides/postgresql), then head to
  [Home](/guides/home) to put your data to work.
</Tip>