Merge Demos
merge_demosMerge multiple single-POV .dm91 demo files from the same match into one omniscient multi-POV demo where every player is always visible. All input demos must be from the same match (same map); the tool validates this and…
How it works ↓Pricing
Per call
$0.02
Model
time-based
Pay only for what you use. No subscriptions.
Inputs
output_filename
stringnullpov_client_num
integernullspec_pov
booleannullinputs *
arrayInput Parameters
Cost per run
Execution cost$0.02
About Merge Demos
Merge multiple single-POV .dm_91 demo files from the same match into one omniscient multi-POV demo where every player is always visible. All input demos must be from the same match (same map); the tool validates this and returns an error if they differ. Provide one file per player POV (at least 2). Returns the output path and any non-fatal warnings.
Frequently Asked Questions
Merge multiple single-POV .dm_91 demo files from the same match into one omniscient multi-POV demo where every player is always visible. All input demos must be from the same match (same map); the tool validates this and returns an error if they differ. Provide one file per player POV (at least 2). Returns the output path and any non-fatal warnings.
Merge Demos costs $0.02 per call on xpay. No subscription, no minimums. Pay only for the calls you make. New accounts get $5 in free credits.
Connect the Mcps MCP endpoint to your client — Claude Code: claude mcp add --transport http quakelive "https://quakelive.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"; Cursor/Windsurf/Cline/VS Code: same URL in mcp.json. The agent will see merge_demos as a callable tool with the input schema and run it directly. (Unified across all providers: https://mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY, then xpay_run with toolPath quakelive/merge_demos.)
Yes — that's exactly what xpay is for. You don't need a Mcps account or API key. Sign up at xpay.tools (Google or email), get $5 free credit, and run Merge Demos immediately. Billing flows through your xpay balance.
Merge Demos accepts 4 input parameters: output_filename, pov_client_num, spec_pov, inputs. See the input schema and runnable form on this page for details and to test live.