DataDoe MCP vs Retailcrm MCP
A side-by-side look at the DataDoe MCP and Retailcrm MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DataDoe MCP for e-commerce work over a hosted endpoint; choose Retailcrm MCP for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose DataDoe MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
sellers_and_vendors_list, sellers_and_vendors_get, sellers_and_vendors_rename.
Choose Retailcrm MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_orders, get_order, create_order.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 56/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 55 | 39 |
| Full listing | View DataDoe MCP | View Retailcrm MCP |
Tools & capabilities
DataDoe MCP tools 55
sellers_and_vendors_listLists Amazon sellers and vendors connected to your DataDoe organization, with account type, marketplace, and connection details.sellers_and_vendors_getReturns one seller or vendor, including whether a connection needs reauthorization.sellers_and_vendors_renameRenames a seller or vendor. Names are unique within the organization.sellers_and_vendors_invitation_createCreates a one-time link to connect a new Amazon account or reconnect an existing one.sellers_and_vendors_invitations_getLists pending invitations, or returns one invitation and its status.sellers_and_vendors_invitation_revokeRevokes a pending invitation so its link can no longer be used.organization_and_subscription_details_getReturns your DataDoe organization profile, subscription plan, billing health, and AI Token balances.exports_sources_getSearches DataDoe's catalog of Amazon data export sources (orders, sales and traffic, ads performance, inventory, listings, settlements, returns, brand analytics, and more) by keyword.exports_source_getReturns the columns (paginated) and metadata of one export source, including whether a date period is required.exports_createCreates an Amazon data export from any source. Supports SQL-like filters, HAVING, GROUP BY, aggregations (sum / avg / count / countDistinct / min / max), date intervals (DAY / WEEK / MONTH), pagination, and CSV or JSON output.exports_getReturns status and metadata for an in-flight or completed export job.exports_listLists export jobs for the organization with pagination and optional export ID filters.- +43 more on the listing page
Retailcrm MCP tools 39
list_ordersList orders with filters by status, customer name, number, and created-date range. Returns (summary): pagination + array of {id, number, status, total, customer, phone, itemCount, createdAt}. Use detail:'full' for line items/delivery/payments, raw:true for the untouched payload.get_orderGet a single order by RetailCRM id or externalId. Returns a shaped order; detail:'full' adds items, delivery, payments, comments.create_orderCreate an order with line items and delivery. Link an existing customer via customer_id/customer_external_id, or pass first_name (+phone/email) to create one inline. Returns {success, id, order?}.update_orderUpdate an order (status, customer, delivery, comments). Only the fields you pass are sent. Returns {success}.orders_historyOrder change history incl. status transitions; supports incremental sync via filter_since_id and a date window. Returns {history[], pagination}.list_customersList/search customers by name, email, phone, created-date. Returns (summary): pagination + array of {id, name, email, phone, ordersCount, totalSpent}. detail:'full' adds address/externalId/all phones.get_customerGet a single customer by id or externalId. Returns a shaped customer; detail:'full' adds address and contact details.create_customerCreate a customer with name, contacts, address, optional externalId. Returns {success, id}.update_customerEdit an existing customer (name, email, phones, address) by id or externalId. Only the fields you pass are sent. Returns {success}.merge_customersMerge duplicate customers into a target; merged records are DELETED. Returns {success}.customers_historyCustomer field-change log for growth/churn signals and incremental sync. Returns {history[], pagination}.list_productsList catalog products with filters by name, active, group, price range. Returns pagination + array of {id, name, article, active, url, groups, offers}.- +27 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
DataDoe MCP
{
"mcpServers": {
"datadoe-mcp": {
"url": "https://www.datadoe.com/connect/amazon/mcp"
}
}
}
Retailcrm MCP
{
"mcpServers": {
"retailcrm-mcp": {
"command": "npx",
"args": [
"-y",
"@theyahia/retailcrm-mcp"
]
}
}
}
Frequently asked questions
DataDoe MCP is categorized under E-Commerce and uses a remote HTTP/SSE transport. Retailcrm MCP belongs to E-Commerce and uses a local stdio subprocess. Pick DataDoe MCP for e-commerce work and Retailcrm MCP for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
DataDoe MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Retailcrm MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add datadoe-mcp and retailcrm-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DataDoe MCP has a quality signal of 56/100 (Good) with 2 views, 0 installs and 16 GitHub stars. Retailcrm MCP has 59/100 (Good) with 1 views, 0 installs and 1 GitHub stars.
