sherweb-mcp
This MCP server connects AI assistants to Sherweb to manage customers, subscriptions, product catalogs, and billing operations.
Discover tools by domain (billing, customers, subscriptions, catalog) and check credential/domain status.
Billing: retrieve distributor payable charges for a billing period and get full details for a specific charge.
Customers: list/search customers, get one customer by ID, and retrieve a customer's receivable charges for a billing period.
Subscriptions: list a customer's subscriptions, get subscription details (renders an interactive card in MCP Apps hosts), change quantity, and check asynchronous amendment status by tracking ID.
Catalog: list products available to a specific customer, with optional SKU/name search.
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 ecosystem — a growing suite of AI integrations for the MSP stack. Built by MSPs, for MSPs.
Installation
npm install @wyre-ai/sherweb-mcpRelated MCP server: partner-center-mcp
Configuration
Copy .env.example and set the variables below.
Variable | Required | Description |
| For stdio and | Sherweb API client ID |
| For stdio and | Sherweb API client secret |
| For stdio and | Sherweb API subscription key |
| No |
|
| No |
|
| 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 ( |
| No | Set to |
| No | Bind address when |
| No | HTTP port. Defaults to |
/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=<unix seconds>,v1=<hex hmac-sha256>. v1 is HMAC-SHA256 over the exact ASCII string t=<unix seconds>, 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-mcpDocker
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-mcpCompose 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 upSingle-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-mcpLocal 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 startAvailable 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 startContributing
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.
Available Tools
12 toolssherweb_billing_charge_detailsA
Get the full detail of one charge by its ID. Sherweb returns charges only as a billing-period collection, so this reads the period and selects the matching charge.
Inputs: chargeId (required), date.
sherweb_billing_payable_chargesA
Get the distributor payable charges for a billing period. Returns every charge in the period — recurring, usage and setup — with pricing, deductions, fees, taxes and invoice details.
Inputs: date.
sherweb_catalog_list_productsA
List the products a specific customer can be sold, with SKU, localized name and description, billing cycle and commitment term. Catalogs are per-customer in Sherweb — there is no global product list.
Inputs: customerId (required), search.
sherweb_customers_accounts_receivableA
Get the receivable charges you bill a customer for a billing period — recurring, usage and setup charges with cost, quantity and currency.
Inputs: customerId (required), date.
sherweb_customers_getA
Get one customer by ID. Sherweb exposes customers only as a collection, so this reads the list and selects the match.
Inputs: customerId (required).
sherweb_customers_listA
List every customer under your service provider account, with display name, ID, hierarchy path, suspension state and company contact information.
Inputs: search.
sherweb_statusC
Show credentials status and available domains
Inputs: no named parameters.
sherweb_subscriptions_amendment_statusA
Check the status of a submitted subscription amendment using the tracking ID returned by sherweb_subscriptions_change_quantity. Returns Unknown, Queued, Processing, Success or Failure.
Inputs: trackingId (required).
sherweb_subscriptions_change_quantityA
Change a subscription's quantity (seats/licenses). This affects billing. The change is submitted asynchronously — it returns a tracking ID to poll with sherweb_subscriptions_amendment_status, not a finished result.
Inputs: quantity (required), customerId (required), subscriptionId (required).
sherweb_subscriptions_getA
Get one subscription's full details. Sherweb exposes subscriptions only per customer, so this reads that customer's subscription details and selects the match.
Inputs: customerId (required), subscriptionId (required).
sherweb_subscriptions_listA
List a customer's subscriptions with product name, SKU, quantity, billing cycle, purchase date, fees and commitment term.
Inputs: customerId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool targets a clearly distinct resource or action: list/get for customers and subscriptions, payable vs receivable for billing direction, and dedicated tools for charge details, quantity changes, amendment status, catalog products, navigation, and status. There is no meaningful overlap that would cause an agent to select the wrong tool.
All tools share the sherweb_ snake_case prefix and mostly group by domain, but the pattern varies between domain_action (customers_list, subscriptions_get) and domain_noun_phrase (billing_payable_charges, customers_accounts_receivable), with two meta tools (navigate, status) outside the pattern. This is readable but not perfectly uniform.
12 tools is well within the ideal range and appropriately scoped for a Sherweb billing/customer/subscription server. Each domain has a focused set of tools with no obvious bloat or redundancy.
The set covers read operations and subscription quantity changes well, but there are notable gaps: no customer create/update/delete and no subscription purchase/cancel tools. Listing sellable products without a way to actually create a subscription is a significant missing workflow.
Maintenance
Related MCP Connectors
Sherweb Platform MCP server to manage subscriptions and orders. Use OpenID Connect to authenticate.
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
An MCP server that provides access to Agility CMS. See https://mcp.agilitycms.com for more details.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceMCP Server for agents to onboard, pay, and provision services autonomously with InFlow6MIT- AlicenseAqualityCmaintenanceAn MCP server that helps you build against the Partner Center REST API, providing scenario discovery, REST examples, authentication guidance, and error decoding without making live API calls.2962 npm2MIT
- AlicenseAqualityCmaintenanceMCP server for interacting with the SuperOps.ai PSA/RMM platform, providing tools for managing clients, tickets, assets, and technicians via GraphQL API.21Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server for the MSPbots Agent Platform tenant/user API, allowing an Agent to list all platform tenants via a single tool.-