MCP Tools connect external MCP services to conversations. Administrators can enable MCP, configure service endpoints, sync tools, edit display information, and limit tool selection and execution.
Entry Point#
Open Tools in the admin console. The page includes global MCP settings, MCP service list, and MCP tool list.
Whether users can select MCP tools depends on the global switch, service status, tool status, and administrator execution limits.
Global Settings#
Global settings control whether MCP is available and how much work one message can trigger.
| Setting | Impact |
|---|---|
| Enable MCP tools | When off, users cannot select MCP tools. |
| Tools selectable per message | Limits how many tools a user can select for one message. |
| Max LLM requests | Limits total model requests in a tool chain, including initial request and final summary. |
| Max tool calls | Limits total tool calls for one message; failed calls count too. |
| Concurrency limit | Limits simultaneous tool calls for one service instance. |
| Tool timeout | Limits waiting time for one tool call. |
| Retry count | Controls retries after tool call failure. |
These limits protect platform stability. Too many tools or calls can slow responses, raise cost, or overload external services.
MCP Services#
The service list shows service name, address, status, tool count, and sync time. Administrators can create, edit, enable, disable, delete, or sync tools for a service.
Creating a service requires name, service address, status, auth token, and headers. Auth tokens are not fully shown after saving; leaving the field blank while editing usually keeps the old token.
Disabled services no longer offer tools to users. Before deleting a service, confirm its tools are no longer used.
Tool Sync#
Tool sync reads tool name, description, and input Schema from the MCP service and updates the admin tool list. After creating a service, sync first and review each tool before enabling it.
Sync again when the external service adds, removes, or changes tools. Sync does not judge business safety; administrators still need to review descriptions, parameters, and enabled status.
Tool List#
The tool list supports searching by name or description, filtering by status, and sorting. Administrators can enable or disable individual tools, or bulk enable and disable selected tools.
Disable tools when they are high risk, temporarily broken, unstable, or return low-quality results. Confirm service recovery before enabling again.
Edit Tool Display#
Administrators can edit display name and description. The display name appears in the user tool selector, and the description helps users decide when to use it.
Descriptions should explain what the tool is good at, what it is not good at, and what input it needs. Do not include internal secrets, private addresses, or sensitive workflows.
View Schema#
Tool Schema shows the input parameter structure. It helps administrators judge whether users can use the tool correctly and whether sensitive parameters exist.
If parameters are complex, add usage context in the description. If a tool performs high-risk actions, keep it disabled until permission and audit policies are ready.
Practical Tips#
Start with a few read-only, low-risk tools. Verify service stability and user experience before enabling write or external-action tools. Set reasonable timeout and concurrency so one tool does not slow the entire conversation. After tool changes, sync and review enabled status.