VLC MCP Server

Created By
piebroa year ago
An MCP (Model Context Protocol) Server to play and control movies using VLC.
Overview

what is VLC MCP Server?

VLC MCP Server is a Model Context Protocol (MCP) server that allows users to play and control movies using VLC media player. It is designed to work with a Raspberry Pi setup for seamless video playback.

how to use VLC MCP Server?

To use the VLC MCP Server, install VLC and start the HTTP server with the command: vlc --extraintf=http --http-host=localhost --http-port=8080 --http-password=your_password. Additionally, install mediainfo for subtitle support and configure the server using the provided JSON configuration.

key features of VLC MCP Server?

  • Control movie playback through an MCP interface.
  • Integration with the Anthropic API for video summarization.
  • Support for subtitles using mediainfo.

use cases of VLC MCP Server?

  1. Playing movies on a Raspberry Pi connected to a projector.
  2. Automating video playback in a home theater setup.
  3. Summarizing video content for quick reviews.

FAQ from VLC MCP Server?

  • What is the purpose of the Anthropic API key?

The API key is used to summarize existing videos in your video folder.

  • Can I use VLC MCP Server on Windows or Mac?

While the server is primarily designed for Linux, you may need to disable subtitles or find alternatives for Windows and Mac users.

  • Is there a license for this project?

Yes, the project is licensed under the MIT License.

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

Recommend Servers

View All
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