Bring Digital Signage
to VS Code Copilot
Learn how to connect FusionSignage to VS Code Copilot and start using 17 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the FusionSignage MCP Server?
Connect your FusionSignage account to any AI agent and manage your digital signage network through natural conversation.
What you can do
- Screen Management — List all screens with online/offline status, inspect configurations, update settings, and check real-time connectivity
- Playlist Builder — Create, update, and delete content playlists with media items and display order
- Content Assignment — Assign playlists to specific screens for targeted content delivery
- Media Library — Browse all uploaded media (images, videos, web pages), inspect file metadata, and remove outdated assets
- Content Scheduling — Create time-based schedules with playlist rotation and screen assignments
- Screen Groups — Organize screens into groups for bulk content management
How it works
1. Subscribe to this server
2. Enter your FusionSignage API Key from your account settings
3. Start managing your signage network from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Facility Managers — monitor screen status, push content updates, and manage display groups without accessing the dashboard
- Marketing Teams — schedule campaigns, rotate promotional content, and update digital menus through AI
- IT Administrators — audit screen connectivity, manage media libraries, and troubleshoot display issues
Built-in capabilities (17)
Assign playlist to screen
Verify connectivity
Create a playlist
Create a schedule
Delete media
Delete a playlist
Get media details
Get playlist details
Get screen details
Get screen status
List screen groups
List all media
List all playlists
List schedules
List all screens
Update a playlist
Update a screen
Why VS Code Copilot?
GitHub Copilot Agent mode brings FusionSignage data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 17 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
FusionSignage in VS Code Copilot
FusionSignage and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect FusionSignage to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for FusionSignage in VS Code Copilot
The FusionSignage MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 17 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
FusionSignage for VS Code Copilot
Every tool call from VS Code Copilot to the FusionSignage MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I monitor which screens are online or offline in real time?
Yes. Use list_screens to see all screens with their current online/offline status and assigned content. For a specific screen, use get_screen_status to check real-time connectivity and playback status. Use get_screen for detailed configuration including orientation and playlist assignment.
Can I create a playlist and assign it to a screen?
Yes. Use create_playlist with a JSON payload containing name and media items. Then use assign_playlist with the screen ID and playlist ID to push it to a display. Use update_playlist to modify content order or add new media, and delete_playlist to remove unused playlists.
Can I schedule content to play at specific times?
Yes. The create_schedule tool accepts a JSON configuration with time slots, playlist rotations, and screen assignments. Use list_schedules to view all active schedules. Combine with list_groups to manage multiple screens simultaneously through group assignments.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.