Revel Digital MCP Server

The Revel Digital MCP Server lets AI assistants like Claude, ChatGPT, Cursor, and others interact directly with your Revel Digital digital signage platform using the Model Context Protocol (MCP).

With this server, you can use natural language to manage devices, media, playlists, schedules, templates, data tables, and more — all through your favorite AI-powered tool.

What is MCP?

The Model Context Protocol is an open standard that allows AI applications to securely connect to external data sources and tools. Instead of copying and pasting data between your signage platform and an AI assistant, MCP lets the AI interact with Revel Digital directly on your behalf.

Getting Started

1. Have a Revel Digital account with API access
2. Connect your MCP client using one of the server endpoints below
3. Authenticate via the browser-based OAuth login when prompted
4. Start using tools to manage your digital signage

No API keys or manual configuration required — the OAuth flow handles everything automatically.

See it in Action

Watch this short demo showing Claude generating a report using the Revel Digital MCP Server:

Server Endpoints

Authentication

The MCP server uses OAuth 2.0 / OpenID Connect via Revel Digital's identity provider. When you first connect:

1. Your MCP client sends a request to the server
2. The server prompts your client to start the OAuth flow
3. A browser window opens to the Revel Digital login page
4. You sign in with your Revel Digital credentials
5. After successful login, the browser redirects back and your client receives an access token
6. All subsequent tool calls use this token automatically

Connecting Your AI Client

Claude Desktop

Add the following to your Claude Desktop MCP configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "revel-digital": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.reveldigital.io/mcp"
      ]
    }
  }
}

Restart Claude Desktop after saving. A browser window will open for authentication on first use.

Note: Claude Desktop uses mcp-remote as a local proxy to connect to remote MCP servers. Make sure you have Node.js 18+ installed.

Claude Code (CLI)

claude mcp add revel-digital --transport http https://mcp.reveldigital.io/mcp

Or add to your .mcp.json file:

{
  "mcpServers": {
    "revel-digital": {
      "type": "url",
      "url": "https://mcp.reveldigital.io/mcp"
    }
  }
}

Cursor

1. Open Settings → MCP Servers
2. Click Add Server
3. Set the URL to https://mcp.reveldigital.io/mcp
4. Select Streamable HTTP as the transport type
5. Click Save

VS Code (Copilot)

Add the following to your VS Code settings.json:

{
  "mcp": {
    "servers": {
      "revel-digital": {
        "type": "http",
        "url": "https://mcp.reveldigital.io/mcp"
      }
    }
  }
}

ChatGPT Desktop

1. Open Settings → Tools & Plugins → MCP Servers
2. Click Add Server
3. Enter the URL: https://mcp.reveldigital.io/mcp
4. Authenticate via the browser when prompted

Windsurf

1. Open Settings → MCP
2. Add a new remote server with URL https://mcp.reveldigital.io/mcp
3. Save and connect

Other MCP Clients

For any MCP-compatible client, connect to:

• Streamable HTTP: POST https://mcp.reveldigital.io/mcp
• SSE: GET https://mcp.reveldigital.io/sse

Available Tools

The server provides 46 tools across 14 categories. For complete parameter documentation, see the full tool reference.

Account & Users (5 tools)

Manage account information, organizations, users, and audit logs.

Devices (7 tools)

Manage devices (players) registered to the account. Each device represents a physical display player (Android, Chrome OS, Windows, Linux, or BrightSign) that renders scheduled content.

Device Groups (5 tools)

Organize devices into hierarchical folder structures.

Media (5 tools)

Manage media files in the Revel Digital library including images (JPG, PNG, GIF), videos (MP4, WebM), PDFs, web pages, and other content types.

Media Groups (4 tools)

Organize media files into hierarchical folder structures.

Playlists (5 tools)

Manage playlists — ordered sequences of media items (images, videos, web pages) that play in rotation on devices.

Playlist Groups (2 tools)

Organize playlists into folders. Tools follow the same pattern as other group tools (list_playlist_groups, create_playlist_group).

Schedules (5 tools)

Manage schedules — time-based rules that determine when playlists, templates, or campaigns play on devices.

Schedule Groups (2 tools)

Organize schedules into folders. Tools follow the same pattern as other group tools (list_schedule_groups, create_schedule_group).

Templates (4 tools)

Manage templates — multi-zone screen layouts where each zone can display a different playlist, web page, or media item simultaneously. Templates also support JavaScript scripting for interactive or dynamic content.

Template Groups (2 tools)

Organize templates into folders. Tools follow the same pattern as other group tools (list_template_groups, create_template_group).

Data Tables (17 tools)

Manage data tables — structured row/column data that can be used in templates and playlists for dynamic content. Includes full CRUD, batch operations, CSV export, and row version history with rollback.

Table Management:

Row Operations:

Batch Operations:

Export & Versioning:

Alerts (3 tools)

Monitor and manage device alerts. Alerts are generated automatically when monitored conditions trigger — for example, when a device goes offline, encounters a content error, or exceeds resource thresholds.

Analytics (13 tools)

Query the AdHawk analytics engine. All analytics tools require startDate and endDate parameters and support optional device filtering.

Play & Content Logs:

Aggregated Metrics:

Audience Analytics (requires audience measurement hardware such as a camera with face detection):

Other:

Troubleshooting

"Connection Error - Check if your MCP server is running" Make sure you're using the correct transport type (Streamable HTTP vs SSE) and the correct URL path (/mcp or /sse).

"Mcp-Session-Id header is required" You're connecting with SSE transport to the Streamable HTTP endpoint. Either switch to Streamable HTTP transport or use the /sse endpoint.

OAuth login loop Clear your browser cookies for mcp.reveldigital.io and id.reveldigital.com, then try connecting again.

Resources

• Full MCP Server Documentation
• GitHub Repository
• Revel Digital REST API Docs
• MCP Specification