Tools connects external MCP services to conversations. You enable MCP, register Streamable HTTP servers, sync their tools, edit how each tool appears, and cap how much work one message can trigger.

Where to find it#

Open Tools in the admin console. The page has three parts:

1. Global MCP settings at the top.
2. The MCP servers table.
3. A per-server MCP tools sheet that opens when you click a tool count.

The global settings are hidden while Enable MCP tools is off. Users cannot select MCP tools until the switch is on, the server is On, the tool is Enabled, and the per-message limits allow it.

Turn MCP on and set limits#

1. Turn on Enable MCP tools.
2. Set Selectable tools per message. Default 32, maximum 128.
3. Set Max LLM requests. Default 5, minimum 2. This counts the first request and the final summary in one message.
4. Set Max MCP tool calls. Default 8. Failed calls count toward the limit.
5. Set MCP tool concurrency. Default 8. This is the limit per service instance.
6. Set MCP tool timeout. Default 10 seconds.
7. Set MCP tool retries. Default 0.
8. Optionally edit MCP tool prompt to control when and how the model calls tools. Leave it empty to use the built-in default prompt.
9. Click Save. The button appears only after a field changes.

Turning the switch off hides the server and tool lists. Existing server and tool records are kept.

Add an MCP server#

1. Click Add above the server table.
2. Fill in Server name.
3. Choose Server status: On or Off.
4. Enter Server URL, the MCP Streamable HTTP endpoint, for example https://example.com/mcp.
5. Optionally enter Auth token. On create the placeholder is "Optional"; on edit it is "Leave empty to keep unchanged".
6. Optionally enter Headers as JSON, for example {"X-API-Key": "..."}.
7. Click Create. The dialog saves the server, then syncs its tools automatically.

Use Quick fill next to Headers to insert Signed user context, which adds:

{  "X-Deeix-User-Context": "${DEEIX_SIGNED_USER_CONTEXT}"}

If a header with the same name already exists with a different value, the preset is not applied and you see "Header already exists with a different value; nothing was changed".

Sync tools#

1. Click the sync icon on a server row, or open the server's tools sheet and click Sync.
2. If the server already has customized names or descriptions, pick how to handle them:
   • Keep current content — keep names and descriptions while syncing other tool data.
   • Use server content — sync the names and descriptions returned by the MCP server.
3. Wait for "MCP tools synced".

Sync again whenever the external service adds, removes, or changes tools. Sync only reads the server's tool list and schema; it does not judge whether a tool is safe to expose.

Manage tools#

Open a server's tools sheet by clicking its tool count, for example 3/8 (enabled/total).

• Search by tool name or description.
• Filter by Status: All, Enabled, Disabled.
• Sort by Custom order, Name A-Z, Name Z-A, Status, Recently updated, or Oldest updated.
• Toggle a single tool with its Enabled switch.
• Select tools and use Enable or Disable for a bulk change. A confirmation dialog shows the selected count.

If a server has never been synced, the sheet shows "No tools. Sync first." A server sync failure is shown above the tool table as an error message.

Edit tool display and image routing#

1. Click the pencil on a tool row.
2. Edit Display name. This is what users see in the conversation tool selector. It can be up to 160 characters.
3. Edit Description. Users read it to decide when to use the tool. It can be up to 4096 characters.
4. Click Save.

For tools that accept image data, turn on Image attachment processing. The backend calls the tool first and the main model receives only the tool's text result. The fields are mapped manually from the tool schema; nothing is detected automatically.

The save button stays disabled until every required schema argument is mapped to the image argument or the user request argument. Unmapped required arguments are listed as "Unmapped required arguments: {names}". If the schema has no string argument, you see "This tool schema has no string argument for image data, so this capability cannot be enabled."

Click the schema icon to open Tool schema and read the input parameter JSON Schema. You can copy it from the dialog.

Reorder the conversation selector#

1. Click Order above the server table.
2. Drag servers in the MCP servers list to change their order.
3. Select a server and drag tools in the Tools list to change their order within that server.
4. Click Save. The tool sort resets to Custom order after saving.

Reference#

Global settings#

Server URLs, auth tokens, headers, and tool schemas are service and tool records, not these global mcp.* settings.

Server fields#

Troubleshooting#

Related#

• Billing for per-call MCP tool pricing.
• Capabilities & pass-through for native tool behavior.
• Logs for tool call events and failures.