Local direct connection disabled / fixed egress mode available: Due to the IP whitelist restriction of the Lingxing OpenAPI, the local environment cannot access it directly. If a fixed egress gateway has been deployed and
EIPhas been added to the whitelist, you can continue to use this Skill. Before deployment, when Amazon business data is needed, please prioritize switching to Amazon SP-API (MCP:amazon-api)。
Lingxing MCP Operations SkillThis public version of the Skill is self-contained and does not depend on any private workspace files or internal protocols.
Core purpose
- Configure the Lingxing MCP on the fixed egress gateway
- Configure the team
HTTPversion of Lingxing MCP with Bearer - Configure Tailscale + SSH Tunnel access
- Learn which
lingxing_*tools can be called - Troubleshoot environment variables, Bearer, permissions, authorization validity period, and IP whitelist issues
Key locations
mcp-servers/lingxing-openapi/server.pymcp-servers/lingxing-openapi/http_server.pymcp-servers/lingxing-openapi/README.mdmcp-servers/lingxing-openapi/deploy/lib/lingxing_openapi/mcp.py
Environment variables
LINGXING_APP_IDLINGXING_APP_SECRETLINGXING_TOKEN_CACHE_FILELINGXING_MCP_BEARER_TOKENLINGXING_MCP_HOSTLINGXING_MCP_PORT
Common commands
python3 mcp-servers/lingxing-openapi/server.py
python3 mcp-servers/lingxing-openapi/http_server.py --host 127.0.0.1 --port 8099
python3 skills/zach-lingxing-openapi-client/scripts/smoke_check.py
bash mcp-servers/lingxing-openapi/deploy/deploy_gateway_via_ssh.sh --help
bash mcp-servers/lingxing-openapi/deploy/install_tailscale_via_ssh.sh --help
bash mcp-servers/lingxing-openapi/deploy/install_tailscale_on_ubuntu.sh --help
bash mcp-servers/lingxing-openapi/deploy/open_ssh_tunnel.sh --help
bash mcp-servers/lingxing-openapi/deploy/install_gateway_on_ubuntu.sh --help
Tool list
lingxing_health_checklingxing_seller_listslingxing_marketplaceslingxing_store_saleslingxing_asin_daily_listslingxing_product_performancelingxing_orderslingxing_promotion_listinglingxing_promotion_sec_killlingxing_promotion_managelingxing_promotion_vip_discountlingxing_promotion_couponlingxing_resolve_daily_promotionslingxing_ad_accountslingxing_ads_sp_*lingxing_ads_sd_*lingxing_ads_sb_*lingxing_profit_sellerlingxing_profit_asinlingxing_profit_parent_asinlingxing_source_*lingxing_fba_*lingxing_replenishment_*lingxing_report_export_*lingxing_asin_ads_daily_rolluplingxing_asin_weekly_rolluplingxing_exp_*lingxing_smoke_check
Troubleshooting principles
- First run
lingxing_health_checkto check environment variables and token - Then run
lingxing_smoke_checkto checkSellerLists -> StoreSales -> Orderlists -> promotionListingList - If it is
403, prioritize going back to the Lingxing backend to check the authorization validity period, API permissions, and IP whitelist - If in HTTP mode it reports
missing_or_invalid_bearer, only look at the Bearer Token, and do not first suspect the Lingxing API
Risks and boundaries
- risk-level: low — only performs MCP service configuration and troubleshooting, and does not write business data
Upstream / Downstream
- Upstream:
zach-lingxing-openapi-client(API authentication foundation) - Downstream: all Skills that depend on Lingxing MCP tools (
zach-lingxing-sales-anomaly-monitor, etc.)
After completion
Report completion status: DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT