Medusa MCP. Manage every part of your headless e-commerce stack via chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Medusa (Headless E-commerce Engine) MCP Server lets your AI client directly manage commerce data from MedusaJS. You can list products by ID, check order statuses, retrieve customer profiles, capture payments, or audit regional tax settings—all through natural conversation.
It gives agents full control over core e-commerce operations without needing manual dashboard exports.
What your AI agents can do
Capture payment
Moves authorized funds from the customer vault into your store's processing pipeline for a specified Medusa order ID.
Get customer
Retrieves all details about a specific Medusa CRM customer using their unique ID.
Get order
Pulls full information for a single order, including line items, shipping addresses, payment status, and fulfillment history.
Retrieves every detail about a single product by its ID, including all variants, pricing structures, and media.
Triggers the manual capture of funds for an authorized order, moving money from the customer vault into your store's processing pipeline.
Lists recent orders and pulls comprehensive data—line items, shipping addresses, payment status, and fulfillment history—for any given ID.
Fetches detailed records for specific customers or lists the entire registered customer directory in the CRM.
Extracts global store metadata, like base URLs and default region settings, to ensure accurate cross-border auditing.
Navigates product group taxonomies, allowing you to list and verify how products are organized across the store.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Medusa (Headless E-commerce Engine) MCP Server: 10 Tools
Manage core e-commerce functions like product retrieval, order status checks, payment capture, and customer CRM access using these ten defined tools.
019d75d1capture payment
Moves authorized funds from the customer vault into your store's processing pipeline for a specified Medusa order ID.
019d75d1get customer
Retrieves all details about a specific Medusa CRM customer using their unique ID.
019d75d1get order
Pulls full information for a single order, including line items, shipping addresses, payment status, and fulfillment history.
019d75d1get product
Gets comprehensive details on one Medusa product by ID, showing all variants, pricing options, and media galleries.
019d75d1get store config
Returns global store settings, including supported currencies and the default operating region for your store.
019d75d1list collections
Lists all product collections available in Medusa, letting you audit how products are grouped by taxonomy.
019d75d1list customers
Provides a full list of registered customers within the Medusa CRM directory.
019d75d1list orders
Returns a list of recent commerce orders, giving you an overview of activity and IDs to investigate further.
019d75d1list products
Lists all available products in your Medusa store, useful for getting an overall catalog snapshot.
019d75d1list regions
Displays configured geographical regions, detailing local tax rates and enabled payment providers for cross-border checks.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Medusa (Headless E-commerce Engine), then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Medusa E-commerce MCP Server - Orders & Products lets your agent talk shop with your entire MedusaJS backend. You'll get full command over everything from product catalog management to processing actual payments, all without lifting a finger on an admin dashboard. This server gives your AI client the tools it needs to run complex commerce ops just by having a conversation.
How Medusa MCP Works
- 1 First, subscribe to this server on Vinkius. You'll need your Medusa Store URL and an Admin API Token.
- 2 Next, tell your AI client exactly what you want—for example, 'List the last 5 orders placed today.'
- 3 Your agent uses the appropriate tool (like
list_orders) to communicate with the backend, pulls the data, and presents a clean summary back to you.
The bottom line is: your AI client talks directly to your e-commerce backend using structured tools, letting you manage complex commerce logic without leaving the chat window.
Who Is Medusa MCP For?
This server targets developers and operations teams who deal with high volumes of e-commerce data but are sick of jumping between dashboards. If you're constantly cross-referencing order IDs, checking regional tax rates, or manually updating product metadata, this is for you. It puts the entire backend API surface right into your conversational workflow.
Monitors complex order flows and customer profiles across multiple store regions. They use list_orders and list_regions to quickly spot discrepancies without running manual exports.
Needs to verify API responses, check product variant mappings, or audit collection hierarchies directly in their workspace for rapid debugging. They rely heavily on get_product and list_collections.
Manages payments and inventory state. They use capture_payment to move funds or get_customer to verify a user's internal flags before proceeding with fulfillment.
What Changes When You Connect
- Audit order status and history instantly. Instead of running a report, simply use
list_ordersorget_orderto pull full line items, payment statuses, and shipping addresses directly into the conversation window. - Handle payments without switching tools. Use
capture_paymenton an authorized order ID to move funds immediately. This is critical for keeping your commerce pipeline running smoothly. - Verify product data instantly. Need to know pricing or variants? Call
get_productwith just an ID, and you get all the necessary metadata (SKUs, options) without navigating the admin panel. - Manage customer records from anywhere. Use
list_customersorget_customerto check a profile's internal flags or default shipping address—it’s like having direct CRM access in your agent. - Understand global tax and currency rules. Run
list_regionsto see all configured store regions, helping you audit localized tax rates and payment providers across different countries.
Real-World Use Cases
Investigating a Failed Shipment
A customer calls about Order #XYZ. Instead of having the agent ask for 10 details, you run get_order(id='XYZ'). The agent returns the full status—including line items and fulfillment history—allowing you to tell the customer exactly what went wrong in one go.
Verifying Product Pricing Changes
Marketing wants to confirm if a product's price changed regionally. You use get_product(id='ABC') and then cross-reference that data with list_regions. The agent compares the base pricing against regional tax logic, confirming the final listed cost.
Completing an Order Transaction
The order is paid but needs fulfillment. You confirm the ID and then immediately call capture_payment(order_id='DEF'). The agent executes the transaction, updating the status to 'Awaiting Fulfillment' in Medusa.
Auditing a New Market Launch
You need to know what payment types are available in Brazil. You call list_regions and filter by currency/country code. The agent returns a list of configured regions, showing exactly which local tax rates and providers apply.
The Tradeoffs
Treating listing tools as the source of truth
Running list_products just to find one product's price. This generates a huge list, forcing you to scroll and filter through potentially hundreds of items.
→
If you know the ID, don't list it; go straight to get_product(id='SKU123'). Use the specific getter tool every single time you can. It saves calls, time, and API cost.
Assuming payment happens automatically
Thinking that just because an order exists, the money is secured for fulfillment. The funds might still be pending or 'Awaiting Capture.'
→
Always confirm status using get_order. If it's authorized but not yet processed, you must explicitly call capture_payment(order_id='...') to move the funds.
Using generic search instead of specific data calls
Asking the agent 'Tell me about a customer from California.' This is too vague and might pull irrelevant or incomplete profile data.
→
If you have the ID, use get_customer(id='CUST456'). If you need a list, use list_customers first. Be precise with your inputs.
When It Fits, When It Doesn't
Use this server if your workflow requires deep, multi-step interaction with MedusaJS data—specifically when you have to sequence calls like checking customer details (get_customer) before verifying their shipping address or triggering an order status update. You need it when a single piece of information (like the correct tax rate from list_regions) dictates the next action.
Don't use it if your goal is simple data consumption, like viewing basic analytics that don't require transactional logic. For those cases, you might just read an internal dashboard export. If all you need is a high-level list and no subsequent actions are required (like capturing payment or updating metadata), simply using list_products gets the job done without needing to trigger complex workflows.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by MedusaJS. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually auditing order fulfillment across multiple tabs is a massive time sink.
Right now, if you need to verify an order's payment status and its associated shipping address for three different customers, you open the dashboard. You click on Order A, copy the ID; check the payment tab; then switch tabs. Repeat this process for B and C. It’s a cycle of clicking, copying, pasting, and cross-referencing.
With the Medusa MCP Server, you just tell your agent: 'Give me the status and addresses for orders A, B, and C.' The server runs `get_order` three times in the background, pulls all the line items and payment data, and gives you a single, structured output. You get instant clarity.
Medusa MCP Server: full control over your commerce backend.
The biggest pain point is separating data retrieval from action. Most systems let you view a list of products, but if you spot an error—like the wrong variant being listed—you have to jump out and use another tool just to correct it or capture payments. It’s a two-stage process.
Here's the difference: You ask your agent about product ID 'X'. The server not only returns all the data via `get_product` but also confirms if that item is eligible for immediate payment capture, linking observation straight to transaction in one single conversation.
Common Questions About Medusa MCP
How do I find out what tax rates apply when listing regions using list_regions? +
The list_regions tool provides detailed data on configured store regions. It shows the local tax rates and currency logic enabled for different geographies, helping you audit cross-border compliance.
Can I use get_product to check if a product is available? +
Yes. get_product returns full details including pricing, variants, and options. You can read the inventory/stock data returned by this tool to confirm availability.
What do I use for listing all customers? Is it list_customers or get_customer? +
Use list_customers when you need a directory overview. Use get_customer(id='...') only when you know the specific ID and need deep, individual profile details.
Is capture_payment safe to run on any order? +
No. You must first use get_order(id='...') to verify the payment status and ensure the order is authorized before calling capture_payment. This prevents unauthorized fund movement.
I need product data, but I only know the collection name. Which tool do I run? +
First, use list_collections to verify the exact taxonomy group. Then, you'll likely need to list products or iterate through collections to find specific IDs for get_product.
When I use `get_order` or any other tool, how does my AI client authenticate with Medusa? +
You need to provide your Medusa Store URL and Admin API Token. Your agent uses these credentials for every call, so make sure the token has read/write permissions for orders and customers.
If I try to run `capture_payment` on an order that is already fulfilled, what happens? +
The tool will return a specific error code detailing why capture failed. This prevents you from trying to move funds for orders that are already marked as shipped or complete in Medusa.
How do I retrieve all products if my catalog has thousands of items using `list_products`? +
The tool handles pagination automatically, but you may need to prompt your agent multiple times. It will use the provided cursor or next page token until it confirms no more records are available.
Can I capture a payment for an authorized order using my agent? +
Yes. Use the capture_payment tool with a specific Order UUID. Your agent will trigger the action against your payment provider (e.g., Stripe) to finalize the fund transfer for the order immediately.
How do I check the tax rates and currencies for a specific region? +
The list_regions tool retrieves all configured geographical zones in Medusa. Your agent will expose the localized currency logic, tax rates, and enabled payment methods assigned to each region.
Can my agent retrieve the detailed variants and prices for a product? +
Absolutely. Use the get_product tool by providing the Product ID. Your agent will fetch the full object including nested variants, options (size, color), and pricing arrays for all configured regions.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Linear (Issue Tracking & PM)
Manage product development via Linear — track issues, monitor sprint cycles, and audit team projects.
Resend Alternative
Send emails and manage domains via Resend — send transactional emails, track deliveries, manage domains and API keys from any AI agent.
Doppler
Manage secrets and environment variables via Doppler — list projects, audit secrets, and track activity logs from any AI agent.
You might also like
ROC AUC Evaluator
Compute the exact Area Under the ROC Curve for binary classification predictions. Local, mathematically perfect, zero LLM estimation.
Moloco
Manage machine learning-powered advertising via Moloco — track campaigns and get analytics directly from your AI agent.
DeskTime
Understand how your team spends their workday with automatic time tracking, productivity scoring, and project cost analysis.