Getting Started with MCP

Enable AI agent control for your digital signage in 2 minutes.

Prerequisites

• avSign.lite installed (any platform: Windows, Linux, Android, Fire TV)
• Network connectivity (MCP server binds to device IP)
• AI assistant with MCP support (Claude, ChatGPT, or custom client)

Step 1: Enable MCP Server

Desktop/Mobile Apps

1. Open avSign.lite
2. Navigate to Settings → Server Settings
3. Find MCP Server section
4. Toggle Enable MCP Server to ON
5. Note the Port (default: 3333)
6. Note your Device IP Address

Configuration Options

Server Status: Once enabled, MCP server starts automatically and runs in the background.

Step 2: Get Your Connection Details

After enabling MCP, you’ll see:

✓ MCP Server Running
  Endpoint: http://192.168.1.100:3333/mcp
  Status: Active
  Connections: 0

Important: Replace 192.168.1.100 with your actual device IP address.

Finding Your Device IP

Windows:

ipconfig
# Look for "IPv4 Address"

Linux/macOS:

ifconfig
# or
ip addr show

Android/Fire TV:

• Settings → Network → Wi-Fi → Advanced → IP Address

Step 3: Connect Your AI Agent

Option A: Claude Desktop (Recommended)

1. Open Claude Desktop
2. Go to Settings → MCP Servers
3. Add new server:

   {
     "avsign-lite": {
       "endpoint": "http://192.168.1.100:3333/mcp",
       "transport": "http"
     }
   }
   

4. Restart Claude Desktop

Option B: Custom MCP Client

import requests

# MCP endpoint
mcp_url = "http://192.168.1.100:3333/mcp"

# Call a tool
response = requests.post(mcp_url, json={
    "tool": "device.status",
    "parameters": {}
})

print(response.json())

Option C: ChatGPT with MCP Plugin

(Coming soon - MCP support in ChatGPT plugins)

Step 4: Test the Connection

Simple Status Check

Ask your AI assistant:

"Check the status of my digital signage device"

Expected response:

Your avSign.lite device is healthy:
- Application: avSign.lite v1.0.5
- Platform: Windows 11
- Playback: Currently playing "Welcome_Screen"
- Content: 45 items, 12 playlists, 8 templates
- Uptime: 3 days, 4 hours

Quick Action Test

Try a simple command:

"What playlists are available?"

The AI should return a list of your playlists with details.

Step 5: First Real Command

Now try publishing content:

"Play the welcome playlist now"

Or create a schedule:

"Schedule the promotional video to play every weekday from 9am to 5pm"

Troubleshooting

MCP Server Not Starting

Problem: Toggle switches to OFF immediately after enabling

Solutions:

• Check if port 3333 is available: netstat -an | findstr 3333
• Try a different port in Settings → MCP Server Port
• Check firewall settings (allow port 3333 inbound)

AI Agent Can’t Connect

Problem: “Connection refused” or timeout errors

Solutions:

1. Verify device IP address is correct
2. Ping the device: ping 192.168.1.100
3. Check firewall allows port 3333
4. Ensure MCP server status shows “Active”
5. Try from same network first (cross-network requires port forwarding)

Commands Don’t Work

Problem: AI receives responses but actions don’t execute

Solutions:

• Check the AI is calling tools (not just explaining them)
• Verify you have content/playlists available
• Check device logs: Settings → Logs → MCP Server

“Terminal not found” Errors

Default behavior: If no terminals specified, MCP auto-assigns to device terminal

If error persists:

• Check terminals exist: Settings → Terminals
• Ensure at least one terminal is active
• Manually specify terminal in command: “on terminal 1”

Security Best Practices

Production Deployments

1. Enable Authentication:

   • Settings → MCP Server → Require Authentication
   • Generate API token
   • Provide token to AI agent

2. Use HTTPS:

   • Set up reverse proxy (nginx, Caddy)
   • Obtain SSL certificate
   • Configure MCP to bind to localhost
   • Expose via HTTPS proxy

3. Firewall Rules:

   • Restrict MCP port to trusted IPs only
   • Use VPN for remote access
   • Never expose directly to internet without authentication

Development/Testing

For local testing, defaults are fine:

• No authentication required
• HTTP is acceptable
• Port 3333 open on local network

Next Steps

Now that MCP is set up:

1. Explore Available Tools - Learn all 9 MCP tools
2. View Use Cases - Real-world examples
3. Integration Guide - Advanced API usage

Quick Reference

Essential Commands

MCP Endpoint Format

http://<device-ip>:<port>/mcp

Example: http://192.168.1.100:3333/mcp

Default Terminal Assignment

When no terminals specified in commands, MCP automatically assigns to the device’s own terminal (on-device CMS mode).

Need help? Join our Discord community or check the FAQ.