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

# Connect Claude (Web)

> Use this when you want to connect your Magic Meal Kits MCP server to Claude on the web (claude.ai) as a custom connector — sign in with OAuth, choose which tools to grant, and start using MMK tools in a chat.

Your Magic Meal Kits deployment runs its own **MCP server**, so Claude on the web
([claude.ai](https://claude.ai)) can call your MMK tools directly in a chat. This guide
covers the two ways to connect it as a **custom connector**:

* **OAuth (recommended)** — add just the `/mcp` URL, sign in with your Magic Meal Kits
  account, and tick which tool groups Claude may use. No API key is placed in the URL.
* **API key (fallback)** — paste the `/mcp` URL with your API key as a query parameter.
  Use this only if OAuth isn't available for your deployment.

<Note>
  OAuth connector login requires **Magic Meal Kits version 4.21.7 or later**. If your
  deployment is older, redeploy to the latest version first (see
  [Installation → Upgrading](/installation#upgrading-redeploy)) or use the API-key method
  below. A Claude **Pro, Team, or Enterprise** plan is recommended for custom connectors.
</Note>

## 1. Get your server URL

You'll need your deployment's **Service URL**.

<Steps>
  <Step title="Open App Status">
    Go to [make.magicmealkits.com/app-status](https://make.magicmealkits.com/app-status)
    and find the **Connection & Access** section.
  </Step>

  <Step title="Copy the Service URL">
    Copy your **SERVICE URL** (e.g. `https://magic-meal-kits-xxxx-uw.a.run.app`). Your MCP
    endpoint is that URL plus `/mcp`. For the API-key method, also copy your **API KEY**.
    See [Authentication](/authentication) for details.
  </Step>
</Steps>

## 2. Connect with OAuth (recommended)

<Steps>
  <Step title="Add a custom connector in Claude">
    In Claude, go to **Settings → Connectors → Add custom connector**. Paste your MCP
    endpoint — the Service URL plus `/mcp` — and leave the URL **without** an API key:

    ```
    https://<your-deployment>/mcp
    ```

    Give it a name (e.g. *Magic Meal Kits*) and add it.
  </Step>

  <Step title="Sign in to Magic Meal Kits">
    Claude opens a Magic Meal Kits sign-in page. Log in with the **same account** you use at
    [make.magicmealkits.com](https://make.magicmealkits.com). (Your server has no login of its
    own — it hands sign-in and consent to the Magic Meal Kits app at
    `make.magicmealkits.com/mcp/authorize`.)
  </Step>

  <Step title="Choose which tools to grant">
    A consent screen shows a checklist of **tool groups**. Tick only the ones this connector
    needs — the connector is limited to exactly the groups you select (least privilege). See
    [the tool groups](#tool-groups-scopes) below.
  </Step>

  <Step title="Authorize and test">
    Click **Authorize**. Claude returns to Settings with the connector enabled. Open a **new
    chat** and confirm the Magic Meal Kits tools appear in the tool list.
  </Step>
</Steps>

<Tip>
  To change which tools a connector can use later, remove the connector in Claude and add it
  again, granting a different set of tool groups.
</Tip>

## Tool groups (scopes)

On the consent screen you grant one or more of these groups. Each group unlocks its related
tools; leaving a group unchecked hides those tools from the connector.

| Group              | What it grants                     |
| ------------------ | ---------------------------------- |
| **Plaud**          | Voice notes, folders, transcripts  |
| **Tiro**           | Meeting notes & summaries          |
| **Notion**         | Page content & transcripts         |
| **Threads**        | Posts, replies & insights          |
| **Threads data**   | Collected posts search & analytics |
| **Paymint**        | Payment invoices                   |
| **YouTube**        | Transcripts & metadata             |
| **PDF**            | PDF info & conversion              |
| **Slack**          | Markdown → Block Kit conversion    |
| **JavaScript**     | Sandboxed JS execution             |
| **JSON**           | Extract JSON from text             |
| **Date/Time**      | ISO 8601 formatting                |
| **Naver Commerce** | Smartstore orders                  |

<Note>
  Some groups (Threads, Plaud, Tiro, Paymint, Notion) also require the matching license tier
  on your deployment. Groups you aren't licensed for simply return no tools even if granted.
</Note>

## 3. Connect with an API key (fallback)

If OAuth isn't available, add the connector with your API key in the URL instead.

<Steps>
  <Step title="Add the connector URL">
    In Claude, go to **Settings → Connectors → Add custom connector**, set **Authentication**
    to **None**, and paste:

    ```
    https://<your-deployment>/mcp?api_key=YOUR_API_KEY
    ```
  </Step>

  <Step title="Optionally filter tools">
    Limit the exposed tools with the `tools` query parameter:

    ```
    https://<your-deployment>/mcp?api_key=YOUR_API_KEY&tools=pdf,youtube
    ```
  </Step>

  <Step title="Enable and test">
    Save the connector, then open a new chat to confirm the tools load.
  </Step>
</Steps>

<Warning>
  With the API-key method your key is part of the URL and can appear in server request logs.
  Prefer OAuth, and keep the key to a filtered tool set when you can.
</Warning>

## Next steps

<Card title="MCP Overview" icon="plug" href="/mcp/overview">
  Endpoints, tool filtering, and how the server MCP differs from the docs MCP.
</Card>