INDIVIDUAL MCP TOOL

learn_platform

Call this FIRST in any conversation about building on this platform.

menubarcode.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://menubarcode.com/mcp/dev

No auth detected

Connect to this endpoint to inspect the live schema for learn_platform and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.menubarcode-dev-mcp]
url = "https://menubarcode.com/mcp/dev"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "menubarcode-dev-mcp": {
      "type": "http",
      "url": "https://menubarcode.com/mcp/dev"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: menubarcode-dev-mcp
Remote MCP URL: https://menubarcode.com/mcp/dev

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "menubarcode-dev-mcp": {
      "url": "https://menubarcode.com/mcp/dev"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "menubarcode-dev-mcp": {
      "type": "http",
      "url": "https://menubarcode.com/mcp/dev"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "menubarcode-dev-mcp",
  "transport": "streamable-http",
  "url": "https://menubarcode.com/mcp/dev"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

get_liquid_reference — The authoritative whitelist of Liquid the theme engine supports, generated at request time by reflection over the engine's own classes — never stale.
get_section_schema — The {% schema %} format for theme sections: JSON shape, every supported setting type with its exact validation rule (unknown types fall back to text), blocks, templates/index.json wiring, and a worked example from the starter theme.
search_docs — Keyword search across ALL public docs — developer (theme format, APIs, webhooks, validation, editor setup) AND the platform help pillars: users (restaurant-owner guides), integrations, resellers, shoppers.
fetch_full_doc — Fetch one complete developer doc by its corpus path (as returned by search_docs, e.g.
validate_theme — Server-side validation of theme files using the SAME rules the marketplace applies at submission: strict whitelist Liquid parse, unknown filters/tags, missing snippets, external URLs, schema shape, dangerous markup, layout/extension rules.
list_webhook_events — The authoritative list of outbound webhook event names an integration can subscribe to, read from the platform's own registry (never stale).
submit_feedback — Report a documentation problem you hit — a missing topic, a wrong or outdated statement, or a search that returned nothing useful.