noibu — Claude Code plugin: what it does, how to install
Connects Claude Code to Noibu error and conversion data for online stores. It tracks down checkout drops and revenue leaks directly from the terminal.
/plugin install noibu@claude-plugins-official
/plugin marketplace add anthropics/claude-plugins-officialWhat noibu does
This plugin connects Claude Code to Noibu e-commerce monitoring. The agent inspects customer session recordings and frontend errors directly in your project. You can trace checkout drop-offs back to code failures and see how much revenue each bug costs.
The tool also links marketing traffic with on-site shopping friction. You must authenticate with Noibu before running requests, as queries pull live metrics directly from your account.
What it helps with
- link store frontend errors to lost revenue
- identify drop-off causes in the checkout funnel
- diagnose why viewed products fail to convert
- review payment friction using session heatmaps
Example prompts for the agent
- Show the errors during checkout that caused the biggest revenue drops this week
- Find catalog items with high pageviews but zero sales and diagnose conversion issues
- Analyze session replays around checkout to uncover payment and delivery friction
How to install noibu
Plugin marketplace
/plugin install noibu@claude-plugins-official/plugin marketplace add anthropics/claude-plugins-officialStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about noibu
How to install noibu in Claude Code?
First add the repository using /plugin marketplace add anthropics/claude-plugins-official. Then install the plugin with /plugin install noibu@claude-plugins-official.
What does noibu do?
It exposes store session replays, error logs, and conversion figures to Claude Code. The agent uses this data to prioritize bugs based on direct revenue impact.
What is required to run the noibu plugin?
You must authenticate with your Noibu account after installation. The plugin cannot retrieve store metrics without valid service credentials.
Source text
src · MIT
# Noibu AI Plugin
Official Noibu plugin for AI clients. Access Noibu products direclty from your AI coding tool.
## Description
Built for ecommerce, the Noibu plugin bridges the gap between customer experience and revenue by connecting Claude
directly to your store's session, error, and conversion data through Noibu — and to the marketing, support, and commerce
platforms that put insight into motion. Go beyond analysis: surface what's costing you revenue, take action across your
stack, build workflows to automate work end-to-end.
## Installation
### Claude Desktop (manual)
1. Download the Noibu plugin: https://github.com/Noibu/ai-plugin/releases/latest/download/noibu.zip
2. Go to **Customize**
3. Click **Create plugin** → **Upload plugin**
4. Upload the `noibu.zip` file
### Claude Code
Install directly from the marketplace — no download required:
```shell
/plugin marketplace add Noibu/ai-plugin
/plugin install noibu@noibu-plugins
/reload-plugins
```
## Releases & distribution
This repo (`Noibu/ai-plugin`, public) is the source of truth and feeds two channels:
- **Claude Code** — installs from this repo as a marketplace (`Noibu/ai-plugin`).
- **Cowork** — served from the private mirror `Noibu/ai-plugin-sync`.
Every push to `main` runs `.github/workflows/release.yml`, which:
1. Bumps the patch version (from the latest `v*` git tag),
2. Stamps it into `noibu.zip` only (the committed `plugin.json` carries **no** version),
3. Tags + creates a GitHub release with the versioned `noibu.zip`,
4. Force-pushes `main` to the private `ai-plugin-sync` mirror.
> **Versioning is by commit SHA, deliberately.** `main` is branch-protected, so the
> workflow cannot push a version-bump commit back to it. Instead, `plugin.json` omits
> the `version` field: the marketplace then versions the plugin by commit SHA, so **every
> merge to `main` is a new version** and Claude Code auto-updates with no write to `main`.
> The semver tag/release exists only for the downloadable `noibu.zip` (Claude Desktop +
> the public directory). Do **not** add a `version` field back to `plugin.json` — it would
> re-freeze marketplace updates.
To distribute to all Claude Code users automatically, deploy a managed-settings.json
via MDM with `extraKnownMarketplaces` (pointing at `Noibu/ai-plugin`, `autoUpdate: true`)
and `enabledPlugins: { "noibu@noibu-plugins": true }`.
## How to develop
1. Clone and install the plugin
2. Authenticate with Noibu
## Documentation
https://help.noibu.com/articles/7434601323-installing-the-noibu-plugin-for-claude
## Example Use Cases
### Example 1:
**Spot and act on your top revenue opportunities on autopilot**: Every Monday, surface my highest-impact opportunities
across acquisition, products, and experience, and help me take action on each.
### Example 2:
**Optimize your checkout**: Find where shoppers are dropping off, the payment and delivery methods they're using, and
the technical issues hurting conversion, then tackle the top fixes.
### Example 3:
**Resolve technical issues at the source**: What errors and performance issues are costing my store the most revenue,
and help me resolve them.
### Example 4:
**Uncover and resolve shopper friction**: Surface where real shoppers are struggling, through session replays and
revenue heatmaps, and act on the highest friction.
### Example 5:
**Turn product views into sales**: Find which products and collections are getting views but no sales, diagnose
why they aren't converting, and execute on the biggest opportunities.
**Example 6:
Shift marketing spend with site behaviour**: Surface which campaigns are sending high-quality traffic, identify
how to lift upper-funnel conversion, and reallocate budget accordingly.
## License
MIT
© Noibu · MIT · Noibu/ai-plugin