Layout

link.layoutPublished by layout.linkOfficial publisherv1.0.1Updated Oct 30, 2026

Order food for pickup by name, with AI, at the restaurants Layout orders from.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Layout is a remote MCP endpoint that lets an assistant place restaurant pickup orders by name at the restaurants Layout works with.

What you can do
  • Place food pickup orders at restaurants Layout orders from, identified by restaurant name.
  • The manifest lists no individual tools, so the exact ordering steps are not documented; the only stated capability is ordering food for pickup by name with AI.
When to use it
Useful when you want an assistant to handle a restaurant pickup order at a supported restaurant without opening the restaurant's own site or app.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the Layout endpoint. No authentication, environment variables or headers are declared in the manifest.
Before you install
Ordering food involves real purchases and spending money, and orders are placed with third-party restaurants. No authentication is declared, so check how the endpoint ties orders to your account before relying on it. Tool-level details are not published, so confirm what it can change or cancel.

Installation

In SourceWeft

  1. Open Layout in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/link.layout%2Frestaurant-food-ordering/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "layout": {
      "type": "http",
      "url": "https://mcp.layout.link/"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.1LatestOct 30, 2026
  2. v1.0.0Sep 30, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Layout integrations