MCP Media Processing Server

Created By
maoxiaokea year ago
A Node.js server implementing Model Context Protocol (MCP) for media processing operations, providing powerful video and image manipulation capabilities.
Overview

What is MCP Media Processing Server?

MCP Media Processing Server is a Node.js server that implements the Model Context Protocol (MCP) for media processing operations, offering powerful capabilities for video and image manipulation.

How to use MCP Media Processing Server?

To use the server, ensure you have FFmpeg and ImageMagick installed, then configure your claude_desktop_config.json to include the media processor command. You can run it using NPX with the command: npx mcp-media-processor@latest.

Key features of MCP Media Processing Server?

  • Video processing and conversion
  • Image processing and manipulation
  • Media compression
  • Video trimming and editing
  • Image effects and watermarking

Use cases of MCP Media Processing Server?

  1. Converting video files to different formats.
  2. Compressing images for web use.
  3. Adding watermarks to images for branding.
  4. Trimming video clips for social media.
  5. Applying effects to images for creative projects.

FAQ from MCP Media Processing Server?

  • What dependencies are required to run the server?

You need to install FFmpeg and ImageMagick on your system.

  • Is there a specific command to start the server?

Yes, you can start it using the command: npx mcp-media-processor@latest.

  • Can I use this server for both video and image processing?

Yes, the server supports a wide range of operations for both video and image files.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
maoxiaoke
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago