HTTP Transport

Ecommaps MCP uses Streamable HTTP for public merchant integrations.

Base URL:

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

Supported HTTP Methods

GET /api/v1/mcp
POST /api/v1/mcp

Authentication

All requests authenticate with:

Authorization: Bearer <STORE_API_KEY>

The authenticated store key determines tenant scope automatically.

Lifecycle

1. Initialize

The client sends an initialize request with a supported protocol version.

2. Negotiation

The server responds with the negotiated protocol version and capabilities.

3. Initialized notification

The client sends notifications/initialized.

4. List tools

The client requests tools/list.

5. Call tools

The client sends tools/call requests to perform merchant operations.

Required HTTP Headers

Authorization: Bearer <STORE_API_KEY>
Content-Type: application/json
Accept: application/json, text/event-stream
MCP-Protocol-Version: <negotiated-version>

Most MCP clients handle the lifecycle and protocol header negotiation automatically.

Low-level Examples

curl -X POST "https://api.ecommaps.com/api/v1/mcp" \
  -H "Authorization: Bearer $ECOMMAPS_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-11-25" \
  -d '{
    "jsonrpc":"2.0",
    "id":"1",
    "method":"initialize",
    "params":{
      "protocolVersion":"2025-11-25",
      "capabilities":{},
      "clientInfo":{"name":"manual-client","version":"1.0.0"}
    }
  }'

Connect Your Client Tool Catalog