@ecommaps/mcp

@ecommaps/mcp is the official Ecommaps stdio bridge for MCP clients that need a local command instead of a native remote HTTP server connection.

It connects local stdio traffic to the Ecommaps MCP server at:

https://api.ecommaps.com/api/v1/mcp

When to use this package

Use @ecommaps/mcp when:

your editor only supports stdio MCP servers
your MCP client expects a local command
you need a simple bridge from local agent tooling to the remote Ecommaps MCP endpoint

If your client supports direct remote HTTP MCP servers, prefer native HTTP instead. See Connect Your Client.

Quick Start

MCP_BEARER_TOKEN=sk_eco_xxxxxxxxxxxxxxxxxxxxxxxxxxxxx \
npx -y @ecommaps/mcp@latest

Recommended Client Config

This configuration is confirmed to work with modern command-based MCP clients:

{
  "ecommaps": {
    "command": "npx",
    "args": ["-y", "@ecommaps/mcp@latest"],
    "env": {
      "MCP_BEARER_TOKEN": "sk_eco_..."
    }
  }
}

If you want to override the default endpoint explicitly, use:

{
  "ecommaps": {
    "command": "npx",
    "args": ["-y", "@ecommaps/mcp@latest", "--url", "https://api.ecommaps.com/api/v1/mcp"],
    "env": {
      "MCP_BEARER_TOKEN": "sk_eco_..."
    }
  }
}

CLI Options

--url <MCP_URL>: Override the remote MCP endpoint
--api-key <KEY>: Pass the store key explicitly
--help: Print usage information

Environment Variables

MCP_BEARER_TOKEN: preferred auth token source
MCP_API_KEY: backward-compatible auth token source
ECOMMAPS_MCP_URL: default MCP endpoint URL

Connection Examples

npx -y @ecommaps/mcp@latest sk_eco_xxxxxxxxxxxxxxxxxxxxxxxxxxxxx --url https://api.ecommaps.com/api/v1/mcp

Default Endpoint Behavior

The package already defaults to:

https://api.ecommaps.com/api/v1/mcp

That means this shorter command is valid for standard production usage:

MCP_BEARER_TOKEN=sk_eco_xxxxxxxxxxxxxxxxxxxxxxxxxxxxx \
npx -y @ecommaps/mcp@latest

Important Notes

Put the package name before --url in args
Use ASCII dashes: --url, not smart dashes
Test from outside a monorepo if you need to verify the published npm package

⚠️

If --url appears before the package name, npx may interpret it as an npm CLI flag and fail before the MCP bridge starts.

Troubleshooting

npm parses `--url` as a normal CLI flag

Use:

["-y", "@ecommaps/mcp@latest", "--url", "https://api.ecommaps.com/api/v1/mcp"]

Do not use:

["--url", "https://api.ecommaps.com/api/v1/mcp", "@ecommaps/mcp@latest"]

Unauthorized or invalid token

Check that:

the key is valid and active
the key belongs to the correct store
the header equivalent is Authorization: Bearer <STORE_API_KEY>

Works in one client, fails in another

If one MCP client succeeds and another fails, the remaining issue is usually the client configuration shape rather than the package or the backend.

@ecommaps/ai-sales-agent Versions & Compatibility