sherweb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport mode: stdio (default) or http | stdio |
| SHERWEB_CLIENT_ID | Yes | Your Sherweb API client ID | |
| SHERWEB_CLIENT_SECRET | Yes | Your Sherweb API client secret | |
| SHERWEB_SUBSCRIPTION_KEY | Yes | Your Sherweb subscription key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sherweb_navigateA | Discover available Sherweb tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite. |
| sherweb_statusC | Show credentials status and available domains |
| 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. |
| sherweb_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. |
| sherweb_customers_listA | List every customer under your service provider account, with display name, ID, hierarchy path, suspension state and company contact information. |
| sherweb_customers_getA | Get one customer by ID. Sherweb exposes customers only as a collection, so this reads the list and selects the match. |
| 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. |
| sherweb_subscriptions_listA | List a customer's subscriptions with product name, SKU, quantity, billing cycle, purchase date, fees and commitment term. |
| 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. |
| 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. |
| 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. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Sherweb Subscription Card | Interactive MCP Apps card rendering a Sherweb customer subscription |
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.