Food Near Me — MCP Server

Model Context Protocol server for AI-native restaurant discovery — three-tier search (verified → menu_indexed → discovered), Menu Protocol menus, and structured menu validation. Plug into Claude Desktop, Cursor, ChatGPT, or any MCP host in about 30 seconds.

Production endpoint: https://foodnear.me/mcp · 8 tools · 4 resources · 3 prompts · No API key (beta)

---

Quick start {#quick-start}

1. Add this to your MCP host config

Cursor — ~/.cursor/mcp.json (macOS/Linux) or %USERPROFILE%\.cursor\mcp.json (Windows)

Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows)

{
  "mcpServers": {
    "foodnear-me": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://foodnear.me/mcp"]
    }
  }
}

2. Restart your MCP host

3. Try a prompt

“Find vegan Thai restaurants near Brooklyn Bridge and show me a menu for the top result.”

Your agent should call search_restaurants → get_menu (or get_restaurant first).

---

What you get

Tools (8)

Tool	Description
search_restaurants	Three-tier geo search by lat/lng — verified → menu_indexed → discovered; check menu_available before get_menu
get_restaurant	Restaurant profile with Schema.org JSON-LD + Menu Protocol extensions
get_menu	Full Menu Protocol v1.0 menu (dietary flags, allergens, signatures)
get_ado_score_breakdown	ADO score factors and improvement recommendations
validate_menu_protocol	Validate a Menu Protocol JSON payload before publish
explore_area_for_diet	Composite: bucketed neighborhood overview (verified / menu_indexed / discovered); optional dietary filter narrows the verified tier only
compare_restaurants_for_diet	Composite: compare 2–5 known restaurants by dietary-eligible menu items and trust tier ranking
find_restaurants_along_route	Composite: route-adjacent restaurant discovery between origin/destination with optional dietary ranking

Resources (4)

URI	Content
foodnearme://spec/menu-protocol	Menu Protocol v1.0 specification
foodnearme://spec/openapi	OpenAPI 3.1 spec pointer
foodnearme://agent/skill	Agent skill summary
foodnearme://examples/search-flow	Example search → menu flow

Prompts (3)

Prompt	Args	Guides agent to
find_dinner_near_me	location (required), cuisine?, dietary?	search_restaurants → get_menu
dietary_constrained_menu	restaurant_id, restrictions	get_menu with explicit MP flags/allergens
validate_my_menu	strict? (true for strict mode)	validate_menu_protocol

---

Configuration

Setting	Value
MCP URL	https://foodnear.me/mcp
Transport	HTTP JSON-RPC (POST); discovery via GET /mcp
Auth	None during beta (rate limits apply)
Registry	me.foodnear/foodnear-me (official MCP Registry)

Preview / local: Replace the URL with http://localhost:3000/mcp when running npm run dev in apps/web.

Operational tool filter: set FNM_MCP_ENABLED_TOOLS=search_restaurants,get_menu to expose only a comma-separated subset in tools/list and GET /mcp. Leave unset or * to expose all tools. This is for temporary degradation/context control, not privacy or auth.

---

Architecture

┌─────────────────────┐     POST /mcp (JSON-RPC)     ┌─────────────────────────┐
│  MCP host           │ ────────────────────────────▶│  apps/web/app/mcp       │
│  (Cursor / Cla

... [View full README on GitHub](https://github.com/food-near-me/platform#readme)