CatchLoop

co.catchloopPublished by catchloop.coOfficial publisherv1.0.2Updated Oct 30, 2026

Product feedback for SaaS: requests, widget bugs with screenshots, changelog drafts.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

CatchLoop connects an assistant to a SaaS product-feedback workspace for requests, bug reports with screenshots, and changelog drafts.

What you can do
  • Work with product feedback in a CatchLoop workspace: feature requests and customer feedback.
  • Handle widget bug reports that include screenshots.
  • Work with changelog drafts.
  • No individual tools are documented, so the exact actions available are not specified.
When to use it
Useful when a team keeps its SaaS product feedback, widget bug reports and changelog drafts in CatchLoop and wants an assistant to work with that material directly instead of copying it between tools.
Requirements
A remote MCP endpoint at mcp.catchloop.co over streamable HTTP. A CatchLoop workspace API key is required, sent as a Bearer token in the Authorization header; the key is found in the dashboard under Settings > Integration.
Before you install
The connection requires a workspace API key sent as a Bearer token in the Authorization header, so treat it as a secret and grant only the workspace you intend. The documented scope covers feedback, bug reports and changelog drafts, which may involve reading customer data and writing or publishing content; the exact read and write actions are not documented, so confirm them before use.

Installation

In SourceWeft

  1. Open CatchLoop 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/co.catchloop%2Fcatchloop/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": {
    "catchloop": {
      "type": "http",
      "url": "https://mcp.catchloop.co/",
      "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

2
  1. v1.0.2LatestOct 30, 2026
  2. v1.0.0Oct 26, 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.