Connect your AI assistant to Vistarro

What the connector is

The Vistarro connector lets an AI assistant you already use — Claude on the web, the Claude desktop app, Claude Code, and other tools that speak the open MCP standard — look at your Vistarro data while you chat with it. Once connected you can ask things like “which screens at the Oshawa store are offline?”, “what is on the lunch menu board right now?” or “list the playlists that still use last season’s promo”, and the assistant answers from your live account.

This first release is read-only. Your assistant can look things up but cannot change anything on your screens. Making changes through the connector comes in a later release and will be a separate permission you choose to grant.

Add it to Claude

You need a Vistarro account that belongs to a company, and the Claude plan you already have. Anthropic lists custom connectors as available on Free, Pro, Max, Ultra, Team and Enterprise plans; on Team and Enterprise plans an organization owner adds the connector first (under Organization settings › Connectors) and each member then clicks Connect.

Claude on the web or the desktop app

Claude Code

From a terminal, register the server once and then sign in from inside Claude Code:

claude mcp add --transport http bravura https://bravuraapp.com/mcp

Start Claude Code, type /mcp, pick bravura and follow the sign-in steps that open in your browser (the same magic link, company choice and Allow as above). claude mcp list shows the server as Connected once that is done. Add --scope user to the command if you want the server available in every project rather than just the current one.

Other MCP clients

Claude is the client we support and test. Any other client that supports remote MCP servers over Streamable HTTP with OAuth sign-in (for example ChatGPT or Cursor) is expected to work with the same URL, but we have not tested those products ourselves. Point it at https://bravuraapp.com/mcp; the technical details below cover what the client needs to support. If you use one and run into trouble, tell us and we will test it with you.

What it can and cannot do

• It can never do more than you can. Every request runs under your own Vistarro account and your role in the company, checked again on every single call.
• It only sees the company you chose when you clicked Allow. Other companies you belong to stay invisible to it.
• Today it is read-only: it can view content (assets, playlists, artboards, set lists, schedules, menus, campaigns, themes) and screens (players, their status, health and proof-of-play), plus basic reference data such as your sites, tags, regions and language settings.
• It cannot publish, edit, push to screens, send emergency broadcasts or change settings. Those permissions are not offered yet, even if the assistant asks for them.
• Vistarro system administration is never reachable through a connector.

Disconnecting

You can disconnect at any time, from either side:

• In Vistarro: open your account menu (your name, top right) › Connected apps and click Revoke next to the connection. The assistant loses access immediately, including any sign-in it still has stored.
• In Claude: go to Customize › Connectors, open the three-dot menu next to Vistarro and choose Remove.
• In Claude Code: run claude mcp logout bravura, then claude mcp remove bravura.

Access also ends on its own if you leave the company or your Vistarro account is closed. Each sign-in lasts 15 minutes and is renewed quietly in the background for up to 30 days of use; after that, or after any revoke, the assistant has to be connected again.

Security

• Standard sign-in, no passwords. The connection uses OAuth 2.1 with PKCE, the same mechanism the big productivity apps use. You sign in on a Vistarro page with your usual magic link; Claude never sees a Vistarro password because there is none.
• Vistarro never sees your conversation. We only receive the specific look-ups the assistant decides to make (for example “list players at site 12”) and return the data. What you typed, and what the assistant says back, stays between you and Claude.
• Checked on every call. Each request re-checks that the connection is still active, that you are still a member of the company, and that your current role allows the look-up.
• What Vistarro logs. Your Connected apps page shows each connection, the company and permissions it was given, when it was connected and when it was last used. When changes through the connector arrive in a later release, every change will add a row to the company’s activity log that names the connected app, so your team can always see what an assistant did versus what a person did. Read-only look-ups are not logged individually.
• Your assistant’s own privacy terms still apply. How Claude handles the data it reads is governed by Anthropic’s terms for your plan, not by Vistarro.

Technical details

For integrators and anyone connecting a client other than Claude.

MCP endpoint	https://bravuraapp.com/mcp — Streamable HTTP, POST only (JSON-RPC in, JSON out; GET/DELETE answer 405), stateless.
Protected resource metadata	https://bravuraapp.com/.well-known/oauth-protected-resource (RFC 9728; also served at /.well-known/oauth-protected-resource/mcp). An unauthenticated POST to the endpoint returns 401 with a WWW-Authenticate: Bearer resource_metadata=… challenge pointing here.
Authorization server metadata	https://bravuraapp.com/.well-known/oauth-authorization-server (RFC 8414). Issuer https://bravuraapp.com.
Endpoints	/oauth/authorize, /oauth/token, /oauth/revoke.
Grant types	authorization_code with PKCE (S256 only, required) and refresh_token (rotating; reuse of an old refresh token revokes the chain). Public clients only (token_endpoint_auth_methods_supported: none). The resource indicator (RFC 8707) is honoured and must be the MCP endpoint; the authorization response carries iss (RFC 9207).
Client identity	Client ID Metadata Documents (preferred): use your public https metadata URL as the client_id; Vistarro fetches it and validates the redirect URI against it. Pre-registered clients are available to partners on request.
Tokens	Access tokens last 15 minutes; refresh tokens 30 days, sliding. Revocation per RFC 7009 at /oauth/revoke; revoking a grant in Vistarro also invalidates its refresh tokens.
Tenancy	One grant covers exactly one company, chosen at consent. Every call is re-authorised against the grant, the user’s current membership and live permissions.

Scopes

All six scopes are advertised in metadata. A scope is a ceiling on top of the user’s own permissions, never an extension of them, and a write scope does not imply its read scope.

Scope	Allows	Status
content:read	Read assets, playlists, artboards, set lists, schedules, menus, campaigns and themes.	Available
fleet:read	See players, their status, health and proof-of-play reports.	Available
content:write	Create and change content, including menu edits and sold-outs.	Available
fleet:push	Assign and push content to players, schedule pushes, change player settings, send device commands.	Available
broadcasts	Create, activate and deactivate emergency broadcasts; manage takeover groups.	Available
settings	Artboard defaults, theme schedule, tags, site menu pages and power schedules.	Available

Basic reference data (sites, tags, regions, company and language settings) is readable under any grant without a dedicated scope.

Questions?

Email [email protected] or use the contact form. If you work with a Vistarro reseller, they can help you connect as well. Vistarro is operated by Triacolyte Business Solutions Inc., Ontario, Canada.