How to Use the FusionSignage MCP in VS Code Copilot

Q: How do we share the FusionSignage configuration in VS Code Copilot?

Create a .vscode/mcp.json file in your repository and commit it to share the FusionSignage MCP Server configuration. Every team member with the VS Code Copilot extension will instantly gain access to the signage tools.

Q: Can we check screen connectivity using FusionSignage inside VS Code Copilot?

Yes, anyone on the team asks VS Code Copilot to run checkfusionstatus to verify the API connection. This makes it easy to rule out network issues during deployments.

Q: How does FusionSignage handle scheduled playlist changes in VS Code Copilot?

Instruct the VS Code Copilot agent to run createschedule to set up automated playlist swaps. The agent manages the timing parameters so you do not write custom cron jobs.

Q: Can we clean up old FusionSignage playlists from the VS Code Copilot workspace?

Yes, ask the agent in VS Code Copilot to run deleteplaylist to remove retired assets. This keeps your environment clean and prevents accidental deployments of legacy content.

Manage your entire FusionSignage network across your team using VS Code Copilot and shared workspace tools.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect FusionSignage MCP to VS Code Copilot

Create your Vinkius account to connect FusionSignage to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup FusionSignage with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Monitor screens as a team in VS Code Copilot

Commit your MCP Server configuration to your repository so your entire engineering team accesses the FusionSignage network via VS Code Copilot. Developers run `list_screens` to audit active hardware directly from their shared VS Code Copilot workspace. When troubleshooting a FusionSignage display issue, ask the VS Code Copilot agent to run `get_screen_status` to diagnose the problem. Having these FusionSignage tools inside the editor means team members never share browser sessions outside VS Code Copilot.

Coordinate playlists across your workspace

Keep your staging and production environments aligned by letting the VS Code Copilot agent run `list_playlists` and `create_playlist` over this MCP connection. Team members inspect FusionSignage configurations together during code reviews in VS Code Copilot. When a FusionSignage playlist is ready for deployment, the VS Code Copilot agent calls `assign_playlist` to push it to the correct screens. This keeps your FusionSignage content pipeline tightly integrated with your VS Code Copilot version control system.

Check media assets before they go live

Prevent broken displays by using this MCP Server in VS Code Copilot to run `get_media_item` to verify file formats and sizes before scheduling. The agent checks the FusionSignage asset metadata inside VS Code Copilot to make sure it matches your hardware requirements. Audit active schedules with `list_schedules` inside VS Code Copilot to ensure no overlapping events cause FusionSignage display conflicts. If you find a bad schedule in VS Code Copilot, use `create_schedule` to overwrite the target display's calendar.

Setup guide

Set up FusionSignage MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the FusionSignage MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the FusionSignage tools listed. Try asking: "List my recent FusionSignage transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "fusionsignage-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by FusionSignage. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect FusionSignage now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about FusionSignage MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your repository and commit it to share the FusionSignage MCP Server configuration. Every team member with the VS Code Copilot extension will instantly gain access to the signage tools.

Yes, anyone on the team asks VS Code Copilot to run `check_fusion_status` to verify the API connection. This makes it easy to rule out network issues during deployments.

Instruct the VS Code Copilot agent to run `create_schedule` to set up automated playlist swaps. The agent manages the timing parameters so you do not write custom cron jobs.

Yes, ask the agent in VS Code Copilot to run `delete_playlist` to remove retired assets. This keeps your environment clean and prevents accidental deployments of legacy content.

All FusionSignage screen configurations, schedule logs, and media IDs transmit through secure, encrypted tunnels. Vinkius executes these MCP requests in a zero-trust environment, so your physical displays remain protected from unauthorized access.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript