Lingxing MCP MCP integration for AI agents.
Connect AI agents to Lingxing MCP through 2 structured actions, including list tools and call tool. Review authentication, inputs, workflows, and safety guid…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Lingxing MCP integration exposes
The Lingxing MCP Agent App exposes 2 provider-backed actions for productivity, data, and marketing work. Its current contract lets an authorized agent discover the current lingxing erp mcp tools, behavior annotations, and live input schemas before choosing a tool to call and 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. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Lingxing MCP account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Lingxing MCP capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_toolsREADDiscover the current Lingxing ERP MCP tools, behavior annotations, and live input schemas before choosing a tool to call.
call_toolREVIEWCall 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.
INPUTS: toolName / arguments
INPUT CONTRACTS
Know what the action needs before it runs.
call_tool
toolNameREQUIRED- The exact tool name returned by list_tools.
argumentsOPTIONAL- JSON arguments matching the inputSchema returned for the selected tool.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Tools
Discover the current Lingxing ERP MCP tools, behavior annotations, and live input schemas before choosing a tool to call. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_toolsVerify with 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. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
call_toolSAFETY BOUNDARY
Operate Lingxing MCP with explicit limits
- Authorize Lingxing MCP with Custom credentials and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Lingxing MCP data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Lingxing MCP rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Lingxing MCP task completed successfully.
CONNECTION MODEL
Custom credentials
Lingxing MCP uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Lingxing MCP.