Video Editor MCP server

Created By
burningiona year ago
MCP Interface for Video Jungle
Overview

what is Video Editor MCP?

Video Editor MCP is a server interface that allows users to upload, edit, search, and generate videos using the Video Jungle platform.

how to use Video Editor MCP?

To use Video Editor MCP, sign up for an account at Video Jungle, obtain your API key, and follow the provided instructions to set up the server and use its tools.

key features of Video Editor MCP?

  • Upload and edit videos from various sources.
  • Search videos using embeddings and keywords.
  • Generate video edits from multiple videos or a single video file.
  • Custom URI scheme for accessing individual videos and projects.

use cases of Video Editor MCP?

  1. Creating video compilations from multiple sources.
  2. Searching for specific content within videos for editing purposes.
  3. Generating quick edits based on user-defined criteria.

FAQ from Video Editor MCP?

  • Do I need an account to use Video Editor MCP?

Yes, you must sign up for an account at Video Jungle to use this tool.

  • Is there a cost associated with using Video Editor MCP?

The project does not specify costs, but check Video Jungle for any potential fees.

  • Can I edit videos from my local storage?

Yes, you can search and edit videos stored locally on your device.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
burningion
Star
146
Language
Python
License
-
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago