Issues and workload
Issue trends, SLA breaches, open workload, resolution stats, repeat issues, per-location rankings and inspection status.
AI assistant integration
CineScope exposes a Model Context Protocol (MCP) server. A circuit connects it once via OAuth and can then ask questions of its own operational data in natural language from an AI assistant such as Claude — no exports, no BI tool, no SQL. Read-only, and scoped to what the connected account is already allowed to see.
We'll walk the circuit view, your POS sync and showtime setup on a live screen. Backed by our 30-day guarantee.
The answer comes back as a sentence with the numbers in it, drawn from the same data your case monitor and cinema operations dashboards already show.
Issue trends, SLA breaches, open workload, resolution stats, repeat issues, per-location rankings and inspection status.
Sellout stats, schedule utilisation, room capacity, a title's performance against its usual draw, the week ahead, programming moves and the cost of downtime.
Nothing the assistant can do changes anything. It answers questions about your data; it does not create, edit, close or dispatch anything, and it does not act on its own.
The assistant sees exactly what that person could already see by signing in — never more. A general manager's connector answers about their own sites.
CineScope implements MCP as specified, so it works with any MCP-capable assistant rather than being locked to one vendor's chat window.
A circuit authorises the connection with OAuth, the same way it would any other app. No exports, no BI tool, no SQL, no copy of your data sitting somewhere else.
How CineScope handles hosting, encryption and access control is written up on the security page.
An MCP server is a service that implements the Model Context Protocol, an open standard for giving an AI assistant structured access to a specific system's data and tools. CineScope runs an MCP server for a circuit's own operational data, so an assistant can answer questions about it directly instead of relying on exports or a BI dashboard.
Any assistant that supports the Model Context Protocol, including Claude. Because CineScope implements the standard rather than a proprietary plugin, a circuit is not tied to a single vendor's chat window.
No. The CineScope MCP integration is read-only. The assistant can retrieve and summarise data through purpose-built tools, and it cannot create, edit, close, dispatch or delete anything in the platform.
Exactly what the connected account could see by signing in to CineScope, and nothing beyond it. Permissions are enforced on the CineScope side, so a general manager's connector answers about their own sites while a circuit owner's connector covers the estate.
The circuit authorises the connection once via OAuth from their AI assistant, and the assistant then queries CineScope directly. There is no export step, no separate BI tool and no SQL to write.
It covers roughly 30 purpose-built tools across the estate: issue trends, SLA breaches, open workload, resolution statistics, repeat issues, per-location rankings and inspection status, plus the programming side — sellout stats, schedule utilisation, room capacity, title performance against a title's usual draw, the week ahead, programming moves and the cost of downtime.
No. The MCP server reads the operational data CineScope already holds for your circuit, so questions are answered in a sentence without a warehouse, an export pipeline or a report builder in between.
See also guest sentiment and NPS, programming and film booking analytics — reachable through the same MCP server — and what a circuit pays on the pricing page.
We'll walk the circuit view, your POS sync and showtime setup on a live screen. Backed by our 30-day guarantee.