@felores/mcp-video 0.5.3

package/.prettierrc

@@ -0,0 +1,3 @@
+{
+  "endOfLine": "auto"
+}

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,49 @@
+# Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of
+fostering an open and welcoming community, we pledge to respect all people who
+contribute through reporting issues, posting feature requests, updating
+documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free
+experience for everyone, regardless of level of experience, gender, gender
+identity and expression, sexual orientation, disability, personal appearance,
+body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery
+- Personal attacks
+- Trolling or insulting/derogatory comments
+- Public or private harassment
+- Publishing other's private information, such as physical or electronic
+  addresses, without explicit permission
+- Other unethical or unprofessional conduct
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+By adopting this Code of Conduct, project maintainers commit themselves to
+fairly and consistently applying these principles to every aspect of managing
+this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting a project maintainer at anais@anaisbetts.org. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. Maintainers are
+obligated to maintain confidentiality with regard to the reporter of an
+incident.
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.3.0, available at
+[http://contributor-covenant.org/version/1/3/0/][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/3/0/

package/COPYING

@@ -0,0 +1,7 @@
+Copyright (c) 2024 Anaïs Betts
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

package/README.md

@@ -0,0 +1,207 @@
+# Video MCP Server
+
+A powerful Model Context Protocol (MCP) server that enables AI assistants like Claude to work with video content. This server provides capabilities for downloading video transcripts in plain text and videos from various platforms including YouTube, Vimeo, Twitter/X, and TikTok.
+
+This project is a fork from anaisbetts/mcp-youtube which only outputs the transcript with timestamps. This project outputs the transcript in plain text without timestamps for easy LLM consumption and adds the download tool.
+
+## Features
+
+- Download and process video subtitles/closed captions for AI analysis
+- Download videos in high quality (up to 1080p)
+- Support for multiple platforms:
+  - YouTube
+  - Vimeo
+  - Twitter/X
+  - TikTok
+  - And more platforms supported by yt-dlp
+
+## MCP Tools
+
+This server provides two powerful tools that can be used by AI assistants through the Model Context Protocol:
+
+### 1. Video Transcript Tool (`get_video_transcript`)
+- Downloads and processes video subtitles/closed captions into plain text format
+- Removes timestamps and formatting for easy AI consumption
+- Supports auto-generated captions when available
+- Works with multiple languages (defaults to English)
+- Input: Video URL from any supported platform
+- Output: Clean, plain text transcript ready for AI analysis
+
+### 2. Video Download Tool (`download_video`)
+- Downloads videos in high quality (limited to 1080p for reasonable file sizes)
+- Automatically selects the best quality format
+- Merges video and audio streams when necessary
+- Saves files to a configurable downloads directory
+- Input: 
+  - Video URL from any supported platform
+  - Optional filename (recommended format: platform-id, e.g., 'youtube-MhOTvvmlqLM')
+- Output: 
+  - Downloaded video file in MP4 format
+  - File information including title, duration, resolution, and file size
+
+## Prerequisites
+
+### Node.js and npm
+
+1. Install Node.js (version 18 or higher) and npm from [nodejs.org](https://nodejs.org/)
+2. Verify installation:
+   ```bash
+   node --version
+   npm --version
+   ```
+
+### Installing yt-dlp
+
+The server requires `yt-dlp` to be installed on your system. Here are the installation methods for different platforms:
+
+#### Windows
+1. Using WinGet (Recommended):
+   ```powershell
+   winget install yt-dlp
+   ```
+2. Using Scoop:
+   ```powershell
+   scoop install yt-dlp
+   ```
+3. Manual Installation:
+   - Download the latest release from [yt-dlp releases](https://github.com/yt-dlp/yt-dlp/releases)
+   - Place the executable in a directory in your PATH
+
+#### macOS
+1. Using Homebrew:
+   ```bash
+   brew install yt-dlp
+   ```
+2. Using MacPorts:
+   ```bash
+   sudo port install yt-dlp
+   ```
+
+#### Linux
+1. Using package manager:
+   ```bash
+   # On Debian/Ubuntu
+   sudo apt install yt-dlp
+   
+   # On Fedora
+   sudo dnf install yt-dlp
+   
+   # On Arch Linux
+   sudo pacman -S yt-dlp
+   ```
+2. Using pip:
+   ```bash
+   python3 -m pip install -U yt-dlp
+   ```
+
+## Installation and Setup
+
+### Option 1: Direct Installation (Recommended for Users)
+
+Install the MCP server using the [mcp-installer](https://github.com/anaisbetts/mcp-installer):
+```bash
+# Install mcp-installer if you haven't already
+npm install -g @anaisbetts/mcp-installer
+
+# Install this MCP server
+mcp-installer install @felores/mcp-video
+```
+
+### Option 2: Manual Installation (Recommended for Developers)
+
+1. Clone the repository:
+   ```bash
+   git clone https://github.com/felores/mcp-video.git
+   cd mcp-video
+   ```
+
+2. Install dependencies:
+   ```bash
+   npm install
+   ```
+
+3. Build the project:
+   ```bash
+   npm run build
+   ```
+
+4. Start the server:
+   ```bash
+   npm start
+   ```
+
+## Usage
+
+Once installed, you can use this server through any MCP-compatible client (like Claude.ai). Here are some example prompts:
+
+1. To analyze a video's content:
+   ```
+   Summarize the YouTube video https://youtube.com/watch?v=VIDEO_ID
+   ```
+
+2. To get specific information:
+   ```
+   What are the main points discussed in this video: https://youtube.com/watch?v=VIDEO_ID
+   ```
+
+The server will automatically:
+1. Download the video's subtitles/closed captions
+2. Process and clean the text
+3. Make it available to the AI assistant for analysis
+
+## Environment Variables
+
+- `DOWNLOADS_DIR`: Specify a custom directory for downloaded videos (default: `./downloads`)
+
+## Development
+
+### Setting Up Development Environment
+
+1. Fork and clone the repository:
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/mcp-video.git
+   cd mcp-video
+   ```
+
+2. Install development dependencies:
+   ```bash
+   npm install
+   ```
+
+3. Build the project:
+   ```bash
+   npm run build
+   ```
+
+4. Start the development server:
+   ```bash
+   npm start
+   ```
+
+### Running Tests
+```bash
+npm test
+```
+
+### Making Changes
+1. Create a new branch:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. Make your changes and commit:
+   ```bash
+   git add .
+   git commit -m "Description of changes"
+   ```
+
+3. Push to your fork:
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+4. Create a Pull Request from your fork to the main repository
+
+## License
+
+MIT License - See [COPYING](COPYING) for details.

package/documentation/mcp-inspector-guide.md

@@ -0,0 +1,308 @@
+# MCP Inspector Guide for LLMs
+
+This guide provides detailed information about using the MCP Inspector tool for testing, debugging, and validating MCP servers.
+
+## 1. Getting Started
+
+### Installation and Basic Usage
+```bash
+# Run directly without installation
+npx mcp-inspector <server-command>
+
+# For NPM/PyPi packages
+npx mcp-inspector npx -y @your-package/server-name
+
+# For local development
+npx mcp-inspector node path/to/your/server.js
+npx mcp-inspector python path/to/your/server.py
+```
+
+### Server Connection Setup
+1. Select appropriate transport (stdio/SSE)
+2. Configure command-line arguments
+3. Set required environment variables
+4. Test initial connection
+
+## 2. Core Features
+
+### Server Connection Pane
+1. Transport Selection:
+   - stdio for local servers
+   - SSE for network-based servers
+   - Custom transport configuration
+
+2. Connection Settings:
+   - Command-line arguments
+   - Environment variables
+   - Connection timeouts
+
+3. Status Monitoring:
+   - Connection state
+   - Protocol version
+   - Capability negotiation
+
+### Resources Tab
+1. Resource Listing:
+   ```typescript
+   // Example resource listing structure
+   {
+     resources: [
+       {
+         uri: "custom://resource",
+         name: "Resource Name",
+         description: "Resource description",
+         mimeType: "text/plain"
+       }
+     ]
+   }
+   ```
+
+2. Resource Inspection:
+   - View metadata
+   - Examine content
+   - Check MIME types
+   - Test resource reading
+
+3. Subscription Testing:
+   - Subscribe to updates
+   - Monitor changes
+   - Test unsubscribe
+
+### Prompts Tab
+1. Template Inspection:
+   ```typescript
+   // Example prompt structure
+   {
+     name: "prompt-name",
+     description: "Prompt description",
+     arguments: [
+       {
+         name: "arg1",
+         description: "Argument description",
+         required: true
+       }
+     ]
+   }
+   ```
+
+2. Testing Features:
+   - View available templates
+   - Test with custom arguments
+   - Preview generated messages
+   - Validate responses
+
+### Tools Tab
+1. Tool Discovery:
+   ```typescript
+   // Example tool listing
+   {
+     tools: [
+       {
+         name: "tool-name",
+         description: "Tool description",
+         inputSchema: {
+           type: "object",
+           properties: {
+             // Parameter definitions
+           }
+         }
+       }
+     ]
+   }
+   ```
+
+2. Testing Features:
+   - List available tools
+   - Validate schemas
+   - Test execution
+   - Monitor results
+
+### Notifications Pane
+1. Message Types:
+   - Server logs
+   - Error messages
+   - Status updates
+   - Progress notifications
+
+2. Monitoring:
+   - Real-time updates
+   - Message filtering
+   - Error tracking
+
+## 3. Testing Workflows
+
+### Development Workflow
+1. Initial Testing:
+   ```bash
+   # Start Inspector with development server
+   npx mcp-inspector npm run dev
+   ```
+
+2. Development Cycle:
+   - Make code changes
+   - Restart server
+   - Test affected features
+   - Monitor logs
+   - Debug issues
+
+3. Feature Testing:
+   - Verify basic functionality
+   - Test edge cases
+   - Check error handling
+   - Validate responses
+
+### Resource Testing
+1. Listing Verification:
+   - Check resource discovery
+   - Validate metadata
+   - Test pagination
+   - Check updates
+
+2. Content Testing:
+   - Read resource content
+   - Verify MIME types
+   - Test binary data
+   - Check encoding
+
+3. Subscription Testing:
+   - Subscribe to resources
+   - Monitor updates
+   - Test unsubscribe
+   - Verify notifications
+
+### Tool Testing
+1. Discovery Testing:
+   - List available tools
+   - Verify schemas
+   - Check descriptions
+   - Validate metadata
+
+2. Execution Testing:
+   - Test with valid inputs
+   - Try invalid inputs
+   - Check error handling
+   - Monitor progress
+   - Validate results
+
+### Prompt Testing
+1. Template Verification:
+   - Check available prompts
+   - Validate arguments
+   - Test descriptions
+   - Verify schemas
+
+2. Generation Testing:
+   - Test with arguments
+   - Check message format
+   - Validate content
+   - Test error cases
+
+## 4. Debugging
+
+### Common Issues
+1. Connection Problems:
+   - Check server process
+   - Verify transport
+   - Monitor initialization
+   - Check capabilities
+
+2. Message Errors:
+   - Validate formats
+   - Check handlers
+   - Monitor responses
+   - Track errors
+
+3. Resource Issues:
+   - Check permissions
+   - Verify paths
+   - Test content types
+   - Monitor updates
+
+### Debugging Tools
+1. Console Logging:
+   ```typescript
+   // Server-side logging
+   console.error("Debug message");
+   ```
+
+2. Message Inspection:
+   - View raw messages
+   - Check formatting
+   - Track request/response
+   - Monitor timing
+
+3. Error Analysis:
+   - Stack traces
+   - Error codes
+   - Response validation
+   - Context examination
+
+## 5. Best Practices
+
+### Testing Strategy
+1. Systematic Approach:
+   - Test core features first
+   - Add edge cases
+   - Verify error handling
+   - Check performance
+
+2. Resource Management:
+   - Monitor memory usage
+   - Check file handles
+   - Verify cleanup
+   - Test limits
+
+3. Error Handling:
+   - Test all error paths
+   - Verify messages
+   - Check recovery
+   - Monitor cleanup
+
+### Security Testing
+1. Input Validation:
+   - Test boundaries
+   - Try invalid input
+   - Check sanitization
+   - Verify limits
+
+2. Authentication:
+   - Test credentials
+   - Check permissions
+   - Verify tokens
+   - Monitor access
+
+3. Resource Protection:
+   - Test access control
+   - Check paths
+   - Verify isolation
+   - Monitor usage
+
+## 6. Performance Testing
+
+### Response Time
+1. Operation Timing:
+   - Track latency
+   - Monitor variance
+   - Check thresholds
+   - Log outliers
+
+2. Batch Operations:
+   - Test concurrent requests
+   - Monitor memory
+   - Check throughput
+   - Verify ordering
+
+### Resource Usage
+1. Memory Monitoring:
+   - Track allocation
+   - Check leaks
+   - Monitor peaks
+   - Verify cleanup
+
+2. Connection Management:
+   - Test connection stability
+   - Check timeouts
+   - Monitor states
+   - Verify cleanup
+
+This guide should be used as a reference when testing and debugging MCP servers using the Inspector tool. Always consider the specific requirements of your server while following these guidelines.