@ecommaps/mcp
v1.0.10
Published
Official Ecommaps MCP stdio bridge
Readme
@ecommaps/mcp
Official Ecommaps MCP stdio bridge.
This package lets MCP-capable editors connect to Ecommaps over the modern
Streamable HTTP endpoint (/api/v1/mcp) while speaking stdio locally.
Quick Start
Run with your store key and the official endpoint:
npx @ecommaps/mcp <YOUR_STORE_MCP_KEY> --url https://api.ecommaps.com/api/v1/mcpCLI Options
--url <MCP_URL>: Override the MCP endpoint URL.--api-key <KEY>: Pass key explicitly instead of positional arg.--help: Show usage.
Environment Variables
MCP_BEARER_TOKEN: Preferred token source.MCP_API_KEY: Backward-compatible token source.ECOMMAPS_MCP_URL: Default endpoint if--urlis not provided.
Editor Configuration (Generic MCP stdio)
Use the following shape in any editor that supports stdio MCP servers:
{
"command": "npx",
"args": [
"-y",
"@ecommaps/mcp",
"sk_eco_xxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"--url",
"https://api.ecommaps.com/api/v1/mcp"
]
}Or with env var:
{
"command": "npx",
"args": ["-y", "@ecommaps/mcp", "--url", "https://api.ecommaps.com/api/v1/mcp"],
"env": {
"MCP_BEARER_TOKEN": "sk_eco_xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}Important: keep --url https://api.ecommaps.com/api/v1/mcp in editor/server configs to avoid falling back to any outdated transport defaults.
Also make sure --url comes after @ecommaps/mcp in args; otherwise npx treats it as an npm flag and fails.
Transport Notes
- Recommended endpoint:
POST /api/v1/mcp - Legacy compatibility endpoints still exist during migration but are not recommended for new integrations.
Release
cd packages/mcp-cli
npm publish --access public