Amazon Kinesis Video Streams Media MCP Configuration
The Amazon Kinesis Video Streams Media MCP configuration provides a hosted JSON schema that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Amazon Kinesis Video Streams Media API via the Model Context Protocol. This configuration maps 1 API endpoints as callable tools, including GetMedia. No authentication credentials are needed — it works out of the box. The configuration is auto-generated from the Amazon Kinesis Video Streams Media OpenAPI specification (v2017-09-30) and has a quality score of 40/99 (fair documentation coverage). Use the hosted URL below to auto-load this schema into any compatible MCP client.
Quick Specs Reference
Hosted Config URL
Use this hosted URL in any client that supports remote MCP schema auto-loading.
https://mcpbridge.org/config/amazonaws-com-kinesis-video-media.jsonOne-Click Client Setup
Copy the configurations below to wire your local coding assistant directly.
Claude Desktop
claude_desktop_config.json{
"mcpServers": {
"amazonaws-com-kinesis-video-media": {
"command": "npx",
"args": [
"-y",
"@mcp/amazonaws-com-kinesis-video-media"
],
"env": {
"AMAZON_KINESIS_VIDEO_STREAMS_MEDIA_API_KEY": "your_amazon_kinesis_video_streams_media_api_key"
}
}
}
}Cursor & VS Code
MCP Server URL Setup{
"mcpServers": {
"amazonaws-com-kinesis-video-media": {
"url": "https://mcpbridge.org/config/amazonaws-com-kinesis-video-media.json"
}
}
}Raw Configuration JSON
For local command line wrappers or dynamic shell bindings.
{
"mcpServers": {
"amazonaws-com-kinesis-video-media": {
"command": "npx",
"args": ["-y","@mcp/amazonaws-com-kinesis-video-media"],
"env": {
"AMAZON_KINESIS_VIDEO_STREAMS_MEDIA_API_KEY": "your_amazon_kinesis_video_streams_media_api_key"
}
}
}
}Required Environment Keys
Substitute these secrets inside your configuration directory environment definitions.
AMAZON_KINESIS_VIDEO_STREAMS_MEDIA_API_KEYyour_amazon_kinesis_video_streams_media_api_key with your secret key credentialMapped Web APIs & Tools
The following routes will be exposed directly as protocol tools for the LLM.
/getMediaGetMedia
Similar Configurations
Figma API
Access Figma files, components, and styles for design-to-code workflows in your AI development environment.
https://mcpbridge.org/config/figma.jsonEC2 Image Builder
EC2 Image Builder is a fully managed service provided by Amazon Web Services (AWS) that fundamentally streamlines the creation, maintenance, and distribution of secure, consistent, and production-ready server images, often referred to as "golden images." At its core, the service eliminates the manual, error-prone, and time-consuming processes traditionally associated with image management by providing a declarative, pipeline-based approach. Users define image recipes—specifying a source image, components (containing installation scripts, configuration steps, and tests), and infrastructure settings—and the service orchestrates the entire build process on AWS infrastructure. This includes launching temporary instances, applying customizations, running security and compliance validations, and finally, creating the image or container. The primary use cases span from enterprise IT teams standardizing hundreds of golden images for diverse workloads across global regions, to DevOps engineers rapidly provisioning secure, compliant base images for containerized microservices or scalable compute fleets, ensuring every deployment starts from a known, auditable, and up-to-date foundation. Exposing the EC2 Image Builder API as tools via the Model Context Protocol (MCP) to an AI coding assistant unlocks significant operational acceleration and introduces a new paradigm of infrastructure-as-code authoring and management. An AI agent, such as Claude or others integrated into IDEs like Cursor, gains the ability to directly interact with and manipulate complex image pipelines through natural language instructions. This transforms the developer's workflow from manually writing extensive JSON or YAML configuration files and navigating the AWS Management Console to engaging in a conversational, intent-driven process. The value lies in the AI's capacity to understand high-level goals ("Create a new pipeline for a hardened Ubuntu 22.04 image with our custom security scanning component") and map them to the precise sequence of API calls required, handling parameters, dependencies, and error states. This acts as a force multiplier, reducing cognitive load, accelerating prototyping, and ensuring consistency by programmatically applying best practices. A developer could instruct the AI agent to perform a wide array of dynamic tasks to manage the image lifecycle. For instance, they could say, "Audit our existing image pipelines and list any that are using a component version older than six months," prompting the AI to use discovery and querying tools to generate a report. More complex orchestration becomes possible with commands like, "Update the distribution configuration for our 'Finance-Prod' pipeline to include a new region, then trigger a fresh image build and notify the security team upon completion." This would chain together an update to an existing configuration, the creation of a new image version via the pipeline, and a final notification action. The AI could also assist in debugging by analyzing build logs or error messages from a failed image creation and suggesting corrective API actions, such as modifying a component's build version or infrastructure settings. While the described API endpoints operate with "None" for direct authentication, it is critical to understand this in the context of the AWS ecosystem. All actual calls to the EC2 Image Builder service are ultimately authenticated and authorized via AWS Identity and Access Management (IAM). Any AI agent or client interacting with these endpoints must be configured with valid AWS security credentials (e.g., an access key and secret key, or an IAM role if running on AWS infrastructure). Adherence to the principle of least privilege is paramount; the IAM policy attached to these credentials should grant only the specific EC2 Image Builder permissions required for the agent's tasks (e.g., ec2imagebuilder:CreateImage, ec2imagebuilder:GetImagePipeline), along with any necessary permissions for interacting with related services like S3 (for component storage), EC2, or IAM roles used in the build. Configuration should involve securely storing AWS credentials outside of source code, using environment variables or dedicated secrets management services, and clearly defining the scope of the MCP server's capabilities to prevent unintended or overly broad actions.
https://mcpbridge.org/config/amazonaws-com-imagebuilder.jsonAmazon Kinesis Video Streams Archived Media
The Amazon Kinesis Video Streams Archived Media API is a specialized service provided by Amazon Web Services (AWS) that enables programmatic access to retrieve and transform archived video and audio streams stored within Kinesis Video Streams. Its core capabilities center on on-demand data extraction, allowing users to pull specific clips, generate adaptive streaming manifests (HLS and DASH), extract individual image frames, and query the underlying fragment metadata of archived streams. This API is fundamental for enterprises that need to analyze historical video footage, such as for security and surveillance retrospectives, media asset management, industrial IoT inspection, and smart city analytics. Typical use cases include forensic investigation where an operator needs a precise clip of an incident, content creators repurposing raw footage from cloud-based cameras, or automated systems pulling frames for machine learning model training and validation. It serves as the critical data plane for unlocking the value of video data stored in the cloud. When exposed as tools via the Model Context Protocol (MCP) to an AI coding assistant, this API transforms from a set of static endpoints into a dynamic, conversational interface for video data manipulation. The value lies in dramatically lowering the barrier to complex video operations, enabling developers to instruct an AI agent in natural language to perform precise, multi-step tasks that would otherwise require deep knowledge of the API specifications, authentication flows, and data formats. The AI assistant can act as an expert bridge, translating high-level requests into the correct sequence of API calls. For instance, a developer could ask the AI to "generate a 5-minute HLS streaming session URL for the last 24 hours of camera footage from 'Warehouse-12' to review a security event," and the AI would handle the required timestamp calculations, endpoint selection, and parameter construction. Practical workflows enabled by this MCP integration are powerful and varied. A developer could instruct an AI agent to "create a Python function that extracts all motion-triggered images from the archived stream 'Drone-07' between 10:00 and 12:00 UTC yesterday and saves them to an S3 bucket." The AI would generate code using the `getImages` endpoint with appropriate fragment selection logic. Another task could be, "Update our monitoring dashboard script to automatically query and display the five most recent 30-second video clips from the 'Public-Square' camera whenever a motion alert is triggered." This involves dynamically using `getClip` and potentially `listFragments` in response to external events. The AI can also assist in debugging by interpreting error messages and suggesting the correct API call or parameter adjustment, effectively becoming a knowledgeable collaborator in the development process. Critical configuration and security practices are paramount when setting up an MCP server for this API. Although the API endpoint itself does not handle authentication, all requests must be signed with valid AWS credentials using Signature Version 4. The developer must provision an IAM user or role with the principle of least privilege, granting only the specific Kinesis Video Streams permissions required (e.g., `kinesisvideo:GetClip`, `kinesisvideo:GetHLSStreamingSessionURL`) and scoped to specific streams via resource ARNs. Best practices include using short-lived temporary credentials via the AWS Security Token Service, encrypting all data in transit and at rest (leveraging the Kinesis Video Streams encryption), and implementing strict API gateway controls or VPC endpoints if the MCP server is deployed within a private network. Comprehensive logging via AWS CloudTrail should be enabled to audit all API calls made through the MCP interface, ensuring traceability and compliance.
https://mcpbridge.org/config/amazonaws-com-kinesis-video-archived-media.jsonAmazon Kinesis Video Signaling Channels
The Amazon Kinesis Video Signaling Channels API, provided by Amazon Web Services (AWS) as an integral component of its Kinesis Video Streams service, acts as a critical infrastructure layer for establishing and managing real-time peer-to-peer connections using the WebRTC protocol. This managed signaling service abstracts the inherent complexity of peer discovery, NAT traversal, and session negotiation. Its core capabilities are exposed through two primary endpoints: POST /v1/get-ice-server-config, which provides developers with a list of ICE (Interactive Connectivity Establishment) servers, including STUN and TURN configurations, essential for establishing connections across restrictive networks; and POST /v1/send-alexa-offer-to-master, which facilitates the transmission of a WebRTC SDP (Session Description Protocol) offer to a designated master node in a master-viewer architecture. Enterprise use cases are vast, ranging from building scalable, low-latency video streaming solutions for security and monitoring systems, enabling real-time audio/video communication in telehealth or remote assistance platforms, and powering interactive live sports or event streaming where direct peer connections are paramount. For consumers, this API underpins the connectivity of smart home devices like video doorbells and baby monitors to companion apps, ensuring reliable, real-time interaction. When exposed as tools to an AI coding assistant via the Model Context Protocol (MCP), this API transforms from a set of static endpoints into a dynamic, programmable interface for AI-driven development and automation. The primary value lies in enabling the AI to act as a real-time infrastructure orchestrator. Instead of a developer manually writing boilerplate code to fetch TURN credentials or construct signaling messages, they can instruct the AI to perform these operations contextually. For instance, the AI can be directed to "Provision a complete WebRTC signaling channel for my new smart camera application," prompting it to generate the necessary client-side code that integrates calls to the get-ice-server-config endpoint, handle the response, and embed the credentials securely. It can dynamically adapt configurations, such as querying the current server config to determine if TURN servers are required based on a simulated network environment, thereby automating network adaptation logic. The AI becomes a knowledgeable partner that understands not just the syntax but the architectural purpose of the signaling service. In practical, developer-led workflows, this MCP integration unlocks significant automation potential. A developer can instruct the AI agent to: "Analyze the peer connection setup in my application and optimize it for mobile networks by querying the current ICE server configuration and generating fallback logic for TURN relay usage if direct connections fail." Another powerful task would be: "Automate the end-to-end connection setup for a new viewer joining a live stream. Have the AI agent obtain the necessary ICE configuration, construct the appropriate WebRTC offer using these credentials, and send it via the send-alexa-offer-to-master endpoint to the stream's master, then handle the response to establish the connection." This elevates the AI from a code generator to a runtime collaborator that can prototype, debug, and verify the entire signaling handshake, dramatically reducing the time to implement complex, real-time communication features. Critical security considerations are paramount, even though the basic description indicates "None" for authentication, which likely refers to the API's own endpoint authentication rather than access to the underlying AWS resource. All calls to Kinesis Video Streams APIs must be authenticated and authorized using AWS credentials and IAM policies, following the principle of least privilege. Developers must ensure the AI assistant is configured with an IAM role or user that has only the specific permissions needed for `kinesisvideo:GetIceServerConfig` and `kinesisvideo:SendAlexaOfferToMaster`, scoped to the specific signaling channel ARN. The use of short-lived, temporary credentials is strongly recommended. Furthermore, API access should be restricted via network controls like Amazon VPC endpoints or IP allow-listing where possible. Any credentials or session tokens obtained via the API must be treated as highly sensitive secrets, never hard-coded in client-side applications, and should be refreshed dynamically by the application as needed. Security best practices mandate that the AI agent itself operates within a secure environment, with its access to AWS credentials tightly controlled and audited.
https://mcpbridge.org/config/amazonaws-com-kinesis-video-signaling.json