Boxem MCP for Openclaw

1. Add the Boxem MCP server with mcporter

mcporter config add boxem --url https://new.boxem.com/backend/mcp
mcporter list boxem --schema

2. Configure an MCP client directly

Add the following server definition to the client configuration:

{
  "boxem": {
    "url": "https://new.boxem.com/backend/mcp",
    "transport": "sse"
  }
}

3. Verify connectivity

Use the client schema or tool-listing command to confirm that Boxem tools are available. The server endpoint is https://new.boxem.com/backend/mcp, and the required transport is Server-Sent Events (SSE).

4. Start with read-oriented operations

Test catalog lookup, daily analytics, knowledge lookup, or supplier retrieval before running listing creation, HTTP requests, code execution, or background jobs. Confirm authentication and platform permissions according to the Boxem environment.

Connection metadata

Functional data domains

• Amazon catalog data: ASINs, product names, and sales ranks.
• Listing controls: restriction checks, ungate URLs, and listing creation requests.
• Seller analytics: SKU-level item analytics and daily statistics over date ranges up to 30 days per call.
• Automation: Lua source or file paths, proxied HTTP requests, and interval-job UUIDs with token usage details.
• Knowledge: an indexed collection of files covering FBA, WFS, e-commerce, Boxem, and selling advice.
• Suppliers: seller supplier records returned by the Boxem platform.
• Memory: persistent, file-based user preferences and conversational context.
• Notifications: email and in-app notification events.

The skill does not specify a local output directory or a fixed client-side file format. Knowledge files, memory files, Lua files, analytics records, and job metadata are handled through the connected Boxem tools and the MCP client configuration.