Restaurant365 MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Restaurant365 MCP Server Show me today's sales transactions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
|
Type |
|
Command |
|
Args |
|
Environment variables:
Variable | Description |
| Instance subdomain (default: |
| R365 username |
| 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 connectionr365_list_entities— List available OData viewsr365_list_locations— List all accessible locationsr365_query— Generic OData query with $filter, $select, $topr365_get_transactions— Financial transactionsr365_get_gl_accounts— GL account master datar365_get_employees— Employee recordsr365_get_sales— Sales ticket headers
Build
npm install
npm run buildAvailable Tools
5 toolsr365_get_transactionsGet R365 TransactionsARead-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 EntitiesBRead-onlyIdempotent
List all available Restaurant365 OData entity endpoints.
Inputs: no named parameters.
r365_list_locationsList R365 LocationsCRead-onlyIdempotent
Retrieve all Restaurant365 locations accessible to the configured user.
Inputs: top, filter.
r365_queryQuery R365 OData EntityARead-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 ConnectionARead-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
Scored across 5 tools
Each tool serves a distinct purpose: connection verification, entity enumeration, location listing, generic querying, and transaction retrieval. No overlap or ambiguity.
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.
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.
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
Query financial statements, KPIs, ratios, cash forecasts and budgets from your general ledger
Read stores, menu items, customers, sale reports and single sales in Linga POS.
Read-only zobrx e-commerce data: P&L, orders, inventory, marketplace, tax & shelf insights.
Read-only NuMetric.work accounting & ERP data: statements, KPIs, reports, invoices, documents.
Related MCP Servers
- FlicenseAqualityDmaintenanceEnables read-only analytics queries on Acumatica ERP data, including sales orders, inventory, shipments, invoices, purchase orders, customers, and OData generic inquiries.16-
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to Xledger accounting data via GraphQL API for querying invoices, balances, projects, timesheets, and more.2MIT
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to Addepar portfolio and ownership data for financial reporting, with transparent provenance caveats and compliance-oriented audit logging.-
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to customer and recurring-billing state from Recurly, including accounts, subscriptions, invoices, and payment outcomes.90 npmMIT