VideoReceiverMCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@VideoReceiverMCPlist all saved videos"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VideoReceiverMCP
A minimal MCP (Model Context Protocol) server that receives video files over both:
stdio — for local agents (Claude Desktop, Cursor)
HTTP (Streamable-HTTP) — for remote/network clients
How it works
Sender project VideoReceiverMCP server
| |
| 1. encode video -> base64 string |
| 2. call receive_video(base64) -----> |
| | 3. decode base64 -> binary
| | 4. save to received_videos/
| <-- "Video received! ..." |MCP uses JSON-RPC (text only), so videos are base64-encoded before sending.
Related MCP server: golpo-mcp
Setup (local)
# 1. Run the setup script (creates venv + installs deps)
.\setup.ps1
# 2. Activate venv
.\venv\Scripts\Activate.ps1Run locally
stdio mode (for Claude Desktop / Cursor)
python video_mcp_server.pyHTTP mode (test network transport locally)
python video_mcp_server.py --http
# MCP endpoint: http://localhost:8000/mcpConfigure in Claude Desktop
Edit %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"VideoReceiverMCP": {
"command": "C:/path/to/mcp/venv/Scripts/python.exe",
"args": ["C:/path/to/mcp/video_mcp_server.py"]
}
}
}Configure in Cursor / VS Code
Edit .cursor/mcp.json in your project:
{
"mcpServers": {
"VideoReceiverMCP": {
"command": "C:/path/to/mcp/venv/Scripts/python.exe",
"args": ["C:/path/to/mcp/video_mcp_server.py"]
}
}
}Deploy on Render (free, persistent server)
Why Render and not Netlify? Netlify runs serverless/stateless functions — they cannot keep a persistent connection open, which MCP Streamable-HTTP requires. Render's free tier runs a full persistent Python process.
Push this repo to GitHub
Go to render.com -> New -> Web Service
Connect your GitHub repo — Render auto-reads
render.yamlDeploy! Your MCP endpoint will be:
https://<your-app>.onrender.com/mcp
Connect your other project to the deployed server
# In your other project:
from mcp.client.streamable_http import streamablehttp_client
from mcp import ClientSession
import base64, asyncio
async def send_video(video_path: str, server_url: str):
with open(video_path, "rb") as f:
b64 = base64.b64encode(f.read()).decode()
async with streamablehttp_client(server_url) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
result = await session.call_tool(
"receive_video",
arguments={"video_base64": b64, "filename": "clip.mp4"}
)
print(result.content[0].text)
asyncio.run(send_video("myvideo.mp4", "https://your-app.onrender.com/mcp"))Available Tools
Tool | Args | Description |
|
| Receives a base64 video, saves to |
| — | Lists all saved videos |
|
| Deletes a video from the server |
Test with the included client
# stdio (local)
python send_video_client.py myvideo.mp4
# HTTP (local server running on port 8000)
python send_video_client.py myvideo.mp4 --url http://localhost:8000/mcp
# HTTP (deployed on Render)
python send_video_client.py myvideo.mp4 --url https://your-app.onrender.com/mcpLimitations
Issue | Notes |
Size overhead | Base64 adds ~33% to file size |
Large files | Videos >50 MB may strain memory / context windows |
Netlify | Cannot host persistent MCP HTTP servers — use Render instead |
Project structure
mcp/
├── video_mcp_server.py # MCP server (stdio + HTTP transport)
├── send_video_client.py # Test client (stdio + HTTP)
├── requirements.txt # Python dependencies
├── setup.ps1 # One-click setup script
├── render.yaml # Render deployment config
├── Procfile # Railway / Heroku deployment
├── .gitignore
├── received_videos/ # Videos saved here (auto-created)
├── video_proxy_mcp.py # Local proxy MCP (VS Code / Antigravity IDE)
└── .vscode/mcp.json # MCP server config for VS Code / Antigravity IDEVS Code & Antigravity IDE Integration
The local proxy (video_proxy_mcp.py) bridges your AI IDE to the remote Render server.
It handles Base64 encoding automatically — just pass a plain file path.
Architecture (detailed)
┌─────────────────────────────────────────────────────────────┐
│ AI Agent (Antigravity IDE / GitHub Copilot) │
│ — asks to upload / download a video — │
└─────────────────────┬───────────────────────────────────────┘
│ stdio (JSON-RPC over stdin/stdout)
▼
┌─────────────────────────────────────────────────────────────┐
│ video_proxy_mcp.py (LOCAL) │
│ │
│ upload_video(path, description) │
│ 1. Path(path).read_bytes() ← reads binary from disk │
│ 2. base64.b64encode(raw) ← ~33 % size overhead │
│ 3. _call_remote("receive_video", {...}) │
│ │
│ download_video(filename, output_path) │
│ 1. _call_remote("download_video", {...}) │
│ 2. base64.b64decode(response["video_base64"]) │
│ 3. Path(output_path).write_bytes(raw) │
│ │
│ list_videos() → _call_remote("list_received_videos", {}) │
│ delete_video() → _call_remote("delete_video", {...}) │
└─────────────────────┬───────────────────────────────────────┘
│ HTTPS (Streamable-HTTP / JSON-RPC)
│ timeout: 300 s (large file support)
▼
┌─────────────────────────────────────────────────────────────┐
│ https://mcp-rgi7.onrender.com/mcp (REMOTE) │
│ video_mcp_server.py │
│ │
│ receive_video(video_base64, filename, description) │
│ 1. base64.b64decode(video_base64) → raw bytes │
│ 2. open(received_videos/<filename>, "wb").write(raw) │
│ 3. returns status + file size │
│ │
│ download_video(filename) │
│ 1. open(received_videos/<filename>, "rb").read() │
│ 2. returns JSON { filename, size_bytes, video_base64 } │
│ │
│ list_received_videos() → scans received_videos/ on disk │
│ delete_video(filename) → os.remove(received_videos/…) │
└─────────────────────┬───────────────────────────────────────┘
│
▼
/opt/render/project/src/
received_videos/
clip.mp4
demo.mp4
...Architecture (simplified overview — original)
AI Agent (VS Code / Antigravity IDE)
│ stdio
▼
video_proxy_mcp.py (runs locally)
│
├─ reads file from disk
├─ Base64-encodes it
└─ forwards to remote MCP
│ HTTPS
▼
https://mcp-rgi7.onrender.com/mcpSetup
The .vscode/mcp.json file is already in this repo. VS Code and Antigravity IDE
both pick it up automatically on startup:
{
"servers": {
"video-proxy": {
"command": "python",
"args": ["d:/workspace/mcp/video_proxy_mcp.py"]
}
}
}Available proxy tools
Tool | What to say to the agent |
| "Upload D:\clips\demo.mp4 to the server" |
| "Download clip.mp4 to C:\Downloads\clip.mp4" |
| "List all videos on the server" |
| "Delete clip.mp4 from the server" |
VS Code — uploading a video
After the upload completes, the server confirms the file name, size, and saved path:

Listing all videos stored on the server:

Antigravity IDE — uploading a video
After the upload the server returns the same confirmation:

Note: The Render free tier sleeps after inactivity. The first request may take 30–60 seconds to wake the server up. Subsequent calls are fast.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for programmatic video generation. Send a prompt, get an MP4.
- AlicenseNot gradedqualityDmaintenanceMCP server for the Golpo AI video API, enabling video generation, listing, and downloading from any MCP-compatible client.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server enabling video processing via natural language: transcription with Whisper, segment cutting with FFmpeg, and file management.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server exposing claude-video functionality for claude.ai web UI via HTTP+SSE, enabling video watching and analysis from claude.ai.
Related MCP Connectors
MCP server for the FFmpeg Micro video transcoding API — create, monitor, download transcodes.
MCP server for Clipkit — gives AI agents a video toolbox via the Clipkit schema.
MCP server for Wan AI video generation
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dpansumisra/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server