Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Sherweb
Overview
Description from the maker (original English)
MCP server for Sherweb — billing, subscriptions, customers, and product catalog.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
- You need to fill in: SHERWEB_CLIENT_ID, SHERWEB_CLIENT_SECRET, SHERWEB_SUBSCRIPTION_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
SHERWEB_CLIENT_ID,SHERWEB_CLIENT_SECRET,SHERWEB_SUBSCRIPTION_KEY,MCP_TRANSPORT,AUTH_MODE,LOG_LEVEL
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- DockerDocker installed
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"sherweb": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SHERWEB_CLIENT_ID",
"-e",
"SHERWEB_CLIENT_SECRET",
"-e",
"SHERWEB_SUBSCRIPTION_KEY",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-technology/sherweb-mcp:v1.4.3"
],
"env": {
"SHERWEB_CLIENT_ID": "your-value",
"SHERWEB_CLIENT_SECRET": "your-value",
"SHERWEB_SUBSCRIPTION_KEY": "your-value",
"MCP_TRANSPORT": "your-value",
"AUTH_MODE": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add sherweb --env SHERWEB_CLIENT_ID=your-value --env SHERWEB_CLIENT_SECRET=your-value --env SHERWEB_SUBSCRIPTION_KEY=your-value --env MCP_TRANSPORT=your-value --env AUTH_MODE=your-value --env LOG_LEVEL=your-value -- docker run -i --rm -e SHERWEB_CLIENT_ID -e SHERWEB_CLIENT_SECRET -e SHERWEB_SUBSCRIPTION_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/sherweb-mcp:v1.4.3Fill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sherweb": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SHERWEB_CLIENT_ID",
"-e",
"SHERWEB_CLIENT_SECRET",
"-e",
"SHERWEB_SUBSCRIPTION_KEY",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-technology/sherweb-mcp:v1.4.3"
],
"env": {
"SHERWEB_CLIENT_ID": "your-value",
"SHERWEB_CLIENT_SECRET": "your-value",
"SHERWEB_SUBSCRIPTION_KEY": "your-value",
"MCP_TRANSPORT": "your-value",
"AUTH_MODE": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"sherweb": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SHERWEB_CLIENT_ID",
"-e",
"SHERWEB_CLIENT_SECRET",
"-e",
"SHERWEB_SUBSCRIPTION_KEY",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-technology/sherweb-mcp:v1.4.3"
],
"env": {
"SHERWEB_CLIENT_ID": "your-value",
"SHERWEB_CLIENT_SECRET": "your-value",
"SHERWEB_SUBSCRIPTION_KEY": "your-value",
"MCP_TRANSPORT": "your-value",
"AUTH_MODE": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Sherweb OAuth client ID
- Sherweb OAuth client secret
- Sherweb API subscription key
MCP_TRANSPORTenvTransport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.AUTH_MODEenvCredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.LOG_LEVELenvLog verbosity: debug, info, warn, error
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account wyre-technology, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 2535 servers in this category
- Published to the registry more recently than 24% of the other 2535 servers in this category
- Basic checks equal to or better than 100% of the other 2535 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Sherweb safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: SHERWEB_CLIENT_ID, SHERWEB_CLIENT_SECRET, SHERWEB_SUBSCRIPTION_KEY
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.4.3) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Sherweb MCP Server
A Model Context Protocol (MCP) server for Sherweb cloud marketplace and partner portal. Enables AI assistants to manage customer subscriptions, browse the product catalog, and handle billing operations.
This is a Model Context Protocol (MCP) server that connects Claude (or any MCP-compatible AI) to your Sherweb environment.
Part of the [MSP Claude Plugins](https://github.com/WYRE-AI) ecosystem — a growing suite of AI integrations for the MSP stack. Built by MSPs, for MSPs.
Installation
npm install @wyre-ai/sherweb-mcp
Configuration
Copy .env.example and set the variables below.
| Variable | Required | Description |
|---|---|---|
SHERWEB_CLIENT_ID | For stdio and AUTH_MODE=env | Sherweb API client ID |
SHERWEB_CLIENT_SECRET | For stdio and AUTH_MODE=env | Sherweb API client secret |
SHERWEB_SUBSCRIPTION_KEY | For stdio and AUTH_MODE=env | Sherweb API subscription key |
MCP_TRANSPORT | No | stdio (default) or http |
AUTH_MODE | No | gateway (Docker image and Compose default) or env. Gateway mode requires X-Sherweb-Client-ID, X-Sherweb-Client-Secret, and X-Sherweb-Subscription-Key on each /mcp request and never falls back to SHERWEB_*. env uses those variables only after S2S auth succeeds. |
CONDUIT_S2S_SECRET | Yes for HTTP | Service-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, your-s2s-secret, placeholder, secret, and similar copied examples). Compose will not start without it. Never commit a real value. Generate one with openssl rand -hex 32. |
MCP_ALLOW_INSECURE_DEV | No | Set to 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) is ignored and the override is logged. A placeholder secret is still refused. |
MCP_HTTP_HOST | No | Bind address when MCP_TRANSPORT=http and CONDUIT_S2S_SECRET is set. Defaults to 127.0.0.1. The container image sets 0.0.0.0. Without a real secret the listener is 127.0.0.1. |
MCP_HTTP_PORT | No | HTTP port. Defaults to 8080. |
/health and /healthz stay unauthenticated and do not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.
HTTP authentication
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. A missing or invalid header returns 401, before vendor credentials are read. The secret is never written to logs.
The header value is t= ,v1= . v1 is HMAC-SHA256 over the exact ASCII string t= , keyed with CONDUIT_S2S_SECRET, hex-encoded (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock.
t=1710000000,v1=<hmac-sha256("t=1710000000", CONDUIT_S2S_SECRET) as hex>
In AUTH_MODE=gateway, /mcp also requires X-Sherweb-Client-ID, X-Sherweb-Client-Secret, and X-Sherweb-Subscription-Key. Those headers are the only credential source for that request. A request missing any of them returns 401 and does not fall back to SHERWEB_* in the process environment.
Usage
Running with Claude Desktop
Add to your Claude Desktop claude_desktop_config.json:
{
"mcpServers": { "sherweb-mcp": { "command": "npx", "args": ["@wyre-ai/sherweb-mcp"], "env": { "SHERWEB_CLIENT_ID": "your-sherweb-client-id", "SHERWEB_CLIENT_SECRET": "your-sherweb-client-secret", "SHERWEB_SUBSCRIPTION_KEY": "your-sherweb-subscription-key" } } } }
Running with Claude Code (CLI)
claude mcp add sherweb-mcp \
-e SHERWEB_CLIENT_ID=your-value \ -e SHERWEB_CLIENT_SECRET=your-value \ -e SHERWEB_SUBSCRIPTION_KEY=your-value \ -- npx -y @wyre-ai/sherweb-mcp
Docker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, Sherweb credentials arrive on each request as headers; they are not read from the environment.
docker build -t sherweb-mcp .
docker run \ -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \ -p 127.0.0.1:8080:8080 \ sherweb-mcp
Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, publishes 127.0.0.1:8080:8080, and does not pass SHERWEB_CLIENT_ID, SHERWEB_CLIENT_SECRET, or SHERWEB_SUBSCRIPTION_KEY into the container:
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses SHERWEB_*:
docker run \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \ -e AUTH_MODE=env \ -e SHERWEB_CLIENT_ID=your-value \ -e SHERWEB_CLIENT_SECRET=your-value \ -e SHERWEB_SUBSCRIPTION_KEY=your-value \ -p 127.0.0.1:8080:8080 \ sherweb-mcp
Local HTTP without a secret is development-only. It binds 127.0.0.1 only (a wider MCP_HTTP_HOST is ignored) and logs a warning:
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm start
Available Domains
Billing
Distributor payable charges for a billing period, and detail for an individual charge. Sherweb returns charges only as a per-period collection, so both tools take an optional date identifying the period.
Catalog
Browse the products a given customer can be sold. Catalogs are per-customer in Sherweb — there is no global product list — so customerId is required.
Customers
List and look up customers, and read the receivable charges you bill them for a billing period.
Subscriptions
List a customer's subscriptions, get one subscription's details, and submit quantity amendments. Amendments are asynchronous: submitting returns a tracking ID, and sherweb_subscriptions_amendment_status reports the outcome.
Interactive Subscription Card (MCP Apps)
sherweb_subscriptions_get renders as an interactive, read-only card in MCP Apps hosts (Claude Desktop/web) showing the product, customer, status, quantity, billing cycle, commitment/renewal dates, and fees; plain-JSON behavior is unchanged in other hosts. The card is neutral by default and brandable via window.__BRAND__ injection or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL, MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG, MCP_BRAND_TEXT) — no rebuild needed.
Development
# Clone the repository
git clone https://github.com/WYRE-AI/sherweb-mcp.git cd sherweb-mcp
Install dependencies
npm install
Build
npm run build
Run tests
npm test
HTTP transport refuses to start until CONDUIT_S2S_SECRET is set
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" MCP_TRANSPORT=http npm start
Local HTTP only, without a service-to-service secret (always binds 127.0.0.1)
MCP_ALLOW_INSECURE_DEV=1 MCP_TRANSPORT=http npm start
Contributing
Contributions are welcome! Please see CONTRIBUTING.md if present, or open an issue to discuss changes.
License
Licensed under the Apache License, Version 2.0. See LICENSE for details.