Connect Your Client
Ecommaps supports two public connection methods for MCP clients:
- native Streamable HTTP
- the official npm stdio bridge
Use the same store API key for both methods.
Method 1: Native Streamable HTTP
Use this when your MCP client supports remote HTTP MCP servers directly.
Required values
- URL:
https://api.ecommaps.com/api/v1/mcp - Header name:
Authorization - Header value:
Bearer <STORE_API_KEY>
Form-based setup
If your MCP client provides a form UI, use:
- server type:
Streamable HTTPorHTTP - URL:
https://api.ecommaps.com/api/v1/mcp - secret environment variable name:
MCP_BEARER_TOKEN - header name:
Authorization - header value:
Bearer ${MCP_BEARER_TOKEN}
Generic JSON shape
{
"mcpServers": {
"ecommaps": {
"type": "http",
"url": "https://api.ecommaps.com/api/v1/mcp",
"headers": {
"Authorization": "Bearer ${MCP_BEARER_TOKEN}"
}
}
}
}Method 2: npm Bridge
Use this when your MCP client expects a local command or stdio process.
The official package is:
@ecommaps/mcp
Recommended config
{
"ecommaps": {
"command": "npx",
"args": ["-y", "@ecommaps/mcp@latest"],
"env": {
"MCP_BEARER_TOKEN": "sk_eco_..."
}
}
}Explicit endpoint override
If you want to pass the production endpoint explicitly:
{
"ecommaps": {
"command": "npx",
"args": ["-y", "@ecommaps/mcp@latest", "--url", "https://api.ecommaps.com/api/v1/mcp"],
"env": {
"MCP_BEARER_TOKEN": "sk_eco_..."
}
}
}@ecommaps/mcp already defaults to the production Ecommaps MCP endpoint, so --url is optional for standard usage.
Quick Setup Checklist
1. Get a store API key
Create or copy a key from store settings.
2. Choose your transport
Use native HTTP when available. Use the npm bridge only when your client requires stdio.
3. Add authentication
Pass the key as Authorization: Bearer <STORE_API_KEY> for HTTP, or as MCP_BEARER_TOKEN for the npm bridge.
4. Verify the connection
Your MCP client should complete initialization and list the available tools.
Which Method Should You Prefer?
- prefer native Streamable HTTP when your client supports it
- use
@ecommaps/mcpfor stdio-only clients