Skip to content
MCP-Bridge
Cloud InfrastructureAuto-generatedScore: 34

Azure Media Services MCP Server

The Azure Media Services Streaming Locator and Policy Management API, provided by Microsoft as part of the Azure cloud platform, is a sophisticated set of RESTful endpoints designed for programmatic control over the delivery configuration of streaming media content.

Quick Start Summary

The Azure Media Services MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Azure Media Services API through natural language. It exposes 10 API endpoints as callable tools, such as List Streaming Locators, Get a Streaming Locator, Create a Streaming Locator, and more. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/azure-com-mediaservices-streamingpoliciesandstreaminglocators. This integration is sourced from the auto Azure Media Services OpenAPI specification (v2018-03-30-preview) and has a quality score of 34/99 (fair documentation coverage).

10Endpointstools mapped
NoneAuthopen access
34/99Qualityfair
~30 secSetupno auth
View Hosted Config URLClaude Desktop Setup Guide

Server Details

Category
Cloud Infrastructure
Authentication
None
Endpoints
10 operations
Transport
STDIO
Spec Version
v2018-03-30-preview
Install Command
npx -y @mcp/azure-com-mediaservices-streamingpoliciesandstreaminglocators

Environment Variables

AZURE_MEDIA_SERVICES_API_KEY

Example: your_azure_media_services_api_key

Top Endpoints

GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/streamingLocators

List Streaming Locators

GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/streamingLocators/{streamingLocatorName}

Get a Streaming Locator

PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/streamingLocators/{streamingLocatorName}

Create a Streaming Locator

DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/streamingLocators/{streamingLocatorName}

Delete a Streaming Locator

POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/streamingLocators/{streamingLocatorName}/listContentKeys

List Content Keys

Own this API?

Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.

Option 1: Free Verification

Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.

  • • Verified badge on page
  • • Standard search sorting
  • • 2-3 business days review
Start Free Claim →
Instant & Boosted

Option 2: Featured Upgrade($9/mo)

Instant verification plus premium styling, featured badges, and directory placement boost.

  • • ★ Featured star & amber highlight border
  • • Top of directory search placement
  • • Instant activation via claim token

📖 Detailed MCP Integration Guide

A technical breakdown of capabilities, agent workflows, and security/configuration best practices.

⚡Capabilities & Use Cases
The Azure Media Services Streaming Locator and Policy Management API, provided by Microsoft as part of the Azure cloud platform, is a sophisticated set of RESTful endpoints designed for programmatic control over the delivery configuration of streaming media content. Its core capabilities encompass the complete lifecycle management of streaming locators and streaming policies within a specified Azure Media Services account. Streaming locators serve as the logical identifiers that define the URL paths and content access conditions for delivering encoded media assets to end-users, effectively mapping content to its delivery endpoint. Streaming policies, conversely, define the security and DRM (Digital Rights Management) encryption schemes applied to the content streams, such as ClearKey, Widevine, or PlayReady. The API enables developers to dynamically create, update, retrieve, and delete these critical resources, as well as to perform operational queries like listing the available content keys for a given locator or resolving the direct streaming paths for content. Typical enterprise use cases include large-scale video-on-demand (VOD) platforms managing vast content libraries, live event broadcasters requiring secure, low-latency stream configuration, and educational institutions delivering protected course materials. This API is fundamental for DevOps and media engineering teams automating the infrastructure-as-code for video delivery pipelines.
🤖AI Agent Value
When this API is exposed as a set of tools to an AI coding assistant via the Model Context Protocol (MCP), it transforms the assistant from a static code generator into a dynamic, context-aware media operations agent. The value lies in bridging the gap between high-level architectural intent and the low-level, intricate configuration of cloud media resources. An AI assistant armed with these MCP tools can directly interact with the live Azure environment, enabling it to understand the current state of a media account, validate proposed changes against existing resources, and execute complex multi-step operations with precision. This allows developers to delegate intricate, error-prone tasks—such as orchestrating the creation of a secure streaming policy linked to a specific content key and then generating a locator for a new asset—through natural language instructions. The assistant can serve as a real-time auditor, querying configurations to ensure compliance with security policies or diagnosing delivery issues by inspecting locator settings, thereby accelerating development cycles and reducing the cognitive load associated with managing distributed media infrastructure.
💬Example Workflows
A developer leveraging this MCP server can issue a variety of dynamic task instructions to the AI agent. For instance, upon ingesting a new video asset, the developer could instruct the agent to "create a new streaming policy named 'Secure-OnDemand-2024' configured for Widevine and Common Encryption, then generate a new streaming locator for asset ID 'video-123' using this policy and return the HLS and DASH manifest URLs for testing." For content maintenance or security updates, a command like "audit all streaming locators for the 'premium-content' container, list any that are using the deprecated 'ClearKeyOnly' policy, and propose a plan to update them to the new 'MultiDRM-Policy'" becomes actionable. The AI can also be tasked with cleanup operations, such as "find and delete all streaming locators that were created more than 90 days ago and are no longer associated with any active asset tags." These workflows illustrate how the AI agent transitions from a code helper to an active participant in operational media management, automating configuration, auditing, and lifecycle tasks that are critical to maintaining a scalable and secure content delivery network.
🛡️Security & Auth
Critical authentication requirements and security best practices must be rigorously followed when configuring this server for MCP integration. Although the Swagger specification may indicate no authentication, in practice, every API call to Azure Resource Manager endpoints requires a valid Azure Active Directory (Azure AD) OAuth 2.0 bearer token. The developer must register an application in Azure AD, grant it the appropriate permissions (typically the "Contributor" or a more granular custom role on the Media Services account), and configure the MCP server to securely handle and inject this token into the Authorization header of each request. The principle of least privilege is paramount; the service principal used by the AI assistant should be scoped to only the specific Media Services account(s) it needs to manage, and its role should be limited to the exact operations required—avoiding over-provisioning with broad roles like "Owner." All secrets, such as client secrets or certificate credentials, must be stored securely in a vault like Azure Key Vault, never in code or configuration files. Furthermore, enabling Azure Resource Locks on critical media accounts and implementing audit logging via Azure Monitor can provide an essential safety net against unintended deletions or modifications initiated by automated agents.

Similar APIs

Other APIs in the Cloud Infrastructure category.

Supabase API

Manage Supabase projects, databases, authentication, and storage through your AI agent.

API Key

Cloudflare API

Manage Cloudflare DNS, CDN, Workers, and security settings through your AI agent.

API Key

Vercel API

Deploy projects, manage domains, and monitor deployments through your AI agent.

Bearer Token

DigitalOcean API

The DigitalOcean API is a comprehensive, RESTful interface provided by DigitalOcean, a leading cloud infrastructure provider focused on simplifying cloud computing for developers, startups, and enterprises. It serves as the programmatic backbone for managing the entire DigitalOcean ecosystem, enabling users to provision, configure, and control cloud resources such as Droplets (virtual private servers), Kubernetes clusters, managed databases, networks, storage volumes, and application platforms. Core capabilities include full lifecycle management of these resources, from creation and scaling to monitoring and deletion, mirroring the functionality available in the DigitalOcean control panel. Its primary use cases range from automating infrastructure setup for CI/CD pipelines and enabling infrastructure-as-code practices to supporting dynamic application scaling and resource optimization for SaaS products, e-commerce sites, and development environments. The API is designed for both developers seeking to automate their cloud operations and businesses that require programmable, scalable cloud infrastructure without the complexity of larger hyperscale providers.

Related MCP Server Integrations

Supabase API MCP Setup

Manage Supabase projects, databases, authentication, and storage through your AI agent.

Cloud InfrastructureConfigure →

Cloudflare API MCP Setup

Manage Cloudflare DNS, CDN, Workers, and security settings through your AI agent.

Cloud InfrastructureConfigure →

Vercel API MCP Setup

Deploy projects, manage domains, and monitor deployments through your AI agent.

Cloud InfrastructureConfigure →

DigitalOcean API MCP Setup

The DigitalOcean API is a comprehensive, RESTful interface provided by DigitalOcean, a leading cloud infrastructure provider focused on simplifying cloud computing for developers, startups, and enterprises. It serves as the programmatic backbone for managing the entire DigitalOcean ecosystem, enabling users to provision, configure, and control cloud resources such as Droplets (virtual private servers), Kubernetes clusters, managed databases, networks, storage volumes, and application platforms. Core capabilities include full lifecycle management of these resources, from creation and scaling to monitoring and deletion, mirroring the functionality available in the DigitalOcean control panel. Its primary use cases range from automating infrastructure setup for CI/CD pipelines and enabling infrastructure-as-code practices to supporting dynamic application scaling and resource optimization for SaaS products, e-commerce sites, and development environments. The API is designed for both developers seeking to automate their cloud operations and businesses that require programmable, scalable cloud infrastructure without the complexity of larger hyperscale providers.

Cloud InfrastructureConfigure →

Access Analyzer MCP Setup

The AWS Identity and Access Management Access Analyzer API provides a powerful, policy-as-code service that automatically identifies resources accessible from outside your AWS account or organization. At its core, the service continuously evaluates resource-based policies—such as Amazon S3 bucket policies, AWS Identity and Access Management (IAM) roles, Amazon KMS key policies, and AWS Lambda function policies—using logic-based reasoning to determine which resources grant access to unknown external principals. Its primary use case is for security and compliance teams within enterprises to proactively detect unintended data exposure, enforce least privilege principles, and audit cross-account and cross-service access. The API endpoints allow programmatic control to create, configure, and query analyzers, manage archive rules for storing findings, and generate custom policy documents, making it a foundational tool for automating cloud security posture management at scale.

Cloud InfrastructureConfigure →