Log inSubmit server
Mindbox MCP logo

Mindbox MCP

Connects AI agents to Mindbox for customer profiles, orders, segments, products, and custom API operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Mindbox MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mindbox-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/mindbox-mcp"
      ],
      "env": {
        "MINDBOX_API_KEY": "YOUR_VALUE_HERE",
        "MINDBOX_ENDPOINT_ID": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 6 tools correctly (7d ago).

Overview

mindbox-mcp MCP server connects AI clients to the Mindbox CDP API through six MCP tools for customer records, orders, segments, products, and custom operations. It uses stdio by default and can expose a Streamable HTTP endpoint with optional host, origin, and bearer-token controls. Mindbox credentials and an endpoint ID are supplied through environment variables, while configured retry and timeout settings handle transient API failures. Reach for it when an agent needs to look up or update customer data, create orders, inspect segments, or call project-specific Mindbox operations.

Use cases

  • Find a customer by email, phone, or ID
  • Create an order linked to a customer
  • Check a customer’s Mindbox segments
  • Update customer profile information
  • Run a project-specific Mindbox operation

Key features

  • Six Mindbox API tools
  • Customer profile lookup and updates
  • Order creation and segment retrieval
  • Product-list access
  • Custom synchronous or asynchronous operations
  • stdio and Streamable HTTP transports

Tools6

What Mindbox MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 50d

What it can do

From the 6 tools this server returned when we ran it.

Read-only tools · 6
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceNot published
Package age205 days
Maintainers1

Observed 2026-10-21 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @theyahia/mindbox-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads125Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed6Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Mindbox MCP works

What mindbox-mcp MCP server does

The mindbox-mcp MCP server gives an AI client access to selected Mindbox CDP actions without requiring a separate export or custom chat integration. Its tool set covers customer lookup, customer updates, order creation, segment retrieval, product-list retrieval, and execution of an arbitrary Mindbox operation.

Customer lookup accepts an email address, phone number, or customer ID. Orders can be associated with an existing customer, and profile updates can modify customer data. Segment and product tools retrieve information from the connected Mindbox project. The raw operation tool accepts a Mindbox operation and request body, which makes it useful for project-specific APIs that are not represented by the dedicated tools.

Two included skills describe common workflows: searching for a customer and obtaining segment statistics.

How it works

The server authenticates requests with a Mindbox secret key and sends them to Mindbox’s v3 operation endpoints. Operations are normally synchronous, so tools can return a response such as a profile or segment result. The raw operation tool can also use asynchronous mode for fire-and-forget events such as views or cart additions.

Mindbox operation names are configured per project. Names shown in examples are conventions rather than universal built-in methods, so the matching operation must exist in the target project. If it does not, Mindbox can return a protocol error.

Requests that receive rate-limit responses, server errors, or timeouts are retried with backoff. The implementation also supports transaction IDs for idempotency. For HTTP use, the default endpoint is /mcp on port 3000, with a /health endpoint for health checks.

Setup and configuration

For local stdio use, run the npm package with npx and provide MINDBOX_API_KEY and MINDBOX_ENDPOINT_ID. Claude Desktop and Claude Code examples in the README show these values in their MCP configuration. The package can also run with --http; PORT and HOST control the listener, which defaults to 127.0.0.1:3000.

Docker deployment is supported. The container listens on port 3000 and can receive the same Mindbox credentials through environment variables. HTTP deployments may set MINDBOX_HTTP_TOKEN, allowed hosts, and allowed origins. Retry count, base backoff, and request timeout are configurable with MINDBOX_MAX_RETRIES, MINDBOX_RETRY_BASE_MS, and MINDBOX_TIMEOUT_MS.

Tools and capabilities

The six tools are:

  • get_customer searches for a customer by email, phone, or ID.
  • create_order creates an order linked to a customer.
  • get_segments retrieves a customer’s segments.
  • get_product_list retrieves a product list.
  • update_customer changes a customer profile.
  • run_operation sends a custom Mindbox operation and can use asynchronous mode.

The mindbox-mcp MCP server also includes the skill-customer-search and skill-segment-stats workflow skills for the triggers documented in the repository.

Limitations and notes

The raw operation tool can perform data-changing actions under the configured secret key. Disable it by setting MINDBOX_ALLOW_RAW to 0, false, off, or no when agents should not have arbitrary operation access. Calls to this tool are written to stderr.

HTTP transport does not provide built-in authentication unless MINDBOX_HTTP_TOKEN is configured. Keep the service behind an authenticating reverse proxy for remote access, and avoid exposing the port unnecessarily. Host and origin checks provide DNS-rebinding protection, while the secret key remains server-side.

The server may start without credentials and list its tools, but tool calls require the Mindbox API key and endpoint ID. A valid key alone is not sufficient if it lacks permission for the requested operation or if the project has not configured the required operation name.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Mindbox MCP

mindbox-mcp is an MCP server that connects AI clients to the Mindbox CDP API. Its main tools look up and update customer profiles, create orders, retrieve customer segments and product lists, and run custom Mindbox operations. It supports stdio by default and Streamable HTTP when started with the HTTP option.

Install it by configuring an MCP client to run `npx -y @theyahia/mindbox-mcp` with `MINDBOX_API_KEY` and `MINDBOX_ENDPOINT_ID`. The README provides configuration examples for Claude Desktop and Claude Code. Docker and Smithery setup are also documented.

Configure Cursor to launch the package through its standard MCP setup and provide the required Mindbox API key and endpoint ID.

Run `npx @theyahia/mindbox-mcp --http` with the Mindbox credentials in the environment. The MCP endpoint defaults to `http://127.0.0.1:3000/mcp`, and `/health` provides a health check. `PORT`, `HOST`, and optional HTTP security variables control deployment.

Set `MINDBOX_ALLOW_RAW` to `0`, `false`, `off`, or `no` to disable `run_operation`. This prevents agents from invoking arbitrary operations through the configured Mindbox secret key while leaving the dedicated tools available.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMindbox MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mindbox-mcp?style=directory)](https://allmcps.com/mcp/mindbox-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/mindbox-mcp"><img src="https://allmcps.com/api/badge/mindbox-mcp?style=directory" alt="Mindbox MCP on AllMCPs" /></a>