Shaka Packager MCP Server

Created By
coderjuna year ago
Experimenting with MCP
Overview

What is Shaka Packager MCP Server?

Shaka Packager MCP Server is an experimental server that integrates Shaka Packager with Claude AI applications for video transcoding, packaging, and analysis.

How to use Shaka Packager MCP Server?

To use the server, set up both the Filesystem MCP Server and the Shaka Packager MCP Server, configure them in Claude Desktop, and use commands to analyze or process video files.

Key features of Shaka Packager MCP Server?

  • Video analysis to extract stream information and codecs.
  • Media packaging for HLS and DASH formats.
  • Advanced options like DRM encryption and ad insertion.
  • Intelligent path handling between Docker and host environments.
  • Robust error management with suggestions.
  • Command assistance for Shaka Packager commands.
  • Interactive documentation and detailed outputs.

Use cases of Shaka Packager MCP Server?

  1. Analyzing video files for detailed stream information.
  2. Packaging videos for streaming in various formats.
  3. Integrating with Claude Desktop for enhanced media processing tasks.

FAQ from Shaka Packager MCP Server?

  • Is this project stable?

No, it is in an alpha stage and is highly experimental, not recommended for production use.

  • What are the prerequisites?

Python 3.10 or higher and Shaka Packager installed.

  • How can I report issues?

Please report any issues on the project's GitHub page.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
coderjun
Star
1
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago