3,400+ MCP servers ready to use
Vinkius

FusionSignage MCP Server for VS Code CopilotGive VS Code Copilot instant access to 17 tools to Assign Playlist, Check Fusion Status, Create Playlist, and more

Built by Vinkius GDPR 17 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Use with Your AI Agent

Ask AI about this App Connector for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The FusionSignage app connector for VS Code Copilot is a standout in the Productivity category — giving your AI agent 17 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install FusionSignage and 3,400+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "fusionsignage": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
FusionSignage
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About FusionSignage MCP Server

Connect your FusionSignage account to any AI agent and manage your digital signage network through natural conversation.

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.

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

The FusionSignage MCP Server exposes 17 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 17 FusionSignage tools available for VS Code Copilot

When VS Code Copilot connects to FusionSignage through Vinkius, your AI agent gets direct access to every tool listed below — spanning digital-signage, screen-management, content-scheduling, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

assign_playlist

Assign playlist to screen

check_fusion_status

Verify connectivity

create_playlist

Create a playlist

create_schedule

Create a schedule

delete_media

Delete media

delete_playlist

Delete a playlist

get_media_item

Get media details

get_playlist

Get playlist details

get_screen

Get screen details

get_screen_status

Get screen status

list_groups

List screen groups

list_media

List all media

list_playlists

List all playlists

list_schedules

List schedules

list_screens

List all screens

update_playlist

Update a playlist

update_screen

Update a screen

Connect FusionSignage to VS Code Copilot via MCP

Follow these steps to wire FusionSignage into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using FusionSignage

Ask Copilot: "Using FusionSignage, help me...". 17 tools available

Why Use VS Code Copilot with the FusionSignage MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with FusionSignage through the Model Context Protocol.

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

FusionSignage + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the FusionSignage MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for FusionSignage in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with FusionSignage immediately.

01

"Show all screens and highlight any that are offline."

02

"Create a new promotional playlist with our latest media and assign it to all lobby screens."

03

"Show all content schedules and the screen groups configured in our account."

Troubleshooting FusionSignage MCP Server with VS Code Copilot

Common issues when connecting FusionSignage to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

FusionSignage + VS Code Copilot FAQ

Common questions about integrating FusionSignage MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.