That's what MCP changes.
The problem with traditional integrations
Broadcasting and OTT teams spend time switching between tools: the analytics tab, the media library, the ad campaigns module. Each answer requires navigation, filtering, exporting. By the time you have the full picture, the decision moment may have passed.
AI coding assistants and chat tools are already part of many workflows. The missing piece has been a direct, secure bridge between those AI tools and the actual data inside your platform.
MCP (Model Context Protocol) is that bridge.
What is MCP, technically speaking?
MCP is an open protocol — developed by Anthropic and adopted across the AI ecosystem — that allows AI clients to connect to external services through a standardized interface. Instead of copying and pasting data into a chat window, the AI queries your platform directly, in real time, using tools defined by the server.
The protocol runs over standard HTTP + JSON-RPC 2.0, which means any MCP-compatible client can connect without custom code or proprietary adapters.
Mediastream Platform exposes an MCP server at:
https://mcp.platform.mediastre.am
The server implements protocol version 2024-11-05 — the current stable spec — and is compatible with all major MCP clients including Claude (Anthropic), Cursor, Windsurf, Continue, and any tool built on the open MCP SDK.
Step 1 — Generate your token
Go to https://platform.mediastre.am/settings/ai and create a new token.
Description: give it a recognizable name (e.g. "Claude Desktop", "Cursor dev")
Access: select Read (Read+Write is coming soon)
Expiration: set a time limit or leave it with no expiration
Click Create Token and copy the token immediately — it won't be shown again after you leave the page.
⚠️ Treat your token like a password. Anyone with it can query your account resources. If compromised, deactivate it from the same settings page and generate a new one.
🔒 Don't see the MCP Tokens section? This feature may not be enabled on your account yet. Contact support via the chat button in Mediastream Platform and request access.
Step 2 — Configure your MCP client
Authentication uses a standard Bearer token header:
Authorization: Bearer YOUR_TOKEN_HERE
Claude (Desktop or claude.ai)
Add the following to your Claude MCP settings:
{
"mcpServers": {
"mediastream": {
"url": "https://mcp.platform.mediastre.am",
"headers": {
"Authorization": "Bearer YOUR_TOKEN_HERE"
}
}
}
}
Cursor
Create or edit .cursor/mcp.json at the root of your project:
{
"mcpServers": {
"mediastream": {
"url": "https://mcp.platform.mediastre.am",
"headers": {
"Authorization": "Bearer YOUR_TOKEN_HERE"
}
}
}
}
Any other MCP-compatible client
The server follows the standard MCP HTTP transport spec. If your client supports remote MCP servers with Bearer token auth, the pattern is the same: server URL + Authorization header. Check your client's documentation for the exact config format.
What you can actually do with it
Once connected, your AI client has access to 9 tools in the current Read tier:
Content & Live
getMediaList— Browse your VOD catalog with filters and pagination. Ask "show me all media published in the last 30 days in the Sports category" and get structured results instantly.getMediaById— Pull the full metadata of a specific media item: title, duration, status, categories, encoding details.getLiveStreamList— List your active and past live streams with filtering options.getLiveStreamById— Get full details on a specific live event, including configuration and status.issueAccessToken— Generate access tokens for protected media or live streams programmatically — useful for automated workflows.
Analytics
getMetricsCatalog— Discover all 200+ available metrics and their supported dimensions before querying. Think of it as asking "what can I measure?" before asking "what are the numbers?"queryAnalytics— The most powerful tool. Query streams, duration, unique users, concurrency, bandwidth, engagement, retention, and session behavior — across dimensions like country, device, content ID, category, and distributor.
Advertising
getAdList— Browse your ad campaigns with filters and pagination.getAdById— Pull the full detail of a specific campaign, including configuration and targeting.
A concrete example
You ask your AI tool: "What were the top 5 most-watched live streams in Brazil last week, and what was the average viewing duration?"
The AI client calls queryAnalytics with the right metric, dimensions (country = Brazil, content_id), filters (date range), and limit — and returns a structured answer ready for a decision or a report.
No exports. No SQL. No switching tabs. Works the same whether you're using Claude, Cursor, or any other MCP-compatible tool.
Access levels and usage
Current tier: Read-only All tokens created today are Read tokens. They allow querying all resources and analytics without any risk of modifying your account — safe to use in shared or exploratory workflows.
Coming soon: Read+Write Read+Write tokens will enable creating and updating resources directly from AI workflows — updating metadata, triggering publishing actions, managing campaigns.
Usage tracking Every MCP request counts toward your plan's usage quota. Request frequency and resource access patterns are tracked in your account analytics. If you reach your limit, requests will be rejected until the quota resets or your plan is upgraded.
Who is this for?
Editorial teams that want to understand content performance without opening analytics every time
Operations teams that monitor live events and need fast answers across streams
Developers building internal tools or automations that combine AI reasoning with Mediastream resources
Product and data teams prototyping AI-assisted workflows on top of real platform data
What's next
The current MCP server covers what teams query most: media, live streams, analytics, and ad campaigns — all in Read mode. As we expand to Write access, it will be possible to update metadata, trigger publishing workflows, and manage campaigns directly from AI clients.
Generate your token at platform.mediastre.am/settings/ai, configure your MCP client, and test with a simple analytics query. If you don't see the MCP Tokens section, contact support via the chat button in Mediastream Platform to request access.