This guide provides five practical prompts based on real MCP capabilities, enabling digital signage teams to leverage natural language interfaces for portal and content management within Wallboard 2.1.
Prompt — Portal Setup From Scratch
The Prompt
Set up an entire Wallboard portal for our company with:
- Two teams: "Marketing" and "Operations"
- Three device groups: "Lobby", "Break Room", "Conference Rooms"
- Permissions so Marketing can manage lobby and break room content,
Operations manages conference room displays
- Enable SSO through Azure AD
- Register 25 screens across these locations
- Import our company logo as default brandingWhat Happens Behind the Scenes
1. MCP reads your intent: complete portal setup from zero
2. It creates two teams in Wallboard with appropriate role assignments
3. Creates the three device groups with proper organizational structure
4. Configures role-based permissions so each team has the right access
5. SSO is enabled for the user
6. Registers 25 screens, organizing them into the device groups
7. Confirms everything is configured and provides a summary of what was set up
The Outcome
Entire portal operational in minutes instead of hours. Team members get access automatically through corporate login. Screen inventory is organized and documented. Permissions are enforced from day one. No manual credential juggling. Setup time — one prompt instead of 2–3 hours of manual configuration.
Impact: A regional healthcare network needed to onboard a new office building with Wallboard in two weeks. Instead of manual setup screens, credential management, and team coordination, they used this prompt. Result: portal was live before their first staff arrived, with teams already able to manage their assigned screens through their existing corporate credentials.
Prompt — Playlist Management Via Natural Language
The Prompt
Create a new playlist called "Daily Standup" that shows:
1. Company news (30 seconds)
2. Local weather (20 seconds)
3. Today's events from our calendar (30 seconds)
Run it on all screens tagged "office" Monday-Friday 8am-9am.
After 9am, switch to the regular "Office Default" playlist.
Confirm when it's set up.What Happens Behind the Scenes
1. MCP interprets your intent: create a time-boxed playlist for a daily ritual
2. It creates three slides: "Company News" linked to your configured news datasource, "Local Weather" pulling current conditions automatically, and "Today's Events" pulling from your company calendar
3. Creates a playlist ordering these three slides with specified durations
4. Applies scheduling: Monday–Friday 8am–9am show Daily Standup, revert to Office Default afterwards
5. Targets all screens tagged "office"
6. Logs the creation with full context for compliance
The Outcome
Employees see relevant information at the right time. Daily ritual becomes automatic — no manual updates. Each slide pulls live data, so it's always current. Easy to adjust durations or add slides later. Setup time — one prompt instead of 30 minutes of playlist building.
Impact: A corporate office was manually updating a daily standup playlist every morning. With this prompt, the playlist began updating automatically. News refreshes hourly, weather updates every 30 minutes, and calendar events pull automatically. Staff sees consistent, relevant information at standup time without operational overhead.
Prompt — Scheduled Content Rollout Across Regions
The Prompt
Deploy the "Spring Campaign 2026" playlist to all screens tagged 'retail'
in the Northeast region. Start on Friday, March 21, at 6pm local time
in each store. Before deploying, show me which stores are affected,
how many screens that is, and what they're currently showing.What Happens Behind the Scenes
1. MCP queries your screen inventory for screens matching criteria: Tag = "retail", Region = "Northeast"
2. Generates a pre-flight report showing: 47 retail screens across 12 stores, current content on each screen, store names and locations
3. Schedules the deployment: creates a scheduled deployment for March 21 6pm local time, handles timezone differences automatically, queues content to deploy at the exact moment
4. Confirms the plan is ready for your review
The Outcome
Complete visibility before deployment — you know exactly what changes. Scheduled for off-peak hours so shoppers aren't disrupted. All 47 screens deploy simultaneously with consistency. Setup time — one prompt instead of coordinating with 12 regional managers.
Impact: A retail company previously spent days coordinating regional deployments. Each regional manager had to be contacted, schedules confirmed, and changes made screen by screen. With this prompt, they get a pre-flight report showing exactly what's changing, deploy to all locations simultaneously at the right time, and it's done. The marketing campaign goes live on Friday evening across the entire Northeast region, with no manual coordination required.
Prompt — Datasource Setup and Scheduling
The Prompt
Create an AI and webscraper datasource that harvests our company's events page every
Day/Week hours and pulls upcoming events within 50 miles of our office.
Show event name, date, time, location, and description. Create a slide
from this datasource and schedule it on all lobby screens during
business hours (8am-6pm). Update the datasource even if the events
website changes its layout.What Happens Behind the Scenes
1. MCP reads your intent: automated event discovery and display
2. It configures the AI & Web Scraper Datasources to: access your company's events page, extract event details semantically, filter by geographic proximity (within 50 miles), and update Daily/Weekly
3. Creates an "Upcoming Events" slide that displays this datasource
4. Schedules the slide on all screens tagged "lobby"
5. Business hours rule: show during 8am–6pm, revert to default outside those hours
6. AI adapts automatically if your events page structure changes
The Outcome
Employees always see current local events without manual updates. Content is fresh and relevant every Day/Week. Automatic adaptation if your events page gets redesigned. Setup time — one prompt instead of 30 minutes of manual datasource configuration.
Impact: A corporate campus wanted to promote local events to employees, but spent 2 hours per week manually copying events from their website to Wallboard. With this datasource, the process is fully automated. Events are pulled every 6 hours, adapt to changes on the website, and display on all lobby screens. That 2 hours per week is freed up, and employees always see current events.
What Makes These Prompts Work
These aren't complex technical requests; they're descriptions of business needs. They work because of four key factors:
Intent-based, not syntax-based — You describe the outcome you want. MCP and Claude figure out the API calls and handle the details.
Built on real capabilities — Each prompt uses documented Wallboard features: playlist management, content scheduling, asset import, datasource configuration, and team-based access. These are in use by organizations running Wallboard today.
Transparent execution — You can ask MCP to show you what it will do before executing, giving you full visibility and control over changes to your signage network.
Your AI assistant handles complexity — Claude or ChatGPT reads Wallboard's capabilities and builds the right sequence of actions. Timezone math, screen filtering, and conditional logic — all handled by the AI.
How to Get Started
MCP is available in Wallboard 2.1 on March 10. You'll need:
A Wallboard account with MCP usage enabled (existing permissions/user roles are maintained), access to Claude, ChatGPT, or your in-house AI, and 5 minutes to enable MCP in Settings.
Ready to try it? — Enable MCP in your Wallboard account and try one of these prompts with your AI assistant.
These prompts show what's possible when you can describe signage work in English instead of clicking through interfaces. Portal setup, playlist management, asset import, content scheduling, and datasource configuration — all become conversational.
Interested in delving deeper? Download our guide: 5 MCP Prompts for Digital Signage Teams
.png)
