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

# Quickstart

> Connect Claude Code to your Langmail mailbox over MCP and make your first successful tool call in about two minutes.

By the end of this page, Claude Code is connected to your Langmail mailbox and has run its first real search over your mail.

## Prerequisites

* A Langmail account — [sign up at app.langmail.me](https://app.langmail.me) with Google. Signing up creates your `you@langmail.me` mailbox.
* [Claude Code](https://code.claude.com) installed. Using a different client? See [Connect other MCP clients](/connect/other-clients).

<Steps>
  <Step title="Add the Langmail MCP server">
    Add the server as a remote MCP server over the Streamable HTTP transport:

    ```sh theme={null}
    claude mcp add --transport http langmail https://mcp.langmail.me/mcp
    ```
  </Step>

  <Step title="Authorize access">
    Start Claude Code and run `/mcp`. Select **langmail** and choose to authenticate. Your browser opens: sign in with the Google account you used for Langmail, then approve the consent screen.

    The grant is per-client: you authorize this Claude Code installation, not a shared credential. Your agent never sees your password.
  </Step>

  <Step title="Verify the connection">
    ```sh theme={null}
    claude mcp list
    ```

    ```text Output theme={null}
    langmail: https://mcp.langmail.me/mcp (HTTP) - ✓ Connected
    ```

    Inside a session you can also ask directly: *"Which Langmail tools do you have available?"* — the answer should list 10 tools, from `search_emails` to `respond_to_event`.
  </Step>

  <Step title="Make your first tool call">
    Ask Claude:

    ```text Prompt theme={null}
    Search my Langmail inbox for the 5 most recent messages.
    ```

    Claude calls `search_emails` with `{ "mailbox": "Inbox", "limit": 5 }` and gets back a compact, newest-first hit list:

    ```text Result theme={null}
    5 message(s) matched:

    1. Your invoice for June
       id: Mabc123
       from: Acme Billing <billing@acme.example>
       date: 2026-07-05T08:12:00Z
       tags: receipt

    2. Lunch on Thursday?
       id: Mabc122
       from: Jonas <jonas@example.com>
       date: 2026-07-04T16:40:00Z
       tags: direct
    ...
    ```

    Search results deliberately omit message bodies to stay light on tokens — Claude fetches a full message with `get_email` when it needs one.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Search and triage email" icon="magnifying-glass" href="/guides/search-and-triage">
    Find to-dos, filter by category and sender, read whole threads.
  </Card>

  <Card title="Calendar workflows" icon="calendar" href="/guides/calendar-workflows">
    Schedule meetings with invitations, create recurring series, RSVP.
  </Card>

  <Card title="How authorization works" icon="key" href="/connect/authorization">
    The OAuth flow behind the browser window, endpoint by endpoint.
  </Card>

  <Card title="Tool reference" icon="wrench" href="/reference/mcp/overview">
    Exact parameters and output shapes for all 10 tools.
  </Card>
</CardGroup>