Director

npx add-mcp 'https://api.director.screenforge.co/api/mcp'

Preview REST + MCP

Never explain your product twice.

Give Director a URL and one sentence. It walks your product in a real browser, maps every flow it finds, then turns that map into demo videos, help articles and in-app guides.

[

Get started

](https://app.director.screenforge.co/)

REC

The Product Graph

Every recording adds to one map of your product.

Director remembers what it explores: each flow, screen and control it touches. Demo videos, help articles and in-app guides are all views of that one map, so a capture made for one of them improves the rest. How the map works

Captured fromThe mapPublished as

Your coding agentOver MCP or REST

Ask DirectorDashboard or Slack

Environment crawlWhen you add a product

Product Graph Sign in Dashboard Settings Reports Projects Editor Billing Checkout Team

Flow: Mapped

Screens

Flows

Stale

Demo videosNarrated and zoomed

Help CenterPublic, on your domain

Internal TrainingPrivate, for your team

GuidesInside your own app

More on the waySame map, new views

What it publishes

Record a flow once. Publish it four ways.

Demo videos

A narrated video of any flow, with auto-zoom on the actions that matter and a cursor eased like a person's. Share a link or embed it.

Help Center

Step-by-step articles written from a recorded flow, with screenshots and markers. Host them on your own domain or sync them to Zendesk.

Internal Training

The same kind of article for your own team: onboarding, support playbooks, how the admin side works. Kept off the public Help Center.

Guides

Walkthroughs that run inside your product from one embed script. If a button moves, the guide skips that step and tells your team.

Ask Director

Ask in the dashboard, or with /director in Slack. It records flows, writes articles and publishes them, all from the same map.

Staying current

Re-check any flow against your live product and Director flags what changed. A live guide flags a step it can't find. Record the flow again to redraft its guides.

How a recording works

The polish an editor would add, added for you.

How Director works

$

Your problem right now

Three teams, one flow. Redone each release.

Here's what changes when Director walks the flow once and every team publishes from what it found.

TODAY

WITH DIRECTOR

Kickoff

Marketing, support and onboarding each record it again.

One instruction. Director walks the flow and adds it to your map.

The run

Record it live - fumble a step, do it again.

It signs in and clicks through the flow itself.

The output

Edit the video, screenshot every step, write it all up by hand.

Video, article and guide, drafted from one recorded flow.

Staying current

Next release, all three are out of date.

Re-checked against the live product, with drift flagged.

1 → 4

One recorded flow: video, help article, training doc, guide.

3 ways in

Your agent over MCP or REST, the dashboard, or Slack.

$0 to start

5 free minutes of video every month, no card needed.

Our pricing plans

Metered by the second, not boxed into a quota.

Every plan runs on credits.

1 credit is 1 minute of finished video, and you're billed for the seconds it actually takes. Your whole team shares one pool.

Free

$0

5 min of video/mo

• Just you

No credit card required

Starter

$29

20 min of video/mo

• About 25 demos
• Unlimited team members

Pro

Recommended

$99

75 min of video/mo

• About 100 demos
• Unlimited team members
• 3 demos at once
• 1-month rollover

Scale

$299

250 min of video/mo

• About 335 demos
• Unlimited team members
• 10 at once, priority queue
• 3-month rollover

Pay-as-you-go

Buy minutes in packs of 10, no subscription. Handy for an agent that only needs a few demos, or a month that runs over.

$2.00

/minute

A 45-second demo uses 0.75 credits, not a whole one. A demo that produces video bills at least 15 seconds.

Every render includes autonomous navigation, auto-zoom on the actions that matter, and a whole voiceover narration track - one output, nothing metered separately.

Compare plans in detail

Called by your agent, and not by a person

Every field is machine-fillable and every response is polled.
Call it as a REST endpoint — same job, same result, every time.

FIELDSNOTES

target{ type: "url" | "tunnel", url }. A public page, or a tunnel to a local dev server.

instructionOne sentence in plain language. Director resolves the steps.

credentials{ username, password }, literal values. Send a test account, not production.

authorizedtrue once the user confirms they own the product or may demo it. Needed once per new domain, and on every tunnel call.

options.fps1–60. Defaults to 30.

options.scaleHeight120–2160px output height. Default capture is roughly 1920x1200.

options.maxSteps1–60. A budget, so a run ends instead of wandering.

options.watermarkBoolean. Burns the Screenforge mark into the render.

# a public URL, or a tunnel to a local dev server

POST /api/demos

{
  "target": {
    "type": "tunnel",
    "url": "https://example-dev.trycloudflare.com"
  },
  "instruction": "Compare plans, then upgrade to Team.",
  "authorized": true,
  "credentials": {
    "username": "demo@example.com",
    "password": "hunter2"
  },
  "options": {
    "fps": 30,
    "scaleHeight": 1200,
    "maxSteps": 40,
    "watermark": false
  }
}

# credentials are literal values — send a test account

A URL and one sentence. Director maps the rest.

Director is in preview. Start with 5 free minutes of video a month, then let your agent, your team or Slack add to the same map.

[

Get started

](https://app.director.screenforge.co/)