🧠 SmartMenu MCP Server

Created By
logeshselvama year ago
Overview

What is SmartMenu MCP Server?

SmartMenu MCP Server is a Model Context Protocol (MCP) server designed for SmartMenu, an AI-powered assistant that facilitates customer interactions with restaurant menus using natural language.

How to use SmartMenu MCP Server?

To use the SmartMenu MCP Server, clone the project from GitHub, install the necessary dependencies, and run the server to connect it with large language models (LLMs) for menu interactions.

Key features of SmartMenu MCP Server?

  • Exposes structured menus as resources to LLMs.
  • Provides tools for finding menus by name or ID, filtering dishes, and listing available menus.
  • Connects to a backend API via REST.
  • Built with the official @modelcontextprotocol/sdk.

Use cases of SmartMenu MCP Server?

  1. Assisting customers in finding dishes based on dietary preferences.
  2. Enabling natural language queries for menu items.
  3. Integrating with various LLMs for enhanced customer interaction.

FAQ from SmartMenu MCP Server?

  • What is the purpose of the SmartMenu MCP Server?

It serves as a bridge between LLMs and structured menu data, allowing for context-aware recommendations.

  • How do I get started with the server?

Clone the repository, install dependencies, and run the server as per the provided instructions.

  • What technologies are used in the SmartMenu MCP Server?

The server is built using TypeScript, Express, and connects to a backend database.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
logeshselvam
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago