Overview

The Magic Meal Kits MCP Server implements the Model Context Protocol (MCP) to expose version information from a Magic Meal Kits API as a tool that AI assistants can call. Instead of hard-coding backend details into an assistant, this MCP server provides a small, secure bridge so LLM clients can programmatically ask “what version is the backend running?” and get a structured answer.

This is useful for debugging, monitoring, and context-aware assistant behavior. For example, an assistant can detect when the API is running an older release and adapt responses or instruct a user to update. The server is lightweight, requires only an API key to authenticate to the Magic Meal Kits backend, and is designed to be run locally or as part of an assistant integration (e.g., Claude Desktop).

GitHub: https://github.com/pureugong/mmk-mcp

Features

Exposes a single MCP tool to retrieve Magic Meal Kits server version details
Authenticates securely using an API key (environment variable)
Returns structured JSON responses suitable for LLM tool integrations
Easy to run locally for development or to integrate with desktop MCP clients
Compatible with MCP clients such as Claude Desktop and the MCP Inspector

Prerequisites

Node.js (recommended current LTS)
Magic Meal Kits API key
Optional: MCP client (e.g., Claude Desktop) for using the tool from an assistant

Installation / Configuration

Install via Smithery (recommended for Claude Desktop integration):

npx -y @smithery/cli install @pureugong/mmk-mcp --client claude

Optional global install via npm:

npm install -g mmk-mcp

Development clone and run:

git clone https://github.com/pureugong/mmk-mcp
cd mmk-mcp
cp .env.example .env
# Set MMK_API_KEY and MMK_API_BASE_URL in .env
npm install
npm run build
npm start

Environment variables

MMK_API_KEY — your Magic Meal Kits API key
MMK_API_BASE_URL — base URL for the Magic Meal Kits API (example: https://magic-meal-kits.example.app)

Claude Desktop configuration example

Add to the “mcpServers” section of claude_desktop_config.json:

{
  "mcpServers": {
    "magic-meal-kits": {
      "command": "npx",
      "args": ["-y", "mmk-mcp"],
      "env": {
        "MMK_API_KEY": "<your-api-key>",
        "MMK_API_BASE_URL": "<your-api-base-url>"
      }
    }
  }
}

Current published version: 1.0.17

Available Tools

Tool name	Description	Parameters
magic_meal_kits_server_version	Returns Magic Meal Kits API server version	None

Example tool call (conceptual)

Request: “What version is the Magic Meal Kits server running?”

MCP response (JSON example):

{
  "name": "magic-meal-kits",
  "tool": "magic_meal_kits_server_version",
  "result": {
    "version": "2024.03.12",
    "commit": "a1b2c3d",
    "buildDate": "2024-03-12T10:24:00Z",
    "status": "ok"
  }
}

Use Cases

Assistant diagnostics: An assistant can check the backend version before explaining API behavior or troubleshooting user-reported issues.
Deployment verification: Part of a deployment pipeline or post-deploy chatops flow can verify the running version matches the expected release.
Conditional messaging: If the server reports an older version or incompatible build, the assistant can modify its guidance (e.g., flag missing features).
Monitoring integration: Use the MCP server from an orchestration script to periodically confirm version and health as part of a lightweight monitoring check.

Concrete example

A user asks the assistant why a particular endpoint behaves differently. The assistant calls magic_meal_kits_server_version, sees the API is on an older release, and returns: “Your backend is running v2023.11.2; the endpoint behavior you expect was introduced in v2024.01.0.”

Debugging & Troubleshooting

Run the server with console output for debugging:

# debug script provided by the project
npm run debug

# or if installed globally
mmk-mcp

Use the MCP Inspector to connect and interactively test tools:

npm install -g @modelcontextprotocol/inspector
npx @modelcontextprotocol/inspector stdio -c "node" -a "build/src/index.js"
# or
mcp-inspector stdio -c "node" -a "build/src/index.js"

Common issue: “Server does not support tools (required for tools/call)”

Ensure you have mmk-mcp version 1.0.11 or later. Update with:

npm install -g mmk-mcp@latest

Security note: Treat MMK_API_KEY as a secret. Do not commit it to source control, and prefer runtime environment injection or a secure secrets manager when deploying.

Additional Resources

Repository: https://github.com/pureugong/mmk-mcp
Smithery server listing: https://smithery.ai/server/@pureugong/mmk-mcp
MCP Inspector: https://www.npmjs.com/package/@modelcontextprotocol/inspector

This MCP server is intentionally minimal: it focuses on providing reliable version metadata so AI assistants can adapt their behavior to the current backend state.

Magic Meal Kits MCP Server Version Endpoint