Table of contents

Fugo runs an MCP (Model Context Protocol) server - an open standard for safely connecting AI assistants to external tools and data. Connecting it lets you manage your Fugo account through natural-language conversation with a supported AI assistant instead of clicking through the CMS: ask what's playing on a screen, upload new media, publish a playlist, or fire a trigger during a live event, all from a chat.

The connector only ever sees and changes what your own Fugo account already has access to - it doesn't grant any assistant broader access than your Fugo user role already allows.

This article covers what the connector is, what it can do, and how permissions and security work. Setup steps, example prompts, and troubleshooting are specific to each AI assistant Fugo supports - see Available connectors below for the assistant-specific guide.

Fugo also has its own built-in AI chat sidebar inside the CMS, called Ask Fugo.

That's a separate feature from the MCP connector described in this article: Ask Fugo lives inside Fugo itself and answers questions or takes action without ever leaving the CMS, while the MCP connector described here is for controlling your Fugo account from a separate, external AI assistant application.

If you're looking for the in-CMS assistant, this isn't the right article.

There's currently no dedicated page inside Fugo for managing this connection - you won't find a list of connected assistants or a revoke button inside the Fugo CMS itself.

The connection is set up and managed entirely from your AI assistant's own connector settings (see the assistant-specific guides linked under Available connectors below), including disconnecting it: remove Fugo from your assistant's connector list to end access immediately.

The connector currently exposes the following areas of your Fugo account. This holds true no matter which supported AI assistant you connect it to.

List every screen in a Space, look up a specific screen's details, or check a screen's configured properties (like region or store format) - handy for auditing your screen inventory or targeting content precisely, without opening the Screens page yourself.

List or look up existing content items and TV Dashboards in your account - useful for finding something to reuse in a new playlist, or for checking what's already been built before creating something new.

Upload new media into your library from a URL, as an attached file, or as raw bytes - your assistant can store it in a folder you specify.

You can also ask it to update an existing media item with a new version; every playlist already using that media picks up the change automatically, the same as updating it in the CMS.

You can also browse your existing media library and folders.

List your existing playlists and manual triggers, or create a new playlist - choosing the screens (by name, Space, or a property like region), the content to play, and the schedule.

You can also unpublish or delete a playlist, and create a new manual trigger for events, announcements, or emergencies you'll want to fire later.

A one-step shortcut for getting content live fast: describe a mix of content in one request - links, web pages, slides made of text or images, existing media, or existing content items - and your assistant will upload, build, publish, and fire it to your chosen screens in a single action.

A matching "stop" action reverts the screen back to its regular schedule when you're done.

List the Spaces and people in your workspace, and - for users with the right permissions - create, rename, or delete a Space.

Because deleting a Space is a destructive, hard-to-reverse action, your assistant will always confirm with you before carrying it out (see Permissions and security below).

The connector doesn't have its own separate permission system - it acts with exactly the same role and permissions your Fugo user account already has. If your role can't edit a particular Space in the CMS, your assistant can't edit it either through the connector.

Fugo marks every action that creates, changes, or deletes something (like updating media, deleting a playlist, or deleting a Space) so your assistant knows it's a meaningful change.

Most assistants use that signal to pause and ask you to confirm before actually making the change - so review what's about to happen before you approve it.

Setup requires a one-time secure sign-in with your Fugo credentials in a browser window - your Fugo password itself is never shared with your AI assistant's provider.

You can end the connection at any time from your assistant's own connector settings; there's no separate step needed inside Fugo (see Managing the connection above).

Fugo's MCP connector is built to work with any MCP-compatible AI assistant. Each supported assistant has its own setup guide, since the exact steps (and things like example prompts and troubleshooting) differ slightly from one assistant to the next:

As Fugo adds support for more AI assistants, their guides will be linked here too.

Any MCP-compatible client can connect today, even without a dedicated guide above. In your tool's connector or MCP settings, add a remote (HTTP) MCP server with this URL:

https://api.fugo.ai/mcp

then complete the one-time "Sign in to Fugo" browser step. To confirm it's working, ask it: "Which of my Fugo screens are online right now?"

Run into something that isn't covered here? Reach out via the support chat inside the Fugo CMS, or email us at support@fugo.ai.

Don't have a Fugo account yet? Start a free trial.