Diff and sync Shopify stores: dry-run plans, cross-store ID remapping, never deletes.
CommerceWeave is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Local MCP server for Allegro, Base.com and WooCommerce. Read-only by default, human-approved writes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user commerceweave-mcp '--' npx -y commerceweave-mcp
# 2 — ask your agent for something these tools do
# allegro_get_account_info, allegro_list_offers, allegro_search_offers and 40 more
CommerceWeave costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts CommerceWeave as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user commerceweave-mcp '--' npx -y commerceweave-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take COMMERCEWEAVE_MODE (read_only (default) | proposal | approval_required), COMMERCEWEAVE_DEMO (true = synthetic demo data, no credentials needed), ALLEGRO_ENABLED (true to enable the Allegro connection), ALLEGRO_ENVIRONMENT (sandbox | production), ALLEGRO_CLIENT_ID (Allegro application client id), ALLEGRO_CLIENT_SECRET (Allegro application client secret), BASE_ENABLED (true to enable the Base.com connection), BASE_API_TOKEN (Base.com API token (sent as X-BLToken)), WOO_ENABLED (true to enable the WooCommerce connection), WOO_STORE_URL (https URL of the WooCommerce store), WOO_CONSUMER_KEY (WooCommerce REST API consumer key), WOO_CONSUMER_SECRET (WooCommerce REST API consumer secret) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
43 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Returns the authorized Allegro account (login, id, environment). Use to verify which account and sandbox/production a connection points to.
No parameter schema on file.
Lists the seller's Allegro offers (id, name, status, buy-now price, available stock), paginated.
No parameter schema on file.
Filters the seller's offers by name, publication status (INACTIVE, ACTIVATING, ACTIVE, ENDED), buy-now price range or offer id.
No parameter schema on file.
Returns key data of one offer (status, stock, buy-now price, external id).
No parameter schema on file.
Returns the available stock quantity of one offer.
No parameter schema on file.
Returns the buy-now price (exact decimal string + currency) and selling format of one offer.
No parameter schema on file.
Lists Allegro orders (checkout forms) for a local day, last N days or explicit range. Personal data masked by default.
No parameter schema on file.
Returns one Allegro order (checkout form) with items and status.
No parameter schema on file.
Reads the Allegro order event stream (BOUGHT, FILLED_IN, READY_FOR_PROCESSING, BUYER_CANCELLED, FULFILLMENT_STATUS_CHANGED, ...). Pass the last seen event id as from to continue.
No parameter schema on file.
Lists Base.com catalogs (inventories) with their warehouses and price groups. Catalogs, warehouses and order sources are separate concepts; use these ids for stock/price tools.
No parameter schema on file.
Lists products of one Base catalog (id, SKU, EAN, name, gross prices per price group, stock per warehouse). Variants are grouped under their parent. Base returns up to 1000 products per page.
No parameter schema on file.
Returns stock (and reservations where enabled) per warehouse for one product or one page of a catalog. Warehouse ids look like bl_123.
No parameter schema on file.
Returns gross prices per price group for products of a catalog (one page). Base does not report currencies here.
No parameter schema on file.
Lists confirmed Base orders for a local day, last N days or range. Orders imported from marketplaces carry importedFrom. Personal data masked by default.
No parameter schema on file.
Returns one Base order by id (including unconfirmed ones).
No parameter schema on file.
Lists the account's custom order statuses (ids and names).
No parameter schema on file.
Reads the Base order event journal (creation, payment, status change, ...) after a given log id.
No parameter schema on file.
Lists WooCommerce products (REST API v3) with SKU, regular/sale price, stock. Variable products can include their variations.
No parameter schema on file.
Searches products by free text and/or exact SKU.
No parameter schema on file.
Returns one product; variable products include variations with their own stock and price.
No parameter schema on file.
Returns the variations of a variable product. Each variation has its own id, SKU, price and stock.
No parameter schema on file.
Returns stock of a product or of one variation. total=null means stock is not managed by quantity (or is inherited from the parent).
No parameter schema on file.
Lists product categories (first 100).
No parameter schema on file.
Lists WooCommerce orders for a local day, last N days or range. Personal data masked by default.
No parameter schema on file.
Returns one WooCommerce order.
No parameter schema on file.
Returns WooCommerce's own aggregated sales report for a date range (YYYY-MM-DD). Figures follow WooCommerce's definitions (net of refunds) and may differ from commerce_sales_summary; revenue is not profit. If the report endpoint is unavailable the error says so; use commerce_sales_summary instead.
No parameter schema on file.
Lists configured store connections (Allegro, Base.com, WooCommerce) with ids, platform, environment, write capability and the active safety mode. Never returns credentials. Call this first to learn valid connection ids.
No parameter schema on file.
Lists products/offers in a normalized shape (source ids, SKU, EAN, gross prices, stock, variants). Pages are per connection: one connection per call is recommended for large catalogs. Stock total is null when the platform does not manage a quantity. Base prices carry no currency (null).
No parameter schema on file.
Looks for the same product on several platforms by SKU, EAN or name. SKU matches are exact; name search is a substring match. Matches are candidates only: SKUs may be missing or reused, so confirm identity before using a result as a write target.
No parameter schema on file.
Lists orders from all (or selected) connections for a local day, last N days, or an explicit range, normalized and de-duplicated: orders imported from another platform are flagged with duplicate (status "confirmed" = same sale proven by ids, "potential" = unproven). Personal data is masked…
No parameter schema on file.
Fetches one order by its platform id from a specific connection, normalized. Personal data is masked unless includePersonalData=true.
No parameter schema on file.
Lists sellable items (variants individually) with stock <= threshold on each connection, lowest first. Items whose platform does not manage a quantity are skipped and counted, never treated as zero. Reports which connections were incomplete or failed.
No parameter schema on file.
Per-connection inventory summary: number of sellable items, total units, out-of-stock, low-stock and unmanaged counts. Units are not summed across platforms because the same stock may be published in several places.
No parameter schema on file.
Gross revenue and order counts per currency and connection for a period. Confirmed imported duplicates (e.g. Base orders imported from Allegro) are excluded; potential duplicates are included but reported separately. Cancelled, refunded and (by default) unpaid orders are excluded. This is revenue,…
No parameter schema on file.
Compares stock for the same product on several connections. Pairs items by explicit config mapping first, then by SKU/EAN only when unique in each store; ambiguous or unmatched items are listed rather than guessed. Changes nothing. Optionally pass sourceOfTruth (a connection id) to get suggested…
No parameter schema on file.
Reads current stock, then records a reviewable proposal with before/after values. NOTHING IS CHANGED ON THE PLATFORM. connectionId is mandatory. Targets that are ambiguous (variable product without variantId, several Base warehouses/catalogs) are rejected. A human must approve the exact plan…
No parameter schema on file.
Computes new prices with exact decimal arithmetic from the live current price (newPrice or changePercent per item) and records a reviewable proposal with before/after and the difference. NOTHING IS CHANGED ON THE PLATFORM. Woo changes the regular price only (warns if a sale price exists). A human…
No parameter schema on file.
Validates the target status against the platform (Allegro fulfillment status, Base status id, Woo status), reads the current status and records a reviewable proposal. NOTHING IS CHANGED ON THE PLATFORM. A human must approve the exact plan out-of-band.
No parameter schema on file.
Records a proposal to add a short internal note (max 190 chars, plain text) to an order. WooCommerce: private staff note, never sent to the customer. Base.com: appended to the seller comment (200 char limit). Allegro is not supported. NOTHING IS CHANGED ON THE PLATFORM until a human approves.
No parameter schema on file.
Records a proposal to ACTIVATE (publish; may incur Allegro fees) or END an Allegro offer. Allegro only. Runs through the async publication command API after human approval. NOTHING IS CHANGED UNTIL A HUMAN APPROVES.
No parameter schema on file.
Records a proposal to create a NEW product that is not live anywhere: WooCommerce = simple product in DRAFT status; Base.com = catalog product not linked to any marketplace (catalogId / priceGroup / locationId required when several exist). SKU is required and must not exist yet; existing products…
No parameter schema on file.
Shows a stored proposal: plan, status (pending/executing/executed/failed), expiry and execution result.
No parameter schema on file.
Executes a proposal ONLY if a human approved that exact plan in a separate terminal (commerceweave-mcp approve <id>). There is no way for the model to grant approval. Re-reads live state first and aborts if anything drifted; runs once; verifies results by reading back; writes an audit entry.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CommerceWeave or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish CommerceWeave can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.