Content Tools

refs.video

Provides searchable video references, frame sheets, and reverse-engineered blueprints and formulas for top-performing launch films, demos, and explainers to guide content production.

1 endpoint12 known toolsFirst detected October 21, 2026Last detected October 21, 2026

ENDPOINT 1

https://refs.video/mcp

No auth detected

MCP server metadata

Name: refs
Version: 0.8.3

Capabilities

tools

Known tools 12

search_videos

Search 4,000+ dissected top-performing videos (launch films, product demos, explainers, motion design, interactive/3D, film + music, teasers).

Inferred read-only

get_blueprint

The full reverse-engineered blueprint of one video: hook frame by frame, beat sheet with timestamps, shot list, style guide, voice and sound, script template, production plan, edit recipe, QA checklist, plus a runnable recipe prompt.

Potential side effects

get_frames

One video's labelled frame sheets as images, so you can see the reference instead of guessing from text: the hook (first 3 s at 0.

Inferred read-only

list_formulas

Formulas distilled across many videos of one format (e.

Inferred read-only

get_formula

The full cross-video formula for one format, as markdown: structure, timing ranges, what top performers share, mistakes to avoid, and a template prompt.

Inferred read-only

list_collections

Your collections on refs.

Inferred read-only

get_collection

Every film in a Refs collection as search cards (REF id, link, length, aspect, measured metrics, why it works).

Inferred read-only

list_brands

Your brand imports on refs.

Inferred read-only

get_brand

One of your brand imports: the brand kit (the brand's house style across all its films: palette, type, logo and end card, motion and easing, pacing and cut rhythm, camera, transitions, sound and voice, recurring formats, written as rules to follow) plus each film's blueprint summary with its id (brand:<import>:<film>) for get_blueprint and get_frames.

Inferred read-only

plan_video

Give a brief (product, audience, length, platform) and 1-5 references (REF ids, links or ids, or your brand films' brand:<import>:<film> ids), and optionally one of your imported brands (brand) to plan in its house style.

Inferred read-only

storyboard

Before anything is built, storyboard the film the way an editor does.

Inferred read-only

check_render

After rendering a video from a reference, check it against that film's measured timeline and get concrete fixes: cut timing to the frame, pace, brightness curve, motion per shot, loudness for the platform, and format.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.refs]
url = "https://refs.video/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "refs": {
      "type": "http",
      "url": "https://refs.video/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: refs
Remote MCP URL: https://refs.video/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "refs": {
      "url": "https://refs.video/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "refs": {
      "type": "http",
      "url": "https://refs.video/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "refs",
  "transport": "streamable-http",
  "url": "https://refs.video/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.