360 Secure SkillHub
360 安全技能中心

Lingxing MCP

该 Skill 是 Lingxing ERP MCP 的调用封装：先用 oo connector schema 查看工具契约，再用 oo connector run 执行 list_tools 与 call_tool。凭证由 OOMOL 服务端注入；带 write 标记的操作需先与用户确认。不包含具体工具字段定义与连接建立流程。

oomol
oomol
热度 37.31
最近更新 2026-09-20 11:12:09
分类：自动化依赖：代码执行 / MCP 服务 / 第三方 API应用场景：工作流 / 数据处理 / API 集成

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-lingxing-mcp
Metadata
name
oo-lingxing-mcp
description
Lingxing MCP (lingxing.com). Use this skill for ANY Lingxing MCP request — reading, creating, and updating data. Whenever a task involves Lingxing MCP, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Lingxing MCP","author":"OOMOL","version":"1.0.3","services":["lingxing_mcp"],"icon":"https://static.oomol.com/logo/third-party/lingxing_mcp.png"}

Lingxing MCP

Operate Lingxing MCP through your OOMOL-connected account. This skill calls the lingxing_mcp connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Lingxing MCP. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "lingxing_mcp" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "lingxing_mcp" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • call_tool — Call a current Lingxing ERP MCP tool with JSON arguments. Discover the tool first and confirm the user's intent because some Lingxing tools create or update ERP data. [write]
  • list_tools — Discover the current Lingxing ERP MCP tools, behavior annotations, and live input schemas before choosing a tool to call.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Lingxing MCP state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Lingxing MCP is not connected, or the connection expired or lacks a scope. Connect once (auth type: custom credential) at:

    https://console.oomol.com/app-connections?provider=lingxing_mcp

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources