Productivity

getrestro.com

An MCP server for the GetRestro restaurant management platform that enables page navigation, platform information retrieval, and free trial signup.

WebMCP1 endpoint3 known toolsFirst detected September 24, 2026Last detected September 24, 2026

ENDPOINT 1

https://getrestro.com

No auth detected

MCP server metadata

Name: WebMCP

Capabilities

imperative

Known tools 3

navigate

Navigate to a named page on the GetRestro platform. Valid pages: home, register, login, pricing, features, about, contact, survey, pos, kitchen, menu, reports.

Inferred read-only

get_platform_info

Get a structured summary of the GetRestro restaurant management platform: its purpose, key modules, pricing, and how to get started.

Inferred read-only

start_free_trial

Redirect the user to registration for temporary early access. No payment method is required and the account will not convert automatically to a paid plan.

Potential side effects

CONNECT WITH APPROVAL

Client installation

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

Codex

~/.codex/config.toml

[mcp_servers.webmcp]
url = "https://getrestro.com"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://getrestro.com"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://getrestro.com

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": {
    "webmcp": {
      "url": "https://getrestro.com"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://getrestro.com"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://getrestro.com"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.