User Stories Bot

com.userstoriesbotPublished by userstoriesbot.comOfficial publisherv0.1.0Updated Oct 29, 2026

Narrated demo videos of a branch: your agent records, polls and fetches the video and stories.

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Remote MCP server that lets an agent record, poll and fetch narrated demo videos and stories for a code branch.

What you can do
  • Record a narrated demo video for a branch
  • Poll the status of a recording job until it finishes
  • Fetch the finished video and its stories
  • No individual tools are listed in the manifest, so exact tool names and parameters are not documented here.
When to use it
Useful when you want an assistant to produce a narrated walkthrough video of a branch's changes and retrieve the result, instead of describing the work in text only.
Requirements
A remote endpoint at app.userstoriesbot.com over streamable HTTP. A User Stories Bot account and an API key, sent as a bearer token in the Authorization header. Network access to the service.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and shared transcripts. Recordings are generated by a third-party service, so branch content and any material captured in the video is sent to that provider. The manifest lists no tools, so review what the server can do before granting access.

Installation

In SourceWeft

  1. Open User Stories Bot in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.userstoriesbot%2Fmcp/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.

{
  "mcpServers": {
    "user-stories-bot": {
      "type": "http",
      "url": "https://app.userstoriesbot.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.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.