Demofy

io.demofyPublished by demofy.ioOfficial publisherv1.0.0Updated Oct 29, 2026

Turn a URL and one line of intent into a narrated product demo video, from any MCP client.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Demofy turns a URL and a one-line intent into a narrated product demo video, usable from any MCP client.

What you can do
  • Generate a narrated product demo video from a URL plus a short statement of intent.
  • No tool list is published, so the exact operations an assistant can call are not documented here.
  • Access is through a hosted remote endpoint, so the work happens on Demofy's side rather than locally.
When to use it
Useful when you want an assistant to produce a short narrated demo or walkthrough video of a web product without recording and editing it yourself.
Requirements
A Demofy account with OAuth sign-in to the remote endpoint at app.demofy.io; no local package, environment variables or headers are declared.
Before you install
OAuth grants the server access to your Demofy account, and the URL and intent you supply are sent to a third-party service that renders the video; check what the account allows before connecting.

Installation

In SourceWeft

  1. Open Demofy 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/io.demofy%2Fdemofy/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": {
    "demofy": {
      "type": "http",
      "url": "https://app.demofy.io/api/mcp"
    }
  }
}

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

1
  1. v1.0.0LatestOct 29, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.