ecompick.
For makers中文Submit a tool

Popular seller tasks

Product & keyword researchListings & product copyProduct photosProduct video & ad creativeAdvertising & PPCEmail & marketing

Lingxing MCP

Query store sales and ASIN performance summaries

AmazonOpen source
#mcp
Visit website

Overview

Lingxing MCP provides read-only access to Lingxing ERP data for technical seller teams. Its setup emphasizes fixed outbound IPs, shared access and reusable reporting workflows.

Who it suits

Cross-border seller teams already using Lingxing ERP and its OpenAPI who want repeatable, read-only sales, advertising, inventory, and replenishment analysis through an assistant.

Who it may not suit

A seller without Lingxing OpenAPI access, or a team hoping to change purchase orders and inventory records through this read-only server.

Seller use cases

  • Read store and ASIN sales summaries to investigate which products contributed to a change in sales.
  • Compare advertising and inventory context before preparing a replenishment discussion.
  • Provide a token-protected, read-only reporting gateway for teammates who share an approved analysis scope.

What you can do

  • Query store sales and ASIN performance summaries. ↗
  • Read advertising reports, inventory and replenishment data. ↗
  • Share read-only access through the documented HTTP gateway. ↗

What you need

  • Lingxing OpenAPI access, APP ID/AppSecret and approved outbound IP configuration. Download the repository and set LINGXING_APP_ID, LINGXING_APP_SECRET and LINGXING_TOKEN_CACHE_FILE before starting.

Install

Local stdio

python3 mcp-servers/lingxing-openapi/server.py
Installation source ↗

Permissions & data

Python calls openapi.lingxing.com, uses local OpenSSL for request signing and can expose a token-protected HTTP gateway.

Project info

Maintainer
zach22-1999
GitHub stars at check date
44
Last commit
2026-07-14
License
MIT
Last checked
2026-10-30
GitHub ↗

Pricing at a glance

The connector code is MIT-licensed. Lingxing ERP and OpenAPI access must be arranged with Lingxing; a local Python process or shared gateway also needs an appropriate execution environment.

Open source

Good to know

The integration requires approved outbound IP configuration. A shared gateway also needs its access token protected; expose only the intended audience and distinguish ERP synchronization timing from marketplace reporting time.

Alternatives to Lingxing MCP

Nexscope can structure a growth or replenishment decision from supplied inputs; Lingxing MCP retrieves the ERP evidence those inputs can come from.

Amazon SP-API MCP reaches Amazon reports without an ERP layer; Lingxing MCP uses the connected ERP’s data model and access arrangements.

Frequently asked questions

Can it write back into Lingxing ERP?

The reviewed project is designed for read-only access. Recommendations from its reports still need a separate authorized operating step if an ERP record must change.

Why does setup mention a fixed IP?

Lingxing OpenAPI access uses an approved outbound IP arrangement. Running the client from a different network can fail even when the app credentials are correct.

What runs locally?

The documented Python integration calls Lingxing OpenAPI and uses OpenSSL for signing. Its credential and token-cache settings belong in the deployment environment, not in a shared report.

Does a team gateway remove OpenAPI setup?

No. The gateway shares access to a configured integration; its backend still needs valid Lingxing application credentials, token storage, and an outbound network address accepted by the ERP API.

Checked against the official site on 2026-10-30 · Official source ↗

Sources