VidForgeX MCP: Video Intelligence for AI Agents
The VidForgeX MCP server gives Claude, Cursor, and any Model Context Protocol client direct access to 11 video intelligence tools — analyze footage, search your library, track persons, and generate reports without leaving your LLM workflow.
What MCP gives you that REST does not
A REST API requires you to write code that calls it. The MCP server lets the LLM call it directly. When Claude is analyzing a coaching session and needs to compare two players, it does not need a human to write an API call — it calls compare_profiles automatically, with the correct parameters, in the context of the conversation.
This enables entirely new workflows: a coach asks Claude to "prepare a scouting report on our next opponent based on the last 3 videos I uploaded" — Claude calls get_session_resultthree times, synthesizes the analysis data, and produces the report without the coach touching any API.
MCP configuration
Claude Desktop config (claude_desktop_config.json):
Add VidForgeX under the mcpServers key with URL https://mcp.vidforgex.com, transport sse, and your vfx_ API key as the Authorization Bearer token.
Tool reference
| Tool | Key parameters | Returns |
|---|---|---|
analyze_session | video_id, analysis_type, organization_id | Job ID for polling |
get_session_result | video_id, analysis_type | Full structured analysis JSON |
ask_about_session | video_id, question, history[] | SSE or JSON text answer |
ask_about_person | person_id, question | Answer grounded in person's video history |
compare_profiles | person_ids[] (2–10), metric_focus | Side-by-side comparison table |
get_person_progression | person_id, limit (1–50) | Metric timeline across sessions |
find_person_in_video | video_id, reference_image_url | Sighting timeline with timestamps |
get_team_summary | organization_id, period_days (1–365) | Aggregated team metrics |
get_sop_compliance | video_id, rule_template_id | Compliance score + violations |
tag_person_to_session | video_id, person_name or person_id | Tag confirmation or disambiguation list |
generate_sop_document | video_id, template_id | Formatted SOP document |
Rate limiting
Rate limiting for the VidForgeX API is enforced globally at the proxy layer using a distributed counter, ensuring limits are consistent across all instances simultaneously — horizontal scaling cannot be exploited to exceed limits.
Tiers: standard=60/min, elevated=300/min, unlimited=no limit. When exceeded: JSON-RPC error -32004 with retry_after_ms.