Loopwise MCP Server

com.loopwisePublished by loopwise.comOfficial publisherv1.0.0Updated Oct 27, 2026

Read and manage courses, members, orders, events, posts, and settings for Loopwise-powered sites.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant read and manage courses, members, orders, events, posts and settings on Loopwise-powered sites.

What you can do
  • Read and manage courses on Loopwise-powered sites
  • Look up and manage members
  • View and handle orders
  • Manage events
  • Manage posts
  • Adjust site settings
When to use it
Useful when you run a site built on Loopwise and want an assistant to look up or change course, member, order, event, post or settings data without using the admin interface directly.
Requirements
A remote MCP endpoint at mcp.loopwise.com over streamable HTTP; OAuth sign-in is required. No packages, environment variables or headers are declared.
Before you install
The server can change data, not just read it: courses, members, orders, events, posts and settings can be modified, so review write actions before approving them. Access is granted through OAuth to a Loopwise account, so scope the authorization to the sites you intend to expose. Order and member data is customer information handled by a third-party service.

Installation

In SourceWeft

  1. Open Loopwise MCP Server 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.loopwise%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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "loopwise": {
      "type": "http",
      "url": "https://mcp.loopwise.com/"
    }
  }
}

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

1
  1. v1.0.0LatestSep 16, 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.