Recapp — Loom for agents

dev.recappPublished by recapp.devOfficial publisherv1.0.0Updated Oct 25, 2026

Loom for agents: AI agents record narrated product demos, plus transcripts, summaries, and search.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryMedia & Design

Overview

AI-generated overview

Recapp is a remote MCP server that lets AI agents record narrated product demos, with transcripts, summaries and search.

What you can do
Record narrated product demos as an AI agent, per the description's positioning as a Loom-style tool for agents. Produce transcripts and summaries of recorded demos. Search recorded content. No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Consider it when an assistant should capture narrated walkthroughs or demos of a product and later retrieve them by transcript, summary or search, rather than only describing steps in text.
Requirements
A remote MCP connection over streamable HTTP to the provider's endpoint. OAuth authentication is required. No environment variables, headers or local packages are declared.
Before you install
Access is granted through OAuth, so review the scopes and permissions requested at sign-in. Recordings may capture screen content and audio, and transcripts, summaries and search results are handled by the third-party service; avoid recording sensitive or confidential material.

Installation

In SourceWeft

  1. Open Recapp — Loom for agents 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/dev.recapp%2Frecapp/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": {
    "recapp-loom-for-agents": {
      "type": "http",
      "url": "https://recapp.dev/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.0LatestSep 24, 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.