ruflo/src/ruvocal/docs/source/configuration/mcp-tools.md
Chat UI supports tool calling via the Model Context Protocol (MCP). MCP servers expose tools that models can invoke during conversations.
Chat UI supports two types of MCP servers:
Base servers are configured by the administrator via environment variables. They appear for all users and can be enabled/disabled per-user but not removed.
MCP_SERVERS=[
{"name": "Web Search (Exa)", "url": "https://mcp.exa.ai/mcp"},
{"name": "Hugging Face", "url": "https://hf.co/mcp"}
]
Each server entry requires:
name - Display name shown in the UIurl - MCP server endpoint URLheaders (optional) - Custom headers for authenticationUsers can add their own MCP servers directly from the UI:
User-added servers are stored in the browser and can be removed at any time. They work alongside base servers.
When users are logged in via Hugging Face, you can forward their access token to MCP servers:
MCP_FORWARD_HF_USER_TOKEN=true
This allows MCP servers to access user-specific resources on their behalf.
Not all models support tool calling. To enable tools for a specific model, add it to your MODELS override:
MODELS=`[
{
"id": "meta-llama/Llama-3.3-70B-Instruct",
"supportsTools": true
}
]`
When a model decides to use a tool:
When using the LLM Router, you can configure automatic routing to a tools-capable model:
LLM_ROUTER_ENABLE_TOOLS=true
LLM_ROUTER_TOOLS_MODEL=meta-llama/Llama-3.3-70B-Instruct
When a user has MCP servers enabled and selects the Omni model, the router will automatically use the specified tools model.