Director

co.screenforgePublished by screenforge.coOfficial publisherv1.0.2Updated Oct 30, 2026

Record demos of your web app from one sentence and turn its product map into help articles and more.

VerifiedStreamable HTTPWeb executableBrowser AutomationKnowledge & MemoryMedia & Design

Overview

AI-generated overview

Director records narrated demo videos of your web app from a one-sentence instruction and turns the flows it maps into help-center articles.

What you can do
  • Create, monitor, cancel and list narrated demo recordings of a web app, and read their transcripts or answer follow-up questions.
  • Manage saved environments for apps behind a login, including verification and login codes.
  • List, attest and verify domains you are authorized to demo.
  • Browse the product map of pages and flows Director discovered, and re-verify a flow.
  • Create, edit, regenerate, publish, unpublish, resync and delete help articles, categories and sections.
  • Manage recording presets and list available integrations.
When to use it
Useful when you want marketing or onboarding demo videos and step-by-step help articles for a web app without screen-recording by hand, and want an assistant to trigger, check and publish them from plain-language requests.
Requirements
A remote Streamable HTTP endpoint; nothing to install locally. Authentication is OAuth (the client opens a browser on first use) or a Director API key sent in the X-API-Key header. A Director account is needed to sign up and obtain keys.
Before you install
The API key is a secret; keep it out of shared configs. Recording a site you do not own requires confirming you are authorized or verifying the domain. Saved environments hold sign-in details for logged-in apps. Many tools write, publish or delete content, so rely on the read-only/destructive annotations and confirm before changes.

Installation

In SourceWeft

  1. Open Director in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.screenforge%2Fdirector/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "director": {
      "type": "http",
      "url": "https://api.director.screenforge.co/api/mcp"
    }
  }
}

README

Director MCP server

Director records narrated product demo videos of your web app from one sentence, and turns the map of your product it builds along the way into help-center articles.

This repository describes Director's hosted MCP server. The server itself runs at https://api.director.screenforge.co/api/mcp; there is nothing to install or run locally.

What it does

Give Director a URL and an instruction such as "show how to invite a teammate". It drives a real browser through your app, records it, writes and voices the narration, and returns a polished video. While it works it maps the pages and flows it walks, and you can turn any of those flows into a step-by-step help article with screenshots.

Configure

The server uses Streamable HTTP. Sign in with OAuth (your client opens a browser the first time), or send a Director API key from app.director.screenforge.co in the X-API-Key header.

VS Code / GitHub Copilot (.vscode/mcp.json):

json
{  "servers": {    "director": {      "type": "http",      "url": "https://api.director.screenforge.co/api/mcp"    }  }}

To use an API key instead of OAuth:

json
{  "inputs": [    {      "type": "promptString",      "id": "director-api-key",      "description": "Director API key",      "password": true    }  ],  "servers": {    "director": {      "type": "http",      "url": "https://api.director.screenforge.co/api/mcp",      "headers": { "X-API-Key": "${input:director-api-key}" }    }  }}

Claude Code:

bash
claude mcp add --transport http director https://api.director.screenforge.co/api/mcp

Any other MCP client: add a remote (Streamable HTTP) server with the URL above.

Use

Ask your assistant in plain language, for example:

  • "Record a demo of app.example.com showing how to create a project."
  • "Is my demo done yet? Send me the video link."
  • "List the flows Director found on app.example.com and write a help article for the billing one."
  • "Publish that article."

Recording a site you don't own needs your confirmation that you're authorized to demo it, or a verified domain. Apps behind a login use a saved environment that holds the sign-in details, so you don't paste passwords into chat.

Tools

Demos: create_demo, wait_for_demo, get_demo_status, get_demo_transcript, answer_demo_question, cancel_demo, list_demos

Environments (logged-in apps): create_environment, get_environment, update_environment, list_environments, verify_environment, create_login_code, delete_session

Domains: list_domains, attest_domain, start_domain_verification, check_domain_verification

Product map: list_graph_flows, get_graph_flow, reverify_flow

Help articles: list_articles, get_article, create_article_from_flow, create_article, update_article, regenerate_article, publish_article, unpublish_article, resync_article, delete_article, list_article_categories, create_article_category, create_article_section

Recording presets: list_recording_presets, create_recording_preset, update_recording_preset

Integrations: list_integrations

Every tool is annotated read-only or destructive so your client can ask before anything changes.

Support

Email [email protected].

Source: README.md at commit 9584338

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.2LatestOct 29, 2026
  2. v1.0.1Oct 26, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.