Aep vs Mindbox MCP
A side-by-side look at the Aep and Mindbox MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Aep for customer data platforms work as a local process; choose Mindbox MCP for customer data platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Aep when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AEP_CLIENT_ID, AEP_CLIENT_SECRET, AEP_ORG_ID, AEP_SANDBOX_NAME.
Choose Mindbox MCP when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MINDBOX_API_KEY, MINDBOX_ENDPOINT_ID.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Customer Data Platforms | Customer Data Platforms |
| Quality signal | 41/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | AEP_CLIENT_IDAEP_CLIENT_SECRETAEP_ORG_IDAEP_SANDBOX_NAME | MINDBOX_API_KEYMINDBOX_ENDPOINT_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Aep | View Mindbox MCP |
Tools & capabilities
Aep tools
No tool names declared yet. Check the project README from the listing page.
Mindbox MCP tools
No tool names declared yet. Check the project README from 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.
Aep
{
"mcpServers": {
"aep": {
"command": "npx",
"args": [
"-y",
"@focusgts/aep-mcp-server"
],
"env": {
"AEP_CLIENT_ID": "YOUR_AEP_CLIENT_ID_HERE",
"AEP_CLIENT_SECRET": "YOUR_AEP_CLIENT_SECRET_HERE",
"AEP_ORG_ID": "YOUR_AEP_ORG_ID_HERE",
"AEP_SANDBOX_NAME": "YOUR_AEP_SANDBOX_NAME_HERE"
}
}
}
}
Mindbox MCP
{
"mcpServers": {
"mindbox-mcp": {
"command": "npx",
"args": [
"-y",
"@theyahia/mindbox-mcp"
],
"env": {
"MINDBOX_API_KEY": "YOUR_MINDBOX_API_KEY_HERE",
"MINDBOX_ENDPOINT_ID": "YOUR_MINDBOX_ENDPOINT_ID_HERE"
}
}
}
}
Frequently asked questions
Aep is categorized under Customer Data Platforms and uses a local stdio subprocess. Mindbox MCP belongs to Customer Data Platforms and uses a local stdio subprocess. Pick Aep for customer data platforms work and Mindbox MCP for customer data platforms.
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.
Aep has no declared pricing — check the project's own site. Mindbox 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 aep and mindbox-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aep has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Mindbox MCP has 41/100 (Fair) with 0 views, 0 installs and 4 GitHub stars.