SuperAPI AI Directory

zach-lingxing-mcp

General & other

View repository

Updated 10-16 09:30

About this skill

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 EIP has 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)。

This public version of the Skill is self-contained and does not depend on any private workspace files or internal protocols.

Lingxing MCP Operations Skill

Core purpose

  • Configure the Lingxing MCP on the fixed egress gateway
  • Configure the team HTTP version 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.py
  • mcp-servers/lingxing-openapi/http_server.py
  • mcp-servers/lingxing-openapi/README.md
  • mcp-servers/lingxing-openapi/deploy/
  • lib/lingxing_openapi/mcp.py

Environment variables

  • LINGXING_APP_ID
  • LINGXING_APP_SECRET
  • LINGXING_TOKEN_CACHE_FILE
  • LINGXING_MCP_BEARER_TOKEN
  • LINGXING_MCP_HOST
  • LINGXING_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_check
  • lingxing_seller_lists
  • lingxing_marketplaces
  • lingxing_store_sales
  • lingxing_asin_daily_lists
  • lingxing_product_performance
  • lingxing_orders
  • lingxing_promotion_listing
  • lingxing_promotion_sec_kill
  • lingxing_promotion_manage
  • lingxing_promotion_vip_discount
  • lingxing_promotion_coupon
  • lingxing_resolve_daily_promotions
  • lingxing_ad_accounts
  • lingxing_ads_sp_*
  • lingxing_ads_sd_*
  • lingxing_ads_sb_*
  • lingxing_profit_seller
  • lingxing_profit_asin
  • lingxing_profit_parent_asin
  • lingxing_source_*
  • lingxing_fba_*
  • lingxing_replenishment_*
  • lingxing_report_export_*
  • lingxing_asin_ads_daily_rollup
  • lingxing_asin_weekly_rollup
  • lingxing_exp_*
  • lingxing_smoke_check

Troubleshooting principles

  1. First run lingxing_health_check to check environment variables and token
  2. Then run lingxing_smoke_check to check SellerLists -> StoreSales -> Orderlists -> promotionListingList
  3. If it is 403, prioritize going back to the Lingxing backend to check the authorization validity period, API permissions, and IP whitelist
  4. 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