MCP Overview

Your Magic Meal Kits deployment exposes an MCP (Model Context Protocol) server, so an LLM client can call MMK tools directly. PDF and YouTube extraction, JavaScript execution, Markdown → Slack conversion, and date parsing come standard; depending on your plan you also get Threads, Plaud, Tiro, Paymint, and Notion tools.

Two different MCP servers are in play, don’t confuse them:

This page: your server’s MCP at https://<your-deployment>/mcp, which runs actions against your MMK deployment.
Docs as MCP: the documentation MCP at https://docs.magicmealkits.com/mcp, which lets an LLM read this reference.

Copy the settings from the app

You don’t build the connection values by hand; copy them from the app. At make.magicmealkits.com, open MCP connection (MCP 연결) under Connections and MCP (연결과 MCP) in the left menu. The screen opens on Magic Meal Kits server 4.13.8 or later.

The Connections (연결 관리) screen in the same group also has an MCP connection section at the top. Pick where you use it (Claude Code, Claude.ai, Notion, or other tools) to get the text to paste; the key goes in only when you copy. On the dashboard’s first screen, Connect MCP (MCP 연결하기) in step 5 of the Get started (시작하기) checklist brings you to this section. To pick a tool scope too, click More settings, like tool scope (도구 범위 고르기 등 자세한 설정) under the section to go to the MCP connection screen.

Tool scope (도구 범위): pick All tools (전체 도구), Deferred loading (지연 로딩), or Custom (직접 선택). Your choice goes straight into the tools query of the URL below.
Deferred loading (?tools=deferred) loads tool descriptions only when needed, which cuts the context the AI uses by a lot. Turn it on when responses are slow because of many tools, or when the AI keeps picking the wrong tool.
Each tab (Claude Code (CLI), Claude.ai (Web), Notion) shows the command or values to paste, already filled in with your server URL and API key.

Tool scope and client tabs on the MCP connection screen

Tool scope and client tabs on the MCP connection screen (Zoomed in) — Zoomed in

Connecting

Client	How
Claude.ai (Web)	Settings → Connectors → Add custom connector → `https://<your-deployment>/mcp`, sign in with OAuth & pick tool groups. See Connect Claude (Web).
Claude Code	`claude mcp add` or `.mcp.json`, header `X-API-KEY: YOUR_API_KEY`
Cursor / other	Add the same `/mcp` URL with an API-key header
Notion agent	Settings → Connections → Add custom MCP, auth type API Key, header `X-API-KEY`. See Connect Notion.

For Claude Code, paste the command from the app’s Claude Code (CLI) tab. It looks like this:

claude mcp add magic-meal-kits \
  --transport http \
  "https://<your-deployment>/mcp" \
  --header "X-API-KEY: YOUR_API_KEY"

{
  "mcpServers": {
    "magic-meal-kits": {
      "type": "http",
      "url": "https://<your-deployment>/mcp",
      "headers": { "X-API-KEY": "YOUR_API_KEY" }
    }
  }
}

Connecting Claude on the web? Connect Claude (Web) is a full step-by-step walkthrough of the OAuth connector flow and how to choose which tools to grant.

Endpoints

Endpoint	Auth	Description
`POST /mcp`	Required	Main JSON-RPC endpoint
`GET /mcp`	Required	Server info / SSE streaming
`GET /mcp/health`	None	Health check
`GET /mcp/categories`	None	List tool categories

Tool filtering

Limit exposed tools with the tools query parameter:

/mcp?tools=pdf,youtube        # by category
/mcp?tools=pdf_info,youtube_transcript   # by specific tool
/mcp                          # all tools (default)

Looking for ready-made automations? The MMK Skills give your agent slash commands (/mmk-notion, /mmk-paymint-send, …) for the most common operations. Install them once and skip writing glue code.

MCP Server

Copy the settings from the app

Connecting

Endpoints

Tool filtering

Examples

Connect Notion

Tiro meeting notes MCP