mCRM
Overview
A CRM for online stores: catalog, orders, customers, payments and delivery — plus a REST API, a payment widget and an MCP server for AI.
- Year
- 2026
- Type
- SaaS · Own product
- Role
- Design and full-stack development
- Link
- mcrm.makarov.media
- 195
- MCP tools
- 7
- payment methods
- 63
- data models
Challenge and solution
The challenge
Small online stores glue together a catalog, payments, delivery and notifications from separate services — and every Russian payment provider and carrier has its own API and webhooks.
The solution
One CRM that wraps 7 payment methods and 3 carriers behind a single dashboard, a REST API and a drop-in widget. Every dashboard action is also an MCP tool, so an AI assistant can run the store with exactly the same permissions as a person.
Screens
What it does
- Catalog with variants, options, discounts and photo background removal
- Orders with statuses, refunds, shipments and tracking
- 7 payment methods and delivery via CDEK, Yandex and Ozon
- Customer emails and SMS; order alerts to Telegram, email and Google Sheets
- A Telegram bot that works as a storefront with cart and checkout
- REST API with keys and an embeddable widget for payment, delivery and forms
Under the hood
- The MCP server builds its tools from the dashboard routes’ Zod schemas; a test fails if one is missing.
- Webhooks signed with HMAC-SHA256, retried with backoff and protected against SSRF.
- Postgres-backed job queue for emails, SMS, webhooks, newsletters and bot broadcasts.
- Public OpenAPI spec with a Scalar reference; product feeds for Yandex and Google Merchant.
- Bun
- Fastify
- Prisma
- PostgreSQL
- Zod
- Next.js
- React
- Tailwind CSS
- TanStack Query
- MCP
- Python
- Docker