Ecommerce Command Center

Ecommerce Command Center runs locally from a Python package published to PyPI: ecommerce-command-center-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx ecommerce-command-center-mcp. It reads these environment variables: EARNALL_MCP_LICENSE_KEY (required, secret), EARNALL_MCP_ACTIVATION_ID and EARNALL_MCP_LICENSE_API; set them in the client's configuration for this server.

Ecommerce Command Center runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/atulhritik/ecommerce-command-center-mcp:0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm docker.io/atulhritik/ecommerce-command-center-mcp:0.1.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "ecommerce-command-center": {
      "command": "uvx",
      "args": [
        "ecommerce-command-center-mcp"
      ],
      "env": {
        "EARNALL_MCP_LICENSE_KEY": "<secret>",
        "EARNALL_MCP_ACTIVATION_ID": "<value>",
        "EARNALL_MCP_LICENSE_API": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect