Skip to main content
Glama
Restaurant365 MCP Server

Restaurant365 MCP Server

Restaurant365 MCP Server — Riviera Dining Group

MCP server for the Restaurant365 OData API (live, near-real-time read access).

Portable Team MCP command

Use this in Cursor Dashboard → Integrations & MCP → Team MCP Servers:

Field

Value

Name

restaurant365

Type

stdio

Command

npx

Args

-y, github:msoutumuro123/r365-mcp-server

Environment variables:

Variable

Description

R365_DOMAIN

Instance subdomain (default: rivieradining)

R365_USERNAME

R365 username

R365_PASSWORD

R365 password

Aliases also supported: RESTAURANT365_ODATA_USERNAME, RESTAURANT365_ODATA_PASSWORD, RESTAURANT365_DOMAIN.

Username is sent as domain\username per R365 OData requirements.

After saving the Team MCP server, click Add to Team Marketplace so teammates can install it from Customize in the IDE.

Related MCP server: Xledger MCP Server

Local config (~/.cursor/mcp.json)

{
  "mcpServers": {
    "restaurant365": {
      "command": "npx",
      "args": ["-y", "github:msoutumuro123/r365-mcp-server"],
      "env": {
        "R365_DOMAIN": "rivieradining",
        "R365_USERNAME": "your-user",
        "R365_PASSWORD": "your-password"
      }
    }
  }
}

Tools

  • r365_test_connection — Verify live OData connection

  • r365_list_entities — List available OData views

  • r365_list_locations — List all accessible locations

  • r365_query — Generic OData query with $filter, $select, $top

  • r365_get_transactions — Financial transactions

  • r365_get_gl_accounts — GL account master data

  • r365_get_employees — Employee records

  • r365_get_sales — Sales ticket headers

Build

npm install
npm run build

Available Tools

5 tools
r365_get_transactionsGet R365 TransactionsA
Read-onlyIdempotent

Retrieve financial transactions from Restaurant365.

Args:

  • location_id: Optional location GUID filter

  • date: Optional business date filter (ISO 8601, e.g. 2026-06-01T00:00:00Z)

  • type: Optional transaction type (e.g. 'Journal Entry', 'AP Invoice')

  • top: Max rows (default 100)

Inputs: top, date, type, location_id.

r365_list_entitiesList R365 OData EntitiesB
Read-onlyIdempotent

List all available Restaurant365 OData entity endpoints.

Inputs: no named parameters.

r365_list_locationsList R365 LocationsC
Read-onlyIdempotent

Retrieve all Restaurant365 locations accessible to the configured user.

Inputs: top, filter.

r365_queryQuery R365 OData EntityA
Read-onlyIdempotent

Run a read-only OData query against any R365 entity.

Args:

  • entity: OData view name (Location, Transaction, GlAccount, etc.)

  • filter: OData $filter expression (e.g. "date ge 2026-01-01T00:00:00Z")

  • select: OData $select comma-separated fields

  • orderby: OData $orderby expression

  • top: Max rows (default 100, max 1000)

  • skip: Offset for pagination

Inputs: entity (required), top, skip, filter, +2 more.

r365_test_connectionTest R365 ConnectionA
Read-onlyIdempotent

Verify live connection to Restaurant365 OData using configured credentials. Returns location count on success.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: connection verification, entity enumeration, location listing, generic querying, and transaction retrieval. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow the 'r365_' prefix and snake_case naming convention. Most use verb_noun pattern (test_connection, list_entities, list_locations, get_transactions), with 'r365_query' being a concise verb form, maintaining overall consistency.

    Tool Count5/5

    Five tools is appropriate for a read-only OData API server, covering connection testing, schema discovery, location listing, generic querying, and a specific transaction query without being excessive or sparse.

    Completeness4/5

    The set provides essential read-only operations: test, list entities, list locations, generic query, and specific transaction query. While a dedicated get-by-ID tool is missing, the generic query can handle it via filters. No write operations are expected per scope.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables read-only analytics queries on Acumatica ERP data, including sales orders, inventory, shipments, invoices, purchase orders, customers, and OData generic inquiries.
      16
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Xledger accounting data via GraphQL API for querying invoices, balances, projects, timesheets, and more.
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Addepar portfolio and ownership data for financial reporting, with transparent provenance caveats and compliance-oriented audit logging.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to customer and recurring-billing state from Recurly, including accounts, subscriptions, invoices, and payment outcomes.
      90 npm
      MIT