medusa-mcp
You can run and analyze a Medusa v2 store through MCP clients with read/write tools, reports, prompts, resources, and interactive dashboards.
Read/analyze: store info, orders, customers, customer groups, products, catalog, inventory, promotions, price lists, and sales/customer/inventory reports.
Orders/fulfillment: create fulfillments/shipments, mark delivered, cancel fulfillments, update/complete/cancel orders, and edit order items.
Payments/returns: mark orders paid, capture/refund payments, create/receive returns.
Draft orders: create and convert draft orders.
Products/catalog: create/update/delete products, variants, prices, categories, collections, and product images.
Inventory: list stock and set/adjust stock levels.
Customers/groups: create/update customers and customer groups, delete groups.
Promotions/pricing: create/update/delete promotions, manage price lists, and run bulk price/stock/product updates with dry-run previews.
Generic API: call allowed
/admin/endpoints viamedusa_requestfor gaps like reservations, exchanges, tax rates.Extras: inline sales/restock dashboards, workflow prompts, attachable resources, destructive-action confirmations, audit logging, stdio local mode, and remote HTTP/OAuth mode.
Provides tools for interacting with the Medusa v2 Admin API, enabling access to orders, customers, products, inventory, and sales reports, plus scoped write actions such as fulfilling and shipping orders, completing or cancelling orders, updating or deleting products, setting variant prices, and restocking inventory.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@medusa-mcp list products that are running low on stock"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
medusa-mcp
π¨πΏ Δesky
An MCP server for the Medusa v2 Admin API. It lets Claude, ChatGPT or any MCP client run a Medusa store: orders, payments and refunds, returns, order edits, draft orders, products and catalog, inventory, customers, promotions and price lists β plus sales, customer and restock analytics with interactive dashboards right in the chat.
55 tools for day-to-day store management, and
medusa_requestfor any other Admin API endpointInteractive views (MCP Apps) β a sales dashboard and a restock planner render inline in Claude and ChatGPT
Prompts β ready-made workflows (store briefing, fulfillment, returns, restocking, monthly reportβ¦) as slash commands
Resources β orders, products and customers as attachable context, with autocompletion
Guard rails β previews (dry run) for bulk changes, confirmation dialogs for destructive actions, an audit log of every change
It runs in two modes:
stdio β locally for Claude Desktop, Claude Code and other MCP clients
Streamable HTTP + OAuth 2.1 β as a remote connector for Claude (web, desktop, mobile) and ChatGPT
It is listed in the MCP Registry as io.github.trhonpavel/medusa-mcp, and also ships as a Claude Code / Cowork plugin with skills and as a one-click Claude Desktop extension (.mcpb).
Tools
Read and analyze
Tool | What it does |
| regions and currencies, sales channels, stock locations, shipping options and profiles, return and refund reasons |
| orders by full-text, date range, customer or status; full detail by ID or order number ( |
| customers (also by group or e-mail), order history, total spent |
| customer groups |
| products by status, collection, category or tag; variants, options, prices, images, inventory items (by ID or handle) |
| categories (tree), collections, tags, product types |
| stock per location, |
| discount codes with conditions, usage and validity; sale and customer-group price lists |
| revenue, net revenue after refunds, AOV, units, customers β compared with the previous period or last year, day/week/month series, top products and variants, countries, discount codes, sales channels Β· interactive dashboard |
| new vs returning customers, repeat purchase rate, top customers, lapsed customers worth winning back |
| sales velocity vs stock: days of cover, out-of-stock / reorder-now / reorder-soon, suggested order quantities, slow movers Β· interactive restock planner |
Write (not registered with MEDUSA_READ_ONLY=true)
Area | Tools |
Fulfillment |
|
Orders |
|
Payments |
|
Returns |
|
Draft orders |
|
Products |
|
Variants |
|
Catalog |
|
Inventory |
|
Customers |
|
Promotions |
|
Price lists |
|
Bulk |
|
Generic
Tool | What it does |
| any Admin API endpoint ( |
Amounts are in major currency units (Medusa v2 does not store minor units). Plain dates (2026-09-01) are interpreted in REPORT_TIMEZONE (default UTC). Large reports send MCP progress notifications.
Fewer tools, less context: MEDUSA_TOOLSETS=orders,reports registers only those groups (orders, customers, products, catalog, inventory, pricing, promotions, reports, bulk, raw; get_store_info is always on).
Related MCP server: WIBI MCP Gateway
Beyond tools
Interactive views (MCP Apps). sales_report and inventory_forecast come with HTML views that clients supporting MCP Apps β Claude, ChatGPT, VS Code, Goose β render inline: KPI tiles with period-over-period changes, a revenue chart, top products, discount codes and countries; and a sortable restock table with status filters, adjustable lead time and a button that asks the assistant to draft a purchase order. The views follow the client's theme and language (Czech or English), switch periods by calling the tools themselves, and make no network requests of their own. Other clients get the same data as text.
Prompts. store_briefing, fulfill_orders, restock_plan, handle_return, customer_overview, monthly_report and plan_promotion β each walks the assistant through a whole workflow and asks before changing anything. Arguments autocomplete (order numbers, customer e-mails, months).
Resources. medusa://store, medusa://orders/{order}, medusa://products/{handle} and medusa://customers/{email} β attach an order or a product to the conversation (e.g. with @ in Claude Code); recent orders are listed and every template autocompletes.
Confirmations. Destructive actions β canceling, refunding, capturing, deleting, bulk changes and writes through medusa_request β ask the user directly through MCP elicitation with a plain-language summary ("Refund 249 CZK to the customer of order 1042?") when the client supports it (Claude Code). A declined dialog changes nothing. Turn it off with MEDUSA_CONFIRM_DESTRUCTIVE=false. The stateless remote connector cannot elicit, so there the client's own tool approval applies.
1. Create a Medusa API key
In the Medusa Admin go to Settings β Developer β Secret API Keys β Create. The key (sk_β¦) acts with the permissions of the user who created it, so consider a dedicated admin user that you can revoke independently.
2. Local use (stdio)
Claude Code / Cowork plugin
claude plugin marketplace add trhonpavel/medusa-mcp
claude plugin install medusa@medusa-mcpClaude Code asks for the backend URL and the API key when you enable the plugin (the key goes to the system keychain). Write tools stay off until you turn off Read-only in /config. Besides the server's prompts, the plugin adds two skills:
store-briefingβ sales vs the previous period, paid orders waiting to ship, what to restockfulfill-ordersβ fulfill paid orders and add tracking numbers, after you confirm the list
Claude Desktop extension
Download medusa-mcp-<version>.mcpb from the latest release and open it, or drag it to Settings β Extensions. Claude Desktop asks for the same settings and runs the server with its bundled Node.js. Build it yourself with npm run build:mcpb.
Manual configuration
Claude Desktop β claude_desktop_config.json:
{
"mcpServers": {
"medusa": {
"command": "npx",
"args": ["-y", "medusa-mcp", "stdio"],
"env": {
"MEDUSA_BACKEND_URL": "https://api.example.com",
"MEDUSA_API_KEY": "sk_...",
"MEDUSA_READ_ONLY": "true"
}
}
}
}Claude Code:
claude mcp add medusa \
-e MEDUSA_BACKEND_URL=https://api.example.com -e MEDUSA_API_KEY=sk_... \
-- npx -y medusa-mcp stdio3. Remote connector (HTTP + OAuth)
docker run -d --name medusa-mcp -p 127.0.0.1:3000:3000 -v medusa-mcp-data:/data \
-e MEDUSA_BACKEND_URL=https://api.example.com \
-e MEDUSA_API_KEY=sk_... \
-e PUBLIC_URL=https://mcp.example.com \
-e OWNER_PASSWORD="$(openssl rand -base64 24)" \
ghcr.io/trhonpavel/medusa-mcp:latestOr clone the repo, copy .env.example to .env and run docker compose up -d --build.
The server listens on 127.0.0.1:3000; expose it through a reverse proxy with TLS. Claude connects to remote connectors from Anthropic's servers, so the endpoint must be publicly reachable over HTTPS. Caddy example:
mcp.example.com {
reverse_proxy 127.0.0.1:3000
}Then add a custom connector in Claude with the URL https://mcp.example.com/mcp. Claude registers itself (Dynamic Client Registration), opens the consent page, you enter OWNER_PASSWORD and click Allow.
ChatGPT
In ChatGPT turn on developer mode in the settings, then create an app (connector) with the MCP server URL https://mcp.example.com/mcp and OAuth authentication. ChatGPT registers itself the same way and redirects to chatgpt.com, which is in the default ALLOWED_REDIRECT_HOSTS. The server returns the RFC 9207 iss parameter, so ChatGPT uses its stable callback URL.
Claude Code
Claude Code can use the same OAuth flow, or a static token if you set MCP_STATIC_TOKEN:
claude mcp add --transport http medusa https://mcp.example.com/mcp \
--header "Authorization: Bearer <MCP_STATIC_TOKEN>"Configuration
Variable | Required | Default | Description |
| yes | Medusa backend URL | |
| yes | Secret API key ( | |
|
| Register read and report tools only | |
|
| Register the generic | |
| all | Comma-separated tool groups to register, e.g. | |
|
| Ask for confirmation through MCP elicitation before destructive actions (clients that support it) | |
| File that receives every write tool call as a JSON line (they always go to stderr too) | ||
|
| IANA timezone for date filters and report buckets | |
|
| Timeout for Medusa requests | |
| HTTP | Public HTTPS origin of this server (without | |
| HTTP | Password required on the consent page | |
| Optional static bearer token | ||
|
| Hosts OAuth clients may use as redirect targets | |
|
| Express | |
|
| Listen address | |
|
| Where OAuth clients and token hashes are stored | |
|
| Token lifetimes in seconds |
Endpoints
Path | Purpose |
| MCP over Streamable HTTP (stateless), requires a bearer token |
| RFC 9728 protected resource metadata |
| RFC 8414 authorization server metadata |
| OAuth 2.1 (DCR, PKCE S256) |
| consent form (rate limited: 10 attempts / 15 min / IP) |
| health check |
Security model
The Medusa API key never leaves the server. Clients get their own short-lived tokens (1 h access, 30-day refresh with rotation).
Only SHA-256 hashes of tokens are stored, in
DATA_DIR/oauth-state.json(mode 600). Delete the file to sign out every client.Dynamic Client Registration only accepts redirect URIs on
ALLOWED_REDIRECT_HOSTS, so an arbitrary app cannot register its own callback and phish a token.Authorization codes are single-use, expire after 5 minutes, and PKCE S256 is mandatory.
The consent page sends
Content-Security-Policy: default-src 'none'andX-Frame-Options: DENY, and compares the password in constant time.Write tools are not marked
readOnlyHint, and tools that cancel, delete or move money carrydestructiveHint, so clients like Claude ask for approval before running them.medusa_requestonly reaches/admin/β¦paths, never writes toapi-keys,usersorinvites(so a prompt injection cannot mint new credentials), and can be disabled withMEDUSA_RAW_API=false.Every write tool call is logged as
[audit] {β¦}on stderr (docker logs) β time, tool, OAuth client (e.g. "Claude"), outcome and arguments β and toAUDIT_LOGwhen set.Destructive actions ask for confirmation through MCP elicitation when the client supports it; bulk tools and
edit_orderpreview by default and change nothing until called withdry_run: false.add_product_imagesdownloads only from public http(s) addresses: private, loopback and link-local targets are refused, also after redirects, so the server cannot be used to reach its own network.The interactive views are self-contained HTML (no external scripts or requests) and are rendered by the client in a sandboxed iframe.
Set
TRUST_PROXYto the number of reverse proxies in front of the server, otherwise rate limiting only sees the proxy's IP.
See SECURITY.md for reporting vulnerabilities.
Development
npm ci
npm run build # TypeScript + the MCP Apps views (dist/apps/*.html with the ext-apps runtime inlined)
npm test # build + tests against a mock Medusa (tools, prompts, resources, views and the full OAuth flow)
npm run smoke # read-only check against a real Medusa β prints response shapes only, no data
npm run dev # HTTP mode via tsxnpm run smoke needs MEDUSA_BACKEND_URL and MEDUSA_API_KEY. Its output contains only keys and types, so it is safe to paste into an issue.
License
Available Tools
48 toolscancel_fulfillmentCancel fulfillmentADestructive
Cancels a fulfillment that has not been shipped yet, so its items can be fulfilled again. Without 'fulfillment_id' it uses the only unshipped fulfillment.
Inputs: order (required), fulfillment_id, notify_customer.
cancel_orderCancel orderADestructiveIdempotent
CANCELS the order. Irreversible β get explicit confirmation from the user before calling. The order must not have active fulfillments.
Inputs: order (required).
capture_paymentCapture paymentADestructive
Captures an authorized payment (charges the customer). Without 'amount' captures the full remaining amount. Without 'payment_id' uses the only payment that is not fully captured.
Inputs: order (required), amount, payment_id.
complete_orderComplete orderCIdempotent
Marks the order as completed.
Inputs: order (required).
convert_draft_orderConvert draft orderA
Turns a draft order into a regular order (reserves stock). Record the payment afterwards with mark_order_paid.
Inputs: draft_order_id (required).
create_draft_orderCreate draft orderA
Creates a draft order on behalf of a customer (phone or e-mail orders, B2B). Items by variant_id or SKU (of published products), optionally with a custom unit price. Shipping options are listed by get_store_info. Turn the draft into a real order with convert_draft_order.
Inputs: items (required), email, region_id, customer_id, +6 more.
create_fulfillmentCreate fulfillmentA
Creates a fulfillment for an order. Without 'items' it fulfills all remaining unfulfilled quantities. Without 'location_id' it uses the only stock location, if there is exactly one.
Inputs: order (required), items, location_id, notify_customer.
create_productCreate productA
Creates a product with its variants and prices. For a simple product without options pass just 'prices' (and optionally 'sku', 'stock'). For variants define 'options' (e.g. Size: S, M, L) and one variant per combination. Defaults: status draft, the store's default sales channel, the default shipping profile. Category and collection IDs come from list_catalog.
Inputs: title (required), sku, tags, stock, +17 more.
create_promotionCreate promotionA
Creates a discount code (or an automatic promotion): percentage or fixed amount off the order, specific products, or shipping. Free shipping = applies_to 'shipping', percentage 100. Restricting to products/categories/collections makes it apply to those items only. Plain dates are interpreted in the reporting timezone.
Inputs: code (required), value (required), discount_type (required), status, +13 more.
create_returnCreate returnA
Requests a return of order items (the customer is sending them back). Without 'items' returns every shipped item. When the parcel arrives, call receive_return. Refund the money separately with refund_payment. Return reasons are listed by get_store_info.
Inputs: order (required), note, items, location_id, +1 more.
create_shipmentMark as shippedB
Marks a fulfillment as shipped and attaches a tracking number. Without 'fulfillment_id' it uses the only unshipped fulfillment.
Inputs: order (required), tracking_url, fulfillment_id, notify_customer, +1 more.
create_variantCreate variantA
Adds a variant to an existing product, e.g. a new size. 'options' must name every product option; new option values are added automatically.
Inputs: prices (required), product_id (required), ean, sku, +9 more.
delete_categoryDelete categoryADestructiveIdempotent
DELETES a product category (products stay, they just lose the category). Confirm with the user first.
Inputs: category_id (required).
delete_collectionDelete collectionADestructiveIdempotent
DELETES a collection (products stay, they just leave the collection). Confirm with the user first.
Inputs: collection_id (required).
delete_customer_groupDelete customer groupADestructiveIdempotent
DELETES a customer group (the customers stay). Price lists and promotions targeting it stop applying. Confirm with the user first.
Inputs: group_id (required).
delete_price_listDelete price listADestructiveIdempotent
DELETES a price list β its prices stop applying immediately. Confirm with the user first.
Inputs: price_list_id (required).
delete_productDelete productADestructiveIdempotent
DELETES the product with all its variants. Irreversible β get explicit confirmation from the user before calling. 'confirm_title' must match the product title exactly. By default the inventory items of its variants are deleted too (only those with nothing reserved).
Inputs: product_id (required), confirm_title (required), delete_inventory_items.
delete_promotionDelete promotionADestructiveIdempotent
DELETES a promotion β the code stops working. To pause it, prefer update_promotion with status 'inactive'. Confirm with the user first. A campaign created for its dates (named after the code) is deleted too.
Inputs: code, promotion_id.
delete_variantDelete variantADestructiveIdempotent
DELETES one variant of a product. Irreversible β confirm with the user first. 'confirm' must equal the variant's SKU (or its title when it has no SKU). By default its inventory item is deleted too (only when nothing is reserved).
Inputs: confirm (required), product_id (required), variant_id (required), delete_inventory_items.
get_customerGet customerARead-only
Customer detail with addresses, groups and order history (count, total spent, recent orders).
Inputs: customer_id (required).
get_orderGet orderARead-only
Full order detail β line items, addresses, payments (with captures and refunds), fulfillments, tracking numbers and returns. Accepts an order ID (order_β¦) or the order number.
Inputs: order (required).
get_productGet productBRead-only
Product detail β variants, prices in all currencies, linked inventory items, options, categories, collection, tags, images and sales channels.
Inputs: product_id (required).
get_store_infoStore overviewARead-only
Returns regions (currencies), sales channels, stock locations, shipping options and profiles, and return/refund reasons. A good first call to learn the IDs other tools need.
Inputs: no named parameters.
list_catalogCatalog structureBRead-only
Product categories (with parent, so the tree can be rebuilt), collections, tags and product types β with IDs for other tools.
Inputs: q.
list_customer_groupsList customer groupsCRead-only
Customer groups (e.g. B2B, VIP) β used by price lists and promotions.
Inputs: q, limit, offset.
list_customersList customersBRead-only
Searches customers by name, email or company, optionally within a customer group.
Inputs: q, email, limit, offset, +2 more.
list_inventoryInventory levelsBRead-only
Inventory items with stock per location (stocked, reserved, available). With low_stock_threshold returns only items at or below the threshold.
Inputs: q, sku, limit, offset, +2 more.
list_ordersList ordersARead-only
Lists orders, newest first. Filters: full-text, date range (YYYY-MM-DD in the reporting timezone), customer, order/payment/fulfillment status.
Inputs: q, limit, offset, status, +5 more.
list_price_listsList price listsBRead-only
Price lists β sales (temporary discounted prices) and overrides (e.g. B2B prices for a customer group). With price_list_id returns that list including all its prices.
Inputs: q, limit, offset, status, +1 more.
list_productsList productsARead-only
Lists products with their variants (SKUs). Filter by full-text, status, collection, category or tag.
Inputs: q, limit, offset, status, +3 more.
list_promotionsList promotionsBRead-only
Discount codes and automatic promotions with their value, conditions, usage and validity.
Inputs: q, code, limit, offset.
mark_deliveredMark as deliveredAIdempotent
Marks a fulfillment as delivered. Without 'fulfillment_id' it uses the only fulfillment that is not delivered yet.
Inputs: order (required), fulfillment_id.
mark_order_paidMark order as paidAIdempotent
Records a manual payment (e.g. a received bank transfer or cash on delivery) for the order's unpaid payment collection. Orders without one (e.g. converted draft orders) get a payment collection for the outstanding amount first.
Inputs: order (required).
medusa_requestMedusa Admin API requestADestructive
Calls any Medusa v2 Admin API endpoint directly β for anything the other tools do not cover (e.g. /admin/reservations, /admin/order-edits, /admin/exchanges, /admin/tax-rates, /admin/shipping-options). Prefer the dedicated tools when one fits. Amounts are in major units. Use 'fields' in the query to choose fields: '+field' adds to the defaults, '*relation' expands a relation. POST creates or updates, DELETE deletes β confirm changes with the user first. Writes to api-keys, users and invites are blocked.
Inputs: path (required), body, query, method.
receive_returnReceive returnA
Records that returned items arrived; they go back to stock. Without 'items' receives everything requested. Without 'return_id' uses the order's only open return.
Inputs: note, items, order, return_id, +1 more.
refund_paymentRefund paymentADestructive
REFUNDS money to the customer through the payment provider. Irreversible β confirm the amount with the user before calling. Without 'payment_id' uses the only captured payment that can cover the amount. Refund reasons are listed by get_store_info.
Inputs: order (required), amount (required), note, payment_id, +1 more.
sales_reportSales reportARead-only
Computes sales for a period: order count, revenue, average order value, units sold, unique customers, a time series (day/week/month) and top products. Amounts are per currency. Canceled and draft orders are excluded.
Inputs: to (required), from (required), top_n, group_by, +2 more.
save_categoryCreate or update categoryAIdempotent
Without category_id creates a product category (name required); with category_id updates only the given fields. Can also add or remove products.
Inputs: name, rank, handle, metadata, +7 more.
save_collectionCreate or update collectionAIdempotent
Without collection_id creates a collection (title required); with collection_id updates it. Can add or remove products (a product belongs to at most one collection).
Inputs: title, handle, metadata, add_products, +2 more.
save_customerCreate or update customerAIdempotent
Without customer_id creates a customer (email required); with customer_id updates only the given fields. Can also add an address and add/remove the customer from groups.
Inputs: email, phone, metadata, last_name, +6 more.
save_customer_groupCreate or update customer groupAIdempotent
Without group_id creates a group (name required); with group_id renames it. Can add/remove customers.
Inputs: name, group_id, metadata, add_customers, +1 more.
save_price_listCreate or update price listAIdempotent
Without price_list_id creates a price list (title required); with price_list_id updates it. 'set_prices' adds or changes the price of a variant in a currency; 'remove_variants' drops variants from the list. type 'sale' shows the original price struck through, 'override' simply replaces it. Plain dates use the reporting timezone.
Inputs: type, title, status, ends_at, +6 more.
set_stock_levelSet stock levelA
Sets the stocked quantity of an item at a location. Provide either an absolute 'stocked_quantity' or a relative 'adjust_by' (+/-). Identify the item by inventory_item_id or SKU. Without location_id the item's only location is used. If the item is not stocked at the given location yet, it is added there.
Inputs: sku, adjust_by, location_id, stocked_quantity, +1 more.
set_variant_priceSet variant priceAIdempotent
Sets the base price (no price rules) of a variant in one currency. All other prices of the variant are preserved. The amount is in major currency units (e.g. 49.99 = 49.99 EUR). For sale or customer-group prices use price lists.
Inputs: amount (required), product_id (required), variant_id (required), currency_code (required).
update_orderUpdate orderAIdempotent
Changes the order's email, shipping or billing address, or metadata (e.g. an internal note). Send only what should change; an address replaces the whole previous address.
Inputs: order (required), email, metadata, billing_address, +1 more.
update_productUpdate productAIdempotent
Updates product fields β texts, status, handle, images, collection, categories, tags, sales channels, metadata. Send only the fields that should change. Lists (category_ids, tags, images, sales_channel_ids) replace the previous list.
Inputs: product_id (required), tags, title, handle, +12 more.
update_promotionUpdate promotionAIdempotent
Changes a promotion: activate/deactivate (status), rename the code, change the value, usage limit or validity dates. Identify it by promotion_id or code.
Inputs: code, value, status, ends_at, +4 more.
update_variantUpdate variantAIdempotent
Updates variant fields β title, SKU, barcodes, inventory tracking, backorders, weight, metadata. For prices use set_variant_price.
Inputs: product_id (required), variant_id (required), ean, sku, +7 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 48 tools
Despite 48 tools, each targets a distinct resource-action pair. Fulfillment, payment, and return tool families are clearly delineated by verbs (create, mark, cancel, capture, refund, receive), and the generic medusa_request is explicitly a fallback. No two tools appear to do the same thing.
The set uses snake_case throughout with a dominant verb_noun pattern, but it mixes upsert conventions: some resources use save_* for create/update (save_collection, save_customer) while others use separate create_* and update_* (create_product, update_product). Two tools (sales_report, medusa_request) are noun-only, breaking the strict verb_noun pattern. This is mostly consistent but not perfectly uniform.
48 tools far exceeds the 16β25 'heavy' threshold and is close to the 50+ extreme. While the Medusa admin domain is broad, the count imposes high selection overhead; a generic medusa_request already provides an escape hatch, so many CRUD tools could be consolidated.
Core lifecycle coverage is strong for orders, products, variants, customers, categories, collections, inventory, price lists, and promotions. Notable gaps include no dedicated delete_customer or order edit/claim/exchange tools, but medusa_request lets agents work around these gaps, so the surface is largely complete.
Maintenance
Related MCP Connectors
Talk to your public-facing AI from any MCP client β Claude, ChatGPT, Cursor, Cline, Windsurf.
Hosted Amazon Seller Central and Amazon Ads MCP server for Claude, ChatGPT, Cursor, and agents.
MCP server for Argo RPG Platform β connects AI assistants to campaign data via OAuth2
Hosted WooCommerce MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Related MCP Servers
- AlicenseBqualityDmaintenanceA minimal local MCP server that wraps any Claude Messages API-compatible upstream into a unified ask_model tool. It enables MCP clients to interact with these models through a standard tool interface using stdio transport.17MIT
- FlicenseNot gradedqualityCmaintenanceMCP server exposing WIBI's API v2 as tools, supporting OAuth 2.1 for production (Claude web/desktop) and stdio for local dev, enabling natural-language queries about campaigns, products, clients, reports, broadcasts, and subscriptions with per-commerce isolation and admin scope switching.-
- FlicenseNot gradedqualityCmaintenanceProvides a production-oriented MCP server exposing tools, resources, and prompts over Streamable HTTP with JWT authentication and per-tool RBAC, enabling Amazon Bedrock Claude clients to securely invoke MCP capabilities.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to read feeds, search, browse full comment trees, and look up users, while performing guarded write actions like posting, replying, editing, voting, saving, and joining or leaving subreddits. Runs over stdio or HTTP with confirmation required for every write, dry-run previews, rate spacing, and hourly caps.Apache 2.0