Deepsrt

🚀 DeepSRT MCP Server

A Model Context Protocol (MCP) server that integrates with the DeepSRT API to provide YouTube video summarization capabilities.

🚀 Quick Start

The DeepSRT MCP Server offers seamless integration with the DeepSRT API, enabling users to generate summaries for YouTube videos effortlessly.

✨ Features

• Generate summaries for YouTube videos.
• Support two summarization modes: narrative and bullet points.
• Multi - language support (default: zh - tw).
• Seamlessly integrate with MCP - enabled environments.

🔧 Technical Details

How It Works

1. Content Caching

   • You must first open the video via DeepSRT to ensure that the content is cached in the service.
   • This initial viewing triggers the content caching process in the DeepSRT service.

2. MCP Summary Retrieval

   • When a summary is requested via MCP, the content will be served from the DeepSRT's CDN edge locations.
   • This ensures fast and efficient delivery of the summary.

3. Pre - cached Content

   • Some videos may have been pre - cached in the system due to previous user requests.
   • Although you may be able to obtain summaries for these pre - cached videos, availability is not guaranteed.
   • For the best results, make sure to open the video via DeepSRT first.

%%{init: {'theme': 'dark', 'themeVariables': { 'primaryColor': '#2496ED', 'secondaryColor': '#38B2AC', 'tertiaryColor': '#1F2937', 'mainBkg': '#111827', 'textColor': '#E5E7EB', 'lineColor': '#4B5563', 'noteTextColor': '#E5E7EB'}}}%%
sequenceDiagram
    participant User
    participant DeepSRT
    participant Cache as DeepSRT Cache/CDN
    participant MCP as MCP Client

    Note over User,MCP: Step 1: Initial Caching
    User->>DeepSRT: Open video via DeepSRT
    DeepSRT->>Cache: Process and cache content
    Cache-->>DeepSRT: Confirm cache storage
    DeepSRT-->>User: Display video/content

    Note over User,MCP: Step 2: MCP Summary Retrieval
    MCP->>Cache: Request summary via MCP
    Cache-->>MCP: Return cached summary from edge location

    Note over User,MCP: Alternative: Pre - cached Content
    rect rgba(31, 41, 55, 0.6)
        MCP->>Cache: Request summary for pre - cached video
        alt Content exists in cache
            Cache-->>MCP: Return cached summary
        else Content is not cached
            Cache-->>MCP: Cache miss
        end
    end

📦 Installation

Installation for Claude Desktop

1. First, build the server:

npm install
npm run build

2. Add the server configuration to your Claude Desktop configuration file:

• On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "deepsrt-mcp": {
      "command": "node",
      "args": [
        "/path/to/deepsrt-mcp/build/index.js"
      ]
    }
  }
}

Installation for Chrome Browser

1. Visit the Chrome Web Store.
2. Install the DeepSRT extension.
3. Complete the configuration according to the instructions in the extension.

💻 Usage Examples

Using the MCP Server via the Command Line

curl -X POST http://localhost:3000 \
     -H "Content-Type: application/json" \
     -d '{"video_id":"VafNvIcOs5w", "lang":"zh-tw", "mode":"narrative"}'

Using the Chrome Extension

1. Open the YouTube video for which you want to obtain a summary.
2. Click the DeepSRT extension icon.
3. Enter the video ID in the extension interface or use the current page directly.
4. Obtain and view the generated Chinese summary.

📚 Documentation

Frequently Asked Questions

Q: I'm getting a 404 error. Why?

A: This is because the video summary has not been cached at the CDN edge location. You need to open the video via the DeepSRT browser extension first so that it can be cached in the CDN network. After that, you can use MCP to obtain the summary.

You can verify the cache status using the following cURL command:

curl -s 'https://worker.deepsrt.com/transcript' \
-i --data '{"arg":"v=VafNvIcOs5w","action":"summarize","lang":"zh-tw","mode":"narrative"}' | grep -i "^cache-status"

If you see cache-status: HIT, it means the content is cached at the CDN edge location, and the MCP server should not return a 404 error.