Luseri

io.github.arthurrenardBPublished by GitHub account arthurrenardBv1.0.0Updated Oct 31, 2026

Read-only analytics for your Shopify apps: MRR, churn, uninstall reasons, App Store rank, reviews.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Read-only Luseri analytics for Shopify apps: MRR, churn, uninstall reasons, App Store rank and reviews, queried by an assistant over a remote endpoint.

What you can do
  • Read Shopify app revenue metrics such as MRR and churn
  • Inspect uninstall reasons and app performance trends
  • Check App Store rank and customer reviews for the app
  • All access is read-only analytics; no tools are listed in the manifest, so exact operations come from the provider's documentation.
When to use it
Useful when you want an assistant to answer questions about a Shopify app's subscription health, churn drivers, store ranking or review sentiment without opening the Luseri dashboard.
Requirements
A remote MCP endpoint at luseri.com over streamable HTTP. A Luseri account and a personal token created in Luseri under Settings, sent as a bearer token in the Authorization header.
Before you install
The Authorization header carries a personal Luseri token; treat it as a secret and avoid exposing it in shared logs or configs. Analytics data about your app's revenue, churn and reviews is sent to the assistant and its model provider.

Installation

In SourceWeft

  1. Open Luseri 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/io.github.arthurrenardB%2Fluseri/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": {
    "luseri": {
      "type": "http",
      "url": "https://luseri.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. v1.0.0LatestOct 31, 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.