StoryCapture

com.storycapturesPublished by storycaptures.comOfficial publisherv0.2.0Updated Oct 31, 2026

Write, rehearse, record and publish website demo videos, from the desktop app or the cloud.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

StoryCapture connects an assistant to a service for writing, rehearsing, recording and publishing website demo videos, via a remote endpoint or a local npm…

What you can do
  • No tool list is published, so capabilities are inferred from the description.
  • Create and script website demo videos from the desktop app or the cloud.
  • Rehearse and record demo walkthroughs of a website.
  • Publish finished demo videos.
  • Connect either to a hosted remote endpoint or to a local process started with npx.
When to use it
When you want an assistant to help produce website demo or product walkthrough videos — drafting the flow, rehearsing it, recording it and publishing the result — rather than editing video by hand.
Requirements
A StoryCapture account with OAuth sign-in, or the token from the app under Settings → Integrations → MCP server, supplied as STORYCAPTURE_MCP_TOKEN. The local option runs through npx (Node.js) and may need STORYCAPTURE_MCP_PORT if the port was changed in Settings → Integrations. Network access to the StoryCapture service.
Before you install
The server requires authentication and a secret token; treat STORYCAPTURE_MCP_TOKEN as a credential and keep it out of shared configuration. It can record and publish content, so check what is being captured and where it is published before letting an assistant act. No tool list is published, so review the actual tools after connecting.

Installation

In SourceWeft

  1. Open StoryCapture 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/com.storycaptures%2Fstorycapture/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": {
    "storycapture": {
      "type": "http",
      "url": "https://mcp.storycaptures.com/mcp"
    }
  }
}

README

This repository has no README.

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. v0.2.0LatestOct 31, 2026
  2. v0.1.0Oct 19, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.