Moltline Dropship Economics
Server Details
Margin, lead time, SKU mapping and price-ladder maths for dropshipping. 4 of 6 free.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
6 toolslead_timeLead TimeRead-onlyIdempotentInspect
Turn supplier and transit times into a date you can promise. FREE.
Adds a buffer, because the number a supplier quotes is their best case and the date you publish is a commitment. Typical input {"supplier_days": 3, "transit_days": 12, "order_date": "2026-08-20"} returns {"total_days": 17, "delivery_date": "2026-09-06", "promise_date": "2026-09-09", "advice": "..."}.
Use when writing a shipping policy or answering "when will it arrive". Not for what the shipping costs — that is the shipping server. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "order_date must be YYYY-MM-DD, e.g. 2026-08-20"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| order_date | No | Start date as YYYY-MM-DD, e.g. "2026-08-20". Defaults to today when omitted. | |
| buffer_days | No | Extra days added before the date you publish. Default 2. | |
| transit_days | Yes | Days in transit from despatch to the customer. | |
| supplier_days | Yes | Days from your order to the supplier despatching it. | |
| working_days_only | No | When true, count supplier and transit days as Monday-Friday only. Default false. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
margin_checkMargin CheckRead-onlyIdempotentInspect
Show what one sale actually leaves after every cost. FREE.
Subtracts supplier cost, shipping, payment fees, the ad spend that found the buyer, and anything else — then reports the break-even price so you know how much room there is. Typical input {"sell_price": 39.99, "supplier_cost": 12.4, "shipping_cost": 4.2, "ad_cost_per_order": 9} returns {"revenue": 39.99, "total_cost": 27.06, "profit": 12.93, "margin_pct": 32.33, "markup_pct": 222.5, "break_even_price": 27.06, "biggest_cost": "supplier_cost"}.
Use before listing a product. Not for a whole tiered price list — that is price_ladder — and not for the effect of returns, which is returns_impact. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| other_cost | No | Anything else per order: packaging inserts, app fees, support time. Default 0. | |
| sell_price | Yes | What the customer pays, excluding tax. Must be above 0. | |
| shipping_cost | No | Shipping you absorb per order. Default 0. | |
| supplier_cost | Yes | What the supplier charges you per unit. | |
| payment_fee_pct | No | Processor percentage fee. Default 2.9 — a common published rate, not a statement about your account. | |
| ad_cost_per_order | No | Blended acquisition cost per order. Default 0, but leaving it at 0 is the most common way this maths lies. | |
| payment_fee_fixed | No | Processor fixed fee per transaction. Default 0.30. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
moq_plannerMoq PlannerRead-onlyIdempotentInspect
Decide how much to order against demand, lead time and the cash you have. PREMIUM (license).
A minimum order quantity is a cash-flow decision disguised as a purchasing one. Typical input {"unit_cost": 4.2, "moq": 500, "monthly_demand": 120, "cash_available": 3000, "lead_time_days": 45} returns {"moq_cost": 2100.0, "months_of_cover": 4.17, "affordable": true, "cash_after": 900.0, "reorder_point_units": 236, "verdict": "..."}.
Use before committing to a supplier's minimum. Not for the margin each unit earns — that is margin_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| moq | Yes | The supplier's minimum order quantity, in units. | |
| unit_cost | Yes | Cost per unit at the MOQ. Must be above 0. | |
| safety_weeks | No | Weeks of demand held as buffer against a late delivery. Default 2. | |
| cash_available | Yes | Cash you can commit to stock right now. | |
| lead_time_days | No | Days from placing the order to stock being sellable. Default 30. | |
| monthly_demand | Yes | Units you expect to sell per month. Must be above 0. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
price_ladderPrice LadderRead-onlyIdempotentInspect
Work backwards from the margin you want to the price you must charge. FREE.
Solves for price including the percentage fee, which is why it is not simply cost divided by one minus margin. Typical input {"supplier_cost": 12.4, "target_margins_pct": [30, 40, 50], "shipping_cost": 4.2} returns {"rows": [{"target_margin_pct": 30, "price": 25.99, "total_cost": 17.65, "profit": 8.34, "actual_margin_pct": 32.07}, ...]}.
Use when setting a price list. Not for checking one price you already have — that is margin_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "target_margins_pct must contain at least one margin"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| charm_ending | No | Force prices to end in these cents, e.g. ".99". Pass an empty string for exact prices. Default ".99". | .99 |
| shipping_cost | No | Shipping you absorb per order. Default 0. | |
| supplier_cost | Yes | Per-unit cost from the supplier. Must be above 0. | |
| payment_fee_pct | No | Processor percentage fee. Default 2.9. | |
| payment_fee_fixed | No | Processor fixed fee. Default 0.30. | |
| target_margins_pct | Yes | Margins to solve for, e.g. [30, 40, 50]. Each must be above 0 and below 100. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
returns_impactReturns ImpactRead-onlyIdempotentInspect
Show what a return rate does to a margin that looked fine. PREMIUM (license).
A 10% return rate does not cost 10% of profit. A returned order gives back the refund, adds inbound shipping, and recovers only the goods — never the advertising that found the buyer. Typical input {"sell_price": 39.99, "unit_profit": 13.23, "unit_cost": 12.4, "return_rate_pct": 8, "restock_pct": 70, "return_shipping": 6} returns {"cost_per_return": 37.31, "effective_profit": 10.25, "profit_lost_pct": 22.56, "break_even_return_rate_pct": 35.46}.
Use when a category's returns are high enough to argue about. Not for the pre-returns margin itself — that is margin_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| unit_cost | Yes | What the goods themselves cost you — the only part a restocked unit gives back. Advertising and fees do not return. | |
| refund_pct | No | Percentage of the sale price refunded, e.g. 100 for a full refund or 80 when a restocking fee is kept. Default 100. | |
| sell_price | Yes | Price the customer paid. | |
| restock_pct | No | Percentage of returned units resellable at full price. Default 0, the conservative case. | |
| unit_profit | Yes | Profit on one kept sale, from margin_check. May be negative, which the result will make obvious. | |
| return_rate_pct | Yes | Percentage of orders returned, e.g. 8. | |
| return_shipping | No | What an inbound return costs you. Default 0. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
sku_map_checkSku Map CheckRead-onlyIdempotentInspect
Find the breaks in a supplier-to-store SKU map before they ship. FREE.
Two store SKUs pointing at one supplier SKU is usually intentional; two supplier SKUs claiming one store SKU is not, and it sends the wrong item. Typical input {"mapping": {"STORE-1": "SUP-A", "STORE-2": "SUP-A", "STORE-3": ""}} returns {"ok": false, "count": 3, "empty_targets": ["STORE-3"], "shared_supplier_skus": {"SUP-A": ["STORE-1", "STORE-2"]}, "whitespace_issues": []}.
Use before importing a mapping or handing one to a fulfilment app. Not for validating Shopify's CSV columns — that is the shopify server. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "mapping must contain at least one store SKU"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| mapping | Yes | Store SKU to supplier SKU, e.g. {"STORE-1": "SUP-A"}. At least one entry. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityAmaintenanceMulti-channel inventory intelligence for Shopify and Amazon sellers. 28 tools for stockout risk, demand forecasts, purchase order management, and sales analytics — with human-in-the-loop safeguards.502452MIT
- AlicenseCqualityCmaintenanceDeterministic Odoo ERP calculators: implementation, migration and upgrade cost, ROI and TCO, US/Canada/EU sales tax and VAT, Canadian payroll source deductions, and inventory maths (reorder point, safety stock, EOQ, landed cost, OEE). 24 tools, each a pure function, the numbers are arithmetic rather than a model's guess. Hosted remote server, no install and no API key; a stdio bridge is included24MIT
- Alicense-qualityCmaintenanceAI-powered e-commerce research tools via MCP. Search Amazon, Alibaba & AliExpress for winning products, vet suppliers, and calculate FBA margins. 19 tools, free tier available.394MIT
- AlicenseAqualityBmaintenanceProvides current, human-verified pricing for 100+ AI tools and calculates AI product margins (MRR after costs). Fetches live price index and runs locally.261MIT