npm Bridge
@ecommaps/mcp is the official npm bridge for MCP clients that require a local stdio command.
It forwards stdio MCP traffic to the Ecommaps production MCP server.
Package
Default Endpoint
The package defaults to:
https://api.ecommaps.com/api/v1/mcp
That means the shortest standard production setup is:
{
"ecommaps": {
"command": "npx",
"args": ["-y", "@ecommaps/mcp@latest"],
"env": {
"MCP_BEARER_TOKEN": "sk_eco_..."
}
}
}Explicit Endpoint Example
{
"ecommaps": {
"command": "npx",
"args": ["-y", "@ecommaps/mcp@latest", "--url", "https://api.ecommaps.com/api/v1/mcp"],
"env": {
"MCP_BEARER_TOKEN": "sk_eco_..."
}
}
}CLI Examples
MCP_BEARER_TOKEN=sk_eco_xxxxxxxxxxxxxxxxxxxxxxxxxxxxx \
npx -y @ecommaps/mcp@latestSupported Inputs
MCP_BEARER_TOKEN: preferred authentication token sourceMCP_API_KEY: backward-compatible token sourceECOMMAPS_MCP_URL: optional endpoint override--url: explicit endpoint override--api-key: explicit key input
Use the npm bridge only when your MCP client cannot connect to remote HTTP MCP servers directly.