List your agent

Lokand Restaurant MCP

MCP server● Hosted · onlinev1.0.4

Free restaurant websites and menus: read any public menu, or build, import and publish a site

Reviews

No review yet. Used Lokand Restaurant MCP? Be the first to help others choose.

What it does

Lokand Restaurant MCP is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.4
PriceNot in the registry
First seen10 Nov 2026
Last checked2h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 22h ago (live check)

Hosted endpoint

  • https://api.lokand.com/mcp streamable-http

In Claude Code: claude mcp add --transport http lokand-restaurant-mcp https://api.lokand.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "lokand-restaurant-mcp": {
      "url": "https://api.lokand.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 22h ago

ONLINE Lokand Restaurant MCP answered an MCP connection on 16 Nov 2026 and introduced itself as lokand 1.0.2 (MCP protocol 2025-06-18).

73 tools offered to AI assistants

  • get_started · How to use Lokand as an agent: the recipes for creating a restaurant for a customer, editing menus, and handing over ownership. Call this first if you're unsure what to do.
  • list_businesses · List the businesses the signed-in user is a member of (id, name, slug, role). Use it to pick the business_id other ops need.
  • get_business · Look up a public Lokand restaurant/business by its slug. Returns profile, hours, contact info, locale and theme metadata.
  • list_menus · List the active menus of a public Lokand restaurant by its slug.
  • get_menu · Fetch a single menu (categories + items with prices) of a public Lokand restaurant.
  • get_status · Private status of a business the caller manages: profile (including unpublished state), all menus (active and inactive), and plan. Requires the menu:read scope and membership.
  • create_full_menu · Create a COMPLETE menu (sections + items) in one call — prefer this over separate create_menu/add_category/add_item calls. With replace=true, existing menus are deactivated so this becomes the business's live menu (their data is kept, just
  • create_menu · Create an EMPTY menu on a business the caller manages (add sections with add_category, dishes with add_item). For a whole menu at once, use create_full_menu instead. Returns the new menu_id.
  • add_category · Add a category (section) to a menu. Returns the new category_id.
  • add_item · Add a dish/item to a menu (optionally inside a category). Returns the new item_id.
  • update_item · Update a menu item's fields (name, description, price, availability, category, sort order). Only provided fields change. Setting is_available=false takes a dish off the public site (86 it).
  • delete_item · Delete a menu item.
Show 61 more
  • update_menu · Rename a menu, change its description, or switch it on/off on the public site (is_active). Only provided fields change. Menu ids come from get_status.
  • delete_menu · Permanently delete a menu together with ALL of its sections and items. To take a menu off the site but keep it, use update_menu is_active=false instead.
  • rename_category · Rename a menu category (section).
  • reorder_categories · Set the order of a menu's categories (sections). List category ids top to bottom; any you leave out keep their current relative order after the listed ones.
  • delete_category · Delete a menu category (section). Its items are NOT deleted — they stay on the menu without a section; move them with update_item category_id or delete them with delete_item.
  • reorder_items · Set the order of the items in one section of a menu. List item ids top to bottom; listed items from another section are moved into this one, and the section's other items keep their relative order after the listed ones.
  • update_business · Update a business's profile: name, description, about text, opening hours, contact info, currency, default locale, menu display options, country, business details, or place (location, address, timezone, category, cuisines). Only provided fi
  • set_theme · Switch the site to a system theme with `theme_id` (lokand-base, lokand-one — get_site lists them; pages, sections and settings are kept). Legacy shape: `theme_key` (a style preset) plus an optional v1 `theme_config` patch (colors, fonts, he
  • publish_site · Publish (or unpublish) the business's public menu site at https://<slug>.lokand.co.
  • create_restaurant · Create a new Lokand restaurant on a customer's behalf — ONE call can produce a complete LIVE website when you pass `menu` (and optionally hours/theme). Returns working OAuth tokens (Bearer, for follow-up edit ops), the live site_url, and a
  • claim_status · Check whether the customer has claimed an agent-created restaurant. On the first poll after a claim with consent granted, returns fresh OAuth tokens for continued management (delivered exactly once).
  • create_checkout_link · Create a Stripe Checkout link to upgrade a business to a paid plan. Hand the returned URL to the customer — anyone who opens it can pay; the plan activates automatically after payment (3-month free trial). Pass customer_country (ISO 3166-1
  • get_billing_summary · Current plan, billing region, and subscription state of a business the caller manages.
  • import_menu · Start an AI import of a restaurant's menu from the URL of its existing website. Returns an import_id to poll with import_status; when complete, call commit_import to turn the draft into a real menu.
  • import_status · Check an AI menu import: processing, complete (draft ready to commit), or failed. `progress.found` lists what is known so far; complete responses include the draft for review.
  • commit_import · Commit a completed AI menu import as a real menu (creates the menu, categories, and items). Returns the new menu_id.
  • check_compliance · Check a business's published menu against what a country's menu rules ask for — allergen and calorie declarations, price-list notices, banned surcharges, operator identity. Returns each requirement with its official sources, plus which ones
  • apply_country_settings · Fill the business's menu display options with the values a country's rules suggest — a notice about tax-inclusive pricing, the price-effective date, ordering restrictions. These are DEFAULTS: the owner can change any of them afterwards, and
  • get_site · Read the business's website: `document` (the v3 site document — settings, home, pages, and templates[page_id] → sections → blocks, with the ids every other site op needs), `theme` (what the live theme offers: every section and block type wi
  • update_site · Low-level escape hatch: apply an RFC 7386 JSON merge patch to the whole v3 site document returned by get_site.document (objects merge, null deletes a key, arrays REPLACE). Prefer the specific site ops. The result is validated against the th
  • update_theme_settings · Merge-patch the theme's global settings (keys from get_site.theme.theme_settings, e.g. color_primary, font_heading, radius, custom_css). null resets a key to the theme/preset default.
  • apply_style_preset · Switch the site's style preset (get_site.theme.style_presets, e.g. terra, porto, noir, marche, slate). Colors and fonts the owner changed are reset unless keep_overrides=true.
  • update_theme · Legacy look op: switch `preset`, patch v2-style `tokens` (colors, fonts, radius, hero layout, …) or set custom CSS. Prefer update_theme_settings / apply_style_preset.
  • apply_template · Rebuild the site's pages and sections from a segment template (cafe, ghost-kitchen, fine-dining, chain, bar, bakery — see get_site.templates). Replaces the page structure; hero copy and custom CSS carry over. keep_theme=true keeps the curre
  • apply_site_preset · Alias of apply_template (`preset` = template id).
  • set_page · Change one page: enable/disable it, show/hide it in the navigation, rename its title, change its path, make it the home page, or move it in the navigation. Only provided fields change. Page ids come from get_site.document.pages (built-ins:
  • add_page · Add a new page with a text section (add more with add_section). Returns the updated document, where the new page's id appears.
  • remove_page · Remove a custom page and its sections. The home page can't be removed — make another page home first (set_page make_home).
  • set_nav_links · Replace the navigation with custom links ([] restores the automatic page list).
  • add_section · Add a section of a given `type` (keys of get_site.theme.sections) to a page, optionally from one of its presets, with a settings patch and a 0-based position (default: the end). Sections hold blocks; add them with add_block.
  • update_section · Change one section: merge-patch its settings (null removes a key; settings: null resets them all) and/or hide/show it. Ids come from get_site.document.templates[page_id].
  • remove_section · Remove a section from a page. To keep it for later, hide it with update_section hidden=true instead.
  • move_section · Move a section to a 0-based position within its page.
  • add_block · Add a block (a repeatable piece inside a section: a link, a photo, a testimonial, …) of a `type` the section accepts (get_site.theme.sections[type].blocks). Nest it in another block with parent_block_id.
  • update_block · Merge-patch one block's settings (null removes a key) and/or hide/show it.
  • move_block · Move a block to a 0-based position among its siblings.
  • remove_block · Remove a block (and any blocks nested in it).
  • set_featured_items · Choose the dishes shown in the home page's "featured" section, in order (menu item ids, max 12; [] lets the site pick automatically). Adds the section after the hero if the page has none.
  • set_system_theme · Switch to another system theme (get_site lists `system_themes`). Pages, sections and settings are kept.
  • make_menu_only · Turn the site into a single menu page (the menu becomes the home page, every other page is disabled). Use when the owner wants "just the menu". Revertible with revert_last_site_change.
  • set_brand_link · Chains only: link this location to its brand's shared site (linked=true) so it shows the brand template's pages and theme, or unlink it (linked=false) to use its own site again. Hours, address, menus and ordering always stay this location's
  • publish_brand_template · Chains only: make this location's published site the brand template that every linked location of its organization shows (see set_brand_link). Requires brand owner/admin and the franchise plan.
  • revert_last_site_change · Undo the most recent site change made through the site ops or set_theme (up to the last 10, kept for 30 days). Call repeatedly to step further back. 404 when there is nothing to undo.
  • update_loyalty_card · Set up or change the business's loyalty stamp card: how many stamps earn the reward, the reward text, whether the card is live, and its look. Only provided fields change; the first call must include stamps_required and reward_text. Requires
  • theme_list · List the business's custom themes (id, name, role live|unpublished|development, version, upload status) and the system themes. Custom theme code is a Pro feature.
  • theme_get · One theme's details and upload status: ready (the version is stored and can be published), processing (poll again in a second or two) or failed (with the error).
  • theme_pull · Download a theme's files ({path: text}). theme_id "lokand-base" or "lokand-one" returns a system theme to start from. Custom themes return their latest stored version. A whole theme is large: pass search to find the lines you need to change
  • theme_upload · Upload a complete custom theme (Pro plan) as a new commit in its Git repo. Files are validated and compiled at once — a 422 lists every problem as `path: message` lines — then compiled in the background: poll theme_get until status is ready
  • theme_write_files · Change some files of a custom theme (Pro plan) as one new commit: files maps path → whole new text (null deletes), edits are find/replace changes. Read the current files with theme_pull first. Same validation and background compile as theme
  • theme_publish · Make a custom theme the live site's code (Pro plan). The previous live theme becomes unpublished and cached pages refresh. `warnings` lists parts of the current site document the new theme doesn't define (fix them with the site ops).
  • theme_unpublish · Stop using custom theme code: the site goes back to its system theme. The custom theme is kept as unpublished.
  • theme_delete · Delete a custom theme and all its stored versions. The live theme can't be deleted — unpublish it first.
  • get_storefront_context · The exact data a theme renders with (the StorefrontData Liquid objects are built from): the business (localized, brand site applied), every active menu with items, primary menu id, loyalty/ordering flags, the stamp-card program and its reso
  • theme_history · The commit history of a custom theme's code, newest first: hash, message, author, time. The `commit` on theme_get is the one the site renders.
  • theme_rollback · Restore a custom theme's code to an earlier commit (Pro plan). It is saved as a new commit, so the rollback itself can be undone; on the live theme it goes live once compiled. Without commit, restores the version before the latest change.
  • theme_git_access · Git access to a custom theme's code: the HTTPS remote and a repo-scoped token (read, or write on the Pro plan). Pushes to main compile automatically and, for the live theme, publish once compiled; theme_get shows a push that failed to compi
  • theme_sync · Compile the latest commit on a custom theme's main branch now (Pro plan). Pushes compile on their own; call this to apply a push immediately or to retry. Validates like an upload and, for the live theme, publishes once compiled. Poll theme_
  • list_assets · List every image the business owns: its media library (uploads, photos copied from its old website at import, photos the owner attached in chat), its logo and every menu item photo. Each entry has its url, kind, source, where it is used, an
  • use_asset · Put one of the business's own images (a url from list_assets) to use: as the logo (target "logo") or as a menu item's photo (target "item" with item_id). For a site section or block image, pass the same url to update_section / update_block
  • suggest_styles · Recommend looks for the business's website from Lokand's style library (14 hand-made looks, from a Michelin-style 'gastronomique' to a street 'bufe'), read from its menu, prices, logo and photos. Returns the three best fits, how bold to go
  • get_style · Compile one look from the style library into the exact settings to send in ONE update_theme_settings call (palette, fonts, shape, spacing and a signature custom_css on the stable [data-lk] hooks), plus the menu section style to set, the pho

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Version1.0.4DECLAREDSRC-001 Official MCP Registry2h ago
Hosted endpointhttps://api.lokand.com/mcpDECLAREDSRC-001 Official MCP Registry2h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry2h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry2h ago
Websitehttps://lokand.com/ai/DECLAREDSRC-001 Official MCP Registry2h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry2h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry2h ago

Change history

  • VERSION17 Nov 2026
    1.0.3 → 1.0.4
  • VERSION17 Nov 2026
    1.0.2 → 1.0.3
  • VERSION10 Nov 2026
    1.0.0 → 1.0.2
  • NEW10 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Lokand Restaurant MCP? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Lokand Restaurant MCPLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Lokand Restaurant MCP?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/lokand-restaurant-mcp?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/lokand-restaurant-mcp/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Lokand Restaurant MCP

How do I connect Lokand Restaurant MCP?

Use the hosted endpoint https://api.lokand.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Lokand Restaurant MCP offer?

When Electra Index connected on 16 Nov 2026, it listed 73 tools: get_started, list_businesses, get_business, list_menus, get_menu, get_status, create_full_menu, create_menu and more. The full list is in "Live check" above.

Is Lokand Restaurant MCP online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 22h ago.