Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"retailcrm": {
"env": {
"RETAILCRM_DOMAIN": "yourstore.retailcrm.ru",
"RETAILCRM_API_KEY": "your-api-key"
},
"args": [
"-y",
"@theyahia/retailcrm-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Production-grade MCP server for RetailCRM e-commerce CRM. 15 tools + 2 prompt skills for managing orders, customers, products, references, and analytics via API v5.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@theyahia/retailcrm-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @theyahia/retailcrm-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ecommerce
Production-grade MCP server and CLI tool for Shopify Admin GraphQL API — 49+ tools, YAML-extensible, dual auth, dual transport, Docker-ready
A command line tool for setting up commercetools MCP server
35+ AI tools for TCG card grading, Monte Carlo pricing, 370K+ product search. BYOK.
This is the reference implementation for the mcp server
MCP Security Weekly
Get CVE alerts and security updates for io.github.theYahia/retailcrm-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Production-grade MCP server for RetailCRM e-commerce CRM. 15 tools + 2 prompt skills for managing orders, customers, products, references, and analytics via API v5.
| Tool | Description |
|---|---|
list_orders | List orders with filters by status, customer, number, date range |
get_order | Get a single order by ID or externalId |
create_order | Create an order with customer info, line items, delivery |
update_order | Update order status, customer details, delivery, comments |
| Tool | Description |
|---|---|
list_customers | Search customers by name, email, phone, date |
get_customer | Get a single customer by ID or externalId |
create_customer | Create customer with contact info and address |
merge_customers | Merge duplicate customer records |
| Tool | Description |
|---|---|
list_products | List products with filters by name, group, active status, price range |
| Tool | Description |
|---|---|
list_statuses | All order statuses (codes, names, groups) |
list_delivery_types | All delivery types with default costs |
list_payment_types | All payment types |
list_stores | All warehouses and stores |
| Tool | Description |
|---|---|
get_orders_summary | Order statistics for a date range |
get_customers_summary | Customer growth stats for a date range |
| Skill | Description |
|---|---|
new-orders | Quick daily overview of today's orders |
customer-search | Find a customer by name, email, or phone |
yourstore part of yourstore.retailcrm.ru)| Variable | Required | Description |
|---|---|---|
RETAILCRM_DOMAIN | Yes | Your RetailCRM domain (e.g. yourstore.retailcrm.ru) |
RETAILCRM_API_KEY | Yes | API key from Settings > Integration > API keys |
PORT | No | HTTP server port (default: 3000, only for --http mode) |
RETAILCRM_URLis still supported as a fallback for backward compatibility.
{
"mcpServers": {
"retailcrm": {
"command": "npx",
"args": ["-y", "@theyahia/retailcrm-mcp"],
"env": {
"RETAILCRM_DOMAIN": "yourstore.retailcrm.ru",
"RETAILCRM_API_KEY": "your-api-key"
}
}
}
}
Run as an HTTP server instead of stdio:
RETAILCRM_DOMAIN=yourstore.retailcrm.ru \
RETAILCRM_API_KEY=your-key \
npx @theyahia/retailcrm-mcp --http
POST /mcp -- MCP Streamable HTTP endpointGET /health -- health check (returns JSON with version, tool count)PORT env var)Install via Smithery:
npx @smithery/cli install @theyahia/retailcrm-mcp
1. Daily order overview:
"Show me all orders created today with status 'new'. Summarize the total count and revenue."
2. Customer lookup and order history:
"Find the customer with email anna@example.com. Show their full profile and recent orders."
3. Quick order creation:
"Create an order for Ivan Petrov, phone +79001234567, for 2x Widget at 500 RUB each, standard delivery to Moscow."
RetailCRM does not support API-created webhooks. Instead, use Triggers in the RetailCRM admin panel (Settings > Triggers) to configure automated actions on order/customer events