Video Content Summarization MCP Server

Created By
fakada year ago
A Model Context Protocol (MCP) server that extracts content from multiple video platforms (Douyin, Bilibili, Xiaohongshu, Zhihu) and generates intelligent knowledge graphs with OCR support.
Overview

what is Video Content Summarization MCP Server?

Video Content Summarization MCP Server is a Model Context Protocol (MCP) server designed to extract content from various video platforms and generate intelligent knowledge graphs with OCR support.

how to use Video Content Summarization MCP Server?

To use the server, clone the repository, set up the environment, and run the server. You can process videos by providing URLs from supported platforms like Douyin, Bilibili, Xiaohongshu, and Zhihu.

key features of Video Content Summarization MCP Server?

  • Multi-platform support for video content extraction
  • OCR text recognition for image text extraction
  • Knowledge graph generation for structured content analysis
  • Context-aware extraction for improved content understanding

use cases of Video Content Summarization MCP Server?

  1. Extracting and summarizing content from social media videos.
  2. Generating knowledge graphs for educational or research purposes.
  3. Enhancing video content accessibility through text extraction.

FAQ from Video Content Summarization MCP Server?

  • What platforms does the server support?

The server supports Douyin, Bilibili, Xiaohongshu, and Zhihu.

  • Is OCR supported?

Yes, the server includes OCR capabilities for text extraction from images.

  • How do I install the server?

Follow the installation instructions in the repository, including setting up a Python environment and installing dependencies.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fakad
Star
1
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
Crevio

2 days ago