Skip to main content
Glama

🎬 Encoding DevOps MCP Server: AI-Powered Video Encoding Assistant

GitHub stars GitHub contributors GitHub last commit open issues Python Version PRs Welcome

Ever been woken up at 3 AM by a failed encoding job? Say goodbye to those late-night troubleshooting sessions! This Model Context Protocol (MCP) server connects Anthropic's Claude directly to your encoding workflow, making video encoding issues a breeze to handle.

✨ What's Cool About This?

  • Smart Error Translation: Turns cryptic "moov atom not found" messages into plain English

  • Real-time Analysis: Connects directly to your encoding workflow and database

  • Human-Friendly Responses: Generates clear, actionable solutions for your team

  • Auto-Email Draft: Creates professional client communications with context

  • Always On Guard: Monitors your encoding jobs 24/7

  • Keeps You in Control: Suggests actions but lets you make the final call

Related MCP server: envious-canvas

🚀 Getting Started

You'll Need

  • Python 3.11 or higher

  • Claude Desktop

  • Your encoding workflow API credentials

  • OMDB API key (optional, for movie metadata)

Quick Setup

  1. Install the package using UV:

curl -LsSf https://astral.sh/uv/install.sh | sh
uv pip install encoding-devops
  1. Set up your environment:

# Copy the example config
cp .env.example .env

# Add your API keys
nano .env
  1. Register with Claude Desktop:

uv run mcp install ./src/encoding_devops/main.py

💡 How to Use It

# Start the MCP server
uv run mcp dev ./src/encoding_devops/main.py

# In Claude Desktop, you can now ask things like:
"What's wrong with job XYZ-123?"
"Draft an email about the failed encoding job"
"Check the encoding cluster status"

🔧 Under the Hood

The MCP server uses three main components to help you:

  1. Resources: Email templates, error guides, and documentation

  2. Tools: Job status checks, log analysis, and email drafting

  3. Prompts: Instructions that help Claude understand encoding issues

🤝 Want to Help?

We'd love your input! Here's how you can contribute:

  1. Fork it

  2. Create your feature branch (git checkout -b feature/awesome-feature)

  3. Commit your changes (git commit -m 'Add awesome feature')

  4. Push to the branch (git push origin feature/awesome-feature)

  5. Open a Pull Request

📋 Coming Soon

  • Integration with more encoding workflow systems

  • Advanced log analysis patterns

  • Automated health checks

  • Slack notifications

  • Custom email templates

📝 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙌 Thanks To

  • Anthropic team for the MCP framework

  • All our contributors

  • The DevOps community for feedback and suggestions


💤 Built by a developer who wanted to sleep through the night. If this helps you too, give us a star!

Read the full story behind this project in my Medium article about using MCP to handle encoding fires.

Available Tools

8 tools
get_clientsB

Get list of all clients

Inputs: no named parameters.

get_job_by_nameC

Get details of an encoding job by its name

Inputs: name (required).

get_job_tasks_by_idC

Get tasks for a specific job by its ID

Inputs: job_id (required).

get_latest_jobsB
Get the most recent encoding jobs

Args:
    limit: Number of jobs to return (default: 3, max: 10)

Returns:
    String representation of the latest jobs

Inputs: limit (required).

get_movie_detailsB
Get detailed information about a movie by its IMDB ID

Args:
    imdb_id: IMDB ID of the movie (e.g., 'tt0111161')

Returns:
    String representation of the movie details

Inputs: imdb_id (required).

is_cluster_busyB

Check if the encoding cluster is busy (has jobs in progress)

Inputs: no named parameters.

open_emailA
Opens the default email client with your message ready to go

Args:
    body: What you want to say in the email
    to: Who to send it to (optional)
    subject: Email subject line (optional)
    cc: CC recipients (optional)
    bcc: BCC recipients (optional)
    ctx: MCP context

Returns:
    str: Quick status message so you know it worked

Inputs: body (required), cc, to, bcc, +1 more.

search_movieC
Search for a movie by title

Args:
    title: Movie title to search for

Returns:
    String representation of the search results

Inputs: title (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target clear, distinct resources (clients, cluster status, movie search, email). The three job-related tools (get_job_by_name, get_job_tasks_by_id, get_latest_jobs) share a resource but differ in intent, so only minor confusion is possible.

    Naming Consistency4/5

    Names follow a consistent snake_case verb_noun pattern (get_job_by_name, get_movie_details, search_movie). The is_cluster_busy predicate is a reasonable deviation for a boolean check rather than a true inconsistency.

    Tool Count5/5

    Eight tools is well-scoped for this domain, with each covering a distinct query. No redundant or filler tools pad the surface.

    Completeness3/5

    The surface is read-only: it exposes job lookups, cluster status, and movie info but no submit/create/cancel/retry job operations, which are core to an encoding-ops workflow. Client and email handling are present but job lifecycle coverage is one-sided.

    Related MCP Connectors

    Related MCP Servers