Skip to main content
Your Magic Meal Kits deployment runs its own MCP server, so Claude on the web (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.
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) or use the API-key method below. A Claude Pro, Team, or Enterprise plan is recommended for custom connectors.

​
1. Get your server URL

You’ll need your deployment’s Service URL.
1

Open App Status

Go to make.magicmealkits.com/app-status and find the Connection & Access section.
2

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 for details.
1

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:
Give it a name (e.g. Magic Meal Kits) and add it.
2

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. (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.)
3

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 below.
4

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.
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.

​
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.
GroupWhat it grants
PlaudVoice notes, folders, transcripts
TiroMeeting notes & summaries
NotionPage content & transcripts
ThreadsPosts, replies & insights
Threads dataCollected posts search & analytics
PaymintPayment invoices
YouTubeTranscripts & metadata
PDFPDF info & conversion
SlackMarkdown → Block Kit conversion
JavaScriptSandboxed JS execution
JSONExtract JSON from text
Date/TimeISO 8601 formatting
Naver CommerceSmartstore orders
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.

​
3. Connect with an API key (fallback)

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

Add the connector URL

In Claude, go to Settings → Connectors → Add custom connector, set Authentication to None, and paste:
2

Optionally filter tools

Limit the exposed tools with the tools query parameter:
3

Enable and test

Save the connector, then open a new chat to confirm the tools load.
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.

​
Next steps

MCP Overview

Endpoints, tool filtering, and how the server MCP differs from the docs MCP.