LabscoMCP early access ↗
MCP SERVER

Red Bee MCP Server

65 tools over Red Bee Media's Exposure API — catalog search, EPG, entitlements, profiles and purchases.

by TamsiERP & Vertical Business SystemsCommunity

LABSCO SUMMARY

Operator-side breadth, not a viewer's remote control.

The catalog and EPG tools are what most people will reach for, but the list keeps going into account creation, payment methods and subscription cancellation — this is the whole Exposure surface, not a curated slice. That makes it strong for building or debugging an OTT integration, and worth scoping carefully before you point it at production, since the same session that searches for a film can also cancel a subscription.

What it is

A broad client for the Red Bee Media OTT platform, aligned tool-for-tool with the Exposure API. It covers the whole customer-facing surface of a streaming service: authenticating a viewer, searching the catalog, reading the EPG, resolving playback entitlements, managing profiles and preferences, and going through purchases and payment methods. It can run for a local assistant over stdio or as an HTTP/SSE service for a web app — or both at once.

What you get

  • search_content_v2 runs free-text search including descriptions; search_assets_autocomplete and search_multi_v3 cover title autocomplete and prefix search across assets and tags
  • get_asset_details, get_seasons_for_series, get_episodes_for_season and get_next_episode walk a series
  • get_epg_for_channel and get_epg_all_channels read the guide; get_active_channels and get_channel_onnow report what is live
  • get_playback_info resolves the play entitlement for an asset and entitle_asset grants it
  • login_user, create_anonymous_session, validate_session_token and logout_user handle sessions
  • get_watch_next, get_user_recommendations and get_continue_watching build the discovery rails
  • get_user_profiles, add_user_profile, set_user_preferences and add_asset_to_list manage profiles, preferences and watchlists
  • get_offerings, purchase_product_offering, get_active_purchases and add_payment_method cover the commerce path

Requirements

REDBEE_CUSTOMER and REDBEE_BUSINESS_UNIT are required — they identify which operator's platform you are talking to. Run it with uvx redbee-mcp --stdio or pip install redbee-mcp (package redbee-mcp, version 1.5.0); --http starts a JSON-RPC endpoint on port 8000 with an /sse stream and a /health check, and --both runs both transports together. Viewer credentials are optional: REDBEE_USERNAME and REDBEE_PASSWORD, or an existing REDBEE_SESSION_TOKEN. Public catalog reads work from an anonymous session.

Setup effort

One command plus credentials — pip install redbee-mcp, then supply credentials