Deliverect

com.deliverectPublished by deliverect.comOfficial publisherv1.0.0Updated Nov 5, 2026

Ask about your restaurant's sales, orders, menus and opening hours, using live Deliverect data.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Deliverect MCP server that lets an assistant answer questions about a restaurant's sales, orders, menus and opening hours from live data.

What you can do
  • Answer questions about restaurant sales and orders using live Deliverect data
  • Look up menu contents and opening hours
  • Query the connected Deliverect account through a hosted remote endpoint
  • No individual tools are documented, so exact capabilities beyond these topics are unclear
When to use it
Useful for restaurant operators or staff already on Deliverect who want to ask an assistant about their own sales, orders, menus or opening hours without opening the Deliverect dashboard.
Requirements
A remote MCP endpoint at mcp.deliverect.com; no local package or runtime needed. OAuth authentication is required, so a Deliverect account with access to the relevant restaurant data is needed. Network access to the endpoint.
Before you install
Access is granted through OAuth to live business data, so review which Deliverect account and locations you authorize. Sales, order and menu data are exposed to the assistant and its model provider. The manifest lists no tools, so confirm what the server can read or change before connecting.

Installation

In SourceWeft

  1. Open Deliverect in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/com.deliverect%2Fdeliverect/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "deliverect": {
      "type": "http",
      "url": "https://mcp.deliverect.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • 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.