# Qencode MCP Server Qencode MCP Server connects MCP-capable AI clients to Qencode’s video processing and media storage workflows. Developers and content teams can describe transcoding, analysis, delivery, and storage tasks in natural language and run them through Qencode. - Findings24: - Site: - Preços: Freemium - Categorias: API de vídeo com IA, Ferramentas MCP ## O que é Qencode MCP Server? Qencode MCP Server is a hosted Model Context Protocol interface for Qencode. It connects MCP-capable AI clients with Qencode’s transcoding API, encoding knowledge base, and media storage workflows, allowing developers and content teams to request video operations in plain language and run the resulting jobs from their AI client. The server covers video conversion, adaptive streaming, audio extraction, thumbnails, subtitles, speech-to-text, translation, video analysis, editing, delivery protection, and storage operations. It is accessed through `https://mcp.qencode.com/mcp` and authenticates with a Qencode API key managed per Project. ## O que Qencode MCP Server pode fazer? ### Natural-language video processing Compose transcoding and media-processing jobs from plain-language instructions, including MP4 or WebM conversion, audio extraction, HLS or DASH ladders, trimming, stitching, rotation, and deinterlacing. ### Media analysis and AI operations Request video intelligence, source metadata inspection, speech-to-text, subtitle translation into up to 15 languages, AI-generated-content checks, VMAF scoring, and audio waveform generation. ### Images, subtitles, and presentation assets Create poster frames, interval-based thumbnails, sprite sheets, and animated GIFs; add or remove subtitle tracks; and apply logo or watermark overlays. ### Streaming delivery and protection Configure adaptive bitrate outputs, per-title encoding, incremental ABR updates, AV1 encoding, AES-128 encryption, and DRM packaging through the documented providers and systems. ### Job tracking and result playback Check job status and completion information, retrieve output URLs and rendition details, view warnings or errors, list jobs started in the current chat, and play finished outputs in an inline Qencode player. ### Knowledge base and media storage access Search and read Qencode documentation from the client, list and browse buckets, create buckets, stage inputs from public URLs, generate time-limited download links, and hand off files with download links. ## Casos de uso ### Prepare a video for web delivery Ask the client to convert a source into MP4 or WebM, or create an HLS or DASH ladder with specified renditions. This suits teams preparing browser, mobile, or CDN playback assets without manually assembling the encoding request. ### Create localized and accessible versions Transcribe an interview, translate subtitles into selected languages, or mux existing SRT files as selectable tracks. The workflow is useful for producing multilingual or captioned versions from one source. ### Review and organize a media library Inspect source resolution, duration, and codecs; create thumbnails or sprite sheets; browse Qencode Media Storage; stage a public input file; and generate a temporary download link for a stored output. ### Run protected or quality-controlled delivery jobs Request AV1 or per-title encoding, compare an encoded version with its source using VMAF, or package HLS with AES-128 or supported DRM. This combines delivery preparation with specific quality or protection requirements. ## Perguntas frequentes ### What is required to use Qencode MCP Server? You need an MCP-capable client, a Qencode account, and a Qencode API key. Keys are generated and managed per Project in the Qencode account. ### Which clients can connect to the server? The documentation lists Claude, Claude Code, Cursor, ChatGPT, Gemini, Grok, and Lovable. Claude and Cursor are shown with one-click connector support; the other listed clients can connect using their remote MCP-server configuration. ### Does the server require local software installation? No additional software or local installation is required beyond an MCP-compatible client. The hosted endpoint is \`https://mcp.qencode.com/mcp\`. ### Where are outputs stored if no destination is specified? They are saved to temporary storage and removed approximately 24 hours after the job completes. Specify a permanent storage destination when the files need to be retained. ### How should job completion be checked? Use the job’s \`status\` field as the primary completion indicator. Output arrays can be empty while a job is queued or processing. If \`wait\_for\_job\` returns before a terminal state, the documentation advises one follow-up check with \`get\_job\_status\` using the same task token. ### How are MCP-started transcoding jobs billed? Transcoding minutes started through the MCP server are billed against the Qencode plan in the same way as jobs started through the Qencode API or dashboard. The supplied documentation does not specify prices or plan limits. ## Informações rápidas - **Category**: Hosted Model Context Protocol server for video processing - **Endpoint**: https://mcp.qencode.com/mcp - **Primary users**: Developers and content teams - **Authentication**: Qencode API key managed per Project - **Supported clients**: Claude, Claude Code, Cursor, ChatGPT, Gemini, Grok, and Lovable - **Billing**: Transcoding minutes count against the Qencode plan