SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillslinkfox-lingxing-erp

linkfox-lingxing-erp

Agents & models

View repository

Updated 10-15 14:54

About this skill

Install the official Lingxing MCP

Only guide the installation of the official Lingxing MCP; do not wrap, proxy calls to, or explain any Lingxing business Tool/API.

Official basis

  • Use only the official Lingxing guidance as the basis:https://www.lingxing.com/help/article/mcp
  • If the server URL, button names, transport method, or configuration fields differ from the official page, the current content of the official page shall prevail.

Mandatory process

  1. Identify the client the current Agent is in and its MCP installation method. You may first perform a read-only check of whether there is already a lingxing-mcp connection; do not discover, list, or call Lingxing business tools.
  2. State the prerequisites: paid Lingxing users need a super administrator to enable the feature in [Business Configuration] → [Open API] → [MCP], and the current account also needs to have the corresponding permissions.
  3. Before requesting any configuration value, fully read references/install.md, and send the text and official Lingxing screenshots according to the "graphical guidance that must be shown to the user" in it. Do not just send a single sentence saying "go get the X-Mcp-Key".
  4. Have the user personally copy two configuration items in Lingxing ERP:
    • The MCP Server URL；
    • X-Mcp-Key authentication key corresponding to the current account.
  5. Prefer to receive the key through the current client's secure credential input, Secret Store, or private configuration interface. If the client has no secure input channel, have the user fill in the configuration locally according to references/install.md , and only reply "configured"; do not ask the user to paste the full key in ordinary chat.
  6. Save the connection using the current client's native MCP add method: use lingxing-mcpfor the name, use Streamable HTTP / HTTP Streamingfor the request header name. X-Mcp-Key。
  7. Before saving, explain to the user which client will be written to and which server domain will be used, and show only the masked key. If the user has explicitly requested installation or configuration, you may continue directly; otherwise, obtain explicit consent first.
  8. Only verify whether the MCP connection, authentication, and tool discovery succeed. Do not call any tool that reads or writes Lingxing business data for verification purposes.
  9. After success, only report that the connection has been installed and the verification result. Subsequent data tasks are handled by the installed official Lingxing MCP; do not provide invocation methods in this skill.

Security boundaries

  • Do not log in to Lingxing on behalf of the user, do not ask for account passwords or verification codes, and do not create, copy, regenerate, or rotate keys for the user.
  • Treat both the MCP Server URL and X-Mcp-Key as sensitive configuration; do not echo them, record them in logs, commit them to repositories, or write them into example files.
  • Do not put real keys into shell commands, command history, screenshots, test output, or troubleshooting reports.
  • If the user has already pasted the key in chat, do not repeat or use that value; treat it as exposed, and have the user first manually regenerate it in [Manage MCP], then provide the new key through a secure method.
  • If leakage is suspected, stop configuration and have the user manually regenerate it on the [Manage MCP] page.

Troubleshooting scope

Only troubleshoot installation and authentication:

  • MCP feature not visible: confirm paid eligibility and whether the super administrator has enabled it.
  • Authentication failed: confirm the URL uses https://, the Header name is X-Mcp-Key, and the key is copied completely with no extra spaces.
  • Permission mismatch: explain that the server URL is bound to the permissions of the current Lingxing account, and have the user switch to the correct account and copy again.
  • The client does not support custom Streamable HTTP MCP: clearly state that the client cannot be installed this way, and guide the user to check the client's official MCP support documentation.

Do not diagnose via curl, Python, OpenAPI, or MCP Tool calls, and do not query inventory, orders, profit, advertising, Listing, or other business data.