Fugo for Claude

Fugo for Claude is a connection that lets you manage your Fugo digital signage system through conversations with Claude, Anthropic's AI assistant.

You can ask Claude about your existing screens or give it a job, such as preparing a playlist or publishing content. Claude then carries out the supported actions directly in Fugo. Your screens still run through Fugo, and you can continue managing them in the CMS whenever you want.

MCP stands for Model Context Protocol. It's an open standard that allows AI assistants to connect to other software and use its tools.

Think of it as the connection that allows Claude to do something with the information you're discussing. Rather than giving you instructions for creating a playlist, Claude can use Fugo's tools to create one in your account.

Fugo provides the MCP server and handles requests from Claude. You don't need to understand the underlying protocol to use it.

Learn more in the Fugo MCP overview.

Once you've connected your Fugo account, you can give Claude a task in ordinary language, much as you would explain it to a colleague.

Say you want to show a new promotion across your UK stores. Claude can look up the relevant screens, find the media you've already uploaded and create a playlist with the appropriate targeting. If it needs to know which promotion you're referring to or when it should start, it can ask.

The actions happen in Fugo, so the resulting content and playlists are available in your CMS too.

You don't need to know every Fugo setting or which buttons to click for a particular task. Describe what you need, and Claude can work through the supported operations.

You'll still want to understand the basics of your screen network: which locations you're managing, what content should be shown and when. And for more detailed configuration or anything the connection doesn't support, Fugo CMS is always there.

The Fugo MCP connection provides both read and write capabilities, although those aren't identical across every part of the product.

Claude can look up:

• Screens and their assigned content
• Media files, folders and existing content
• Playlists and triggers
• Existing TV dashboards
• Spaces and their users

Fugo's MCP tools can also perform actions such as:

• Uploading media or replacing an existing file
• Creating and publishing playlists
• Targeting content to individual screens or groups defined by screen properties
• Creating manual triggers
• Publishing webpages, HTML and media to screens
• Unpublishing or permanently deleting playlists
• Creating, updating or deleting Spaces, where administrator authorization permits it

There are boundaries. For example, the connection doesn't currently create or edit TV dashboards, and it doesn't provide general editing access to every existing playlist.

For the technical breakdown, see the Fugo MCP overview.

Both. You can use Claude to draft an announcement, prepare information for display or build a simple piece of screen content, then use Fugo's publishing tools to get supported content onto your screens.

Claude can also find and reuse media you've already uploaded to Fugo. So if you've got an established library of promotional images, company announcements or videos, there's no need to recreate those assets.

For more involved designs, you can still use Fugo's Design Studio to build and edit screen content directly.

Yes. Fugo's MCP tools support creating playlists using existing media, content and dashboards, then targeting them to selected screens or screens matching particular properties.

The publishing tools also support different playback behaviors. You can show something once, add content to the regular rotation or keep it on screen until it's stopped.

You can inspect and manage the resulting playlists in Fugo CMS. See how Fugo playlists work.

Yes. Claude can work with the screens and Spaces available to your Fugo account, including properties that identify groups of displays.

For example, you could ask for a playlist to be published to every screen associated with a particular region. Fugo's property-based targeting lets you manage that group without selecting each screen individually.

This is particularly useful for organizations that manage different content across offices, retail locations or departments.

Yes. Claude can retrieve screen information from Fugo, including connection status.

You could ask which screens are offline or check the status of a particular reception display.

For detailed screen settings, monitoring and troubleshooting, you can still use Fugo CMS.

Claude can find dashboards that are already configured in Fugo and use existing dashboard content when preparing playlists.

Setting up a new dashboard connection is different. Claude's current MCP tools don't create dashboards or configure their authentication and refresh settings.

For that, Fugo has a dedicated TV Dashboards feature that handles displaying business data on screens, including dashboards protected by SSO and two-factor authentication.

Yes. Fugo's publishing tools support temporary playback, including showing content once and returning to the regular playlist, or keeping it on screen until stopped.

You could use this for a visitor welcome, a company-wide announcement or information that needs to be shown during an event.

Fugo also offers smart content triggers for a different kind of task: automatically changing screen content when something happens in a connected business system, such as Salesforce or HubSpot. Setting up those event-driven integrations isn't currently part of the general MCP toolset.

Fugo uses OAuth authentication to establish the connection. You sign in through Fugo, rather than giving Claude your Fugo password.

Requests operate within your authenticated Fugo account and are subject to tenant boundaries, Space access, and checks for restricted operations. For example, changing Space configurations requires administrator authorization.

It's also important to understand that this is a connection capable of making real changes, including publishing content and deleting certain resources. The MCP tools identify read-only and potentially destructive operations, but confirmation behavior depends on the assistant and the action. You should review proposed changes carefully, especially when they affect live screens.

Fugo uses a shared MCP authorization scope rather than separate read-only and write-only connection permissions.

You can disconnect Fugo at any time from Claude's connector settings.

See the Fugo MCP overview for more detail.

No. Claude works with your Fugo account, so the integration doesn't require a particular TV, operating system or media player.

You can use your existing Fugo deployment, whether you're running compatible Windows PCs, ChromeOS devices, Android players, BrightSign devices or commercial displays with Samsung Tizen or LG webOS.

If you're building a new screen network, browse Fugo's supported digital signage hardware.

Claude isn't the only option. Fugo's MCP server is designed to work with compatible AI assistants.

See the Fugo MCP overview for more information about compatible assistants.

You can add Fugo from Claude's Connector Directory, or add it as a custom connector in Claude's settings using this server address:

https://api.fugo.ai/mcp

Claude will open a Fugo sign-in window to authorize the connection. Once it's connected and enabled in your conversation, you can start asking Claude about your screens or giving it tasks.

You'll need a Fugo account and a Claude plan that supports custom connectors. There's no separate Fugo API key to generate.

Our Claude MCP Connector Guide walks through setup for Claude.ai, Claude Desktop and Claude Code, with example prompts to get you started.