Index LaneLive integration hub
OverviewProvidersDocs
Loading
Skip to Content
Index Lane DocsCLI + MCP
AppProvidersQuickstart
Search docs
  • Index
  • Demo
    • Introduction
    • Quickstart
      • Overview
      • Overview
      • Commands
      • Search
      • Access Rules
      • Overview
      • Auth Model
      • Tools
  • Providers
  • Index
  • Demo
    • Introduction
    • Quickstart
      • Overview
      • Overview
      • Commands
      • Search
      • Access Rules
      • Overview
      • Auth Model
      • Tools
  • Providers

On this page

  • Flow
  • Why this matters
Question about this page?Edit this page
DocsMCPAuth Model

Auth Model

The local MCP server does not authenticate directly to Google, Notion, or Calendar.

Instead it authenticates to Index Lane.

Flow

  1. The user signs in on the Index Lane web app.
  2. The user connects providers there.
  3. The user creates a personal Index Lane API key.
  4. The user runs index-lane login.
  5. The user runs index-lane mcp serve.
  6. The local MCP server calls the Index Lane backend with that saved API key.

Why this matters

This means the MCP server inherits:

  • the same connected providers
  • the same saved provider access rules
  • the same web-managed account identity

The MCP layer does not become a separate auth system.

OverviewTools
Index Lane v1 docs