ClosedLoop AI

io.github.closedloop-ai-orgPublished by GitHub account closedloop-ai-orgv1.0.0Updated Nov 1, 2026

Source-linked product insights from customer feedback. Research needs and prepare customer calls.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that gives an assistant source-linked product insights from customer feedback and helps prepare customer calls.

What you can do
  • Surface product insights drawn from customer feedback, with links back to the underlying sources.
  • Research customer needs ahead of calls.
  • Help prepare for customer conversations.
  • No tool list is published, so the exact operations are not documented in the available material.
When to use it
Useful when a team wants an assistant to ground product decisions in real customer feedback, or to get context ready before a customer call.
Requirements
A remote MCP endpoint at mcp.closedloop.sh over streamable HTTP; OAuth authentication is required, so a ClosedLoop account is presumably needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your account data; customer feedback and call-related information may be sent to and processed by a third-party service. Review what data is shared before connecting.

Installation

In SourceWeft

  1. Open ClosedLoop AI 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.github.closedloop-ai-org%2Fclosedloop-ai/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": {
    "closedloop-ai": {
      "type": "http",
      "url": "https://mcp.closedloop.sh/"
    }
  }
}

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.0LatestNov 1, 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.