In this article
LibreChat agents bind MCP tools in Agent Builder separately from ordinary chat selection; authentication and model capability remain independent.
A connected MCP server does not automatically give every LibreChat agent its tools. Ordinary chats select servers through the composer, while agents carry their own tool configuration in Agent Builder. Check the path you are actually using.
The concrete application boundary
In a regular supported endpoint, open the composer’s + palette, Attach and tools, and select a server under MCP Servers. The selection appears as a chip. Agents and Assistants use their own setup, so that ordinary picker is hidden there. An administrator may also make a server available only to agents. Connection state is another boundary: Disconnected and Needs Auth do not mean the same thing. A server may require the current user’s credential or OAuth sign-in before its tools become available. Finally the selected model must support tool calls. None of these conditions is demonstrated merely by a successful plain-text answer (LibreChat MCP).
A practical route
First identify whether the conversation uses an agent or a regular endpoint. For an agent, open Agent Builder, click Add next to Tools, and filter the Tool Library to MCP servers. Add the required server, keep only the necessary tools, save the agent, and test a new conversation with that agent selected. Inspect any setup or authentication indication for the actual user. Some servers resolve tools only at request time; an upfront list is not always available. Keep that documented case distinct from a server that never connected (LibreChat Agents).
A worked example
A project-note server works in an ordinary chat, but a saved review agent cannot read the same harmless note. The user selected the server in the chat palette and assumed the agent inherited it. Add the server through the agent’s Tool Library, restrict it to the required read tool, and repeat with a fictional note whose contents are independently known.
| Check | Record |
|---|---|
| Conversation path | Regular endpoint selection or the specific saved agent. |
| Binding | The server/tool entry attached through the correct interface. |
| Execution | A returned note value observed in the tool result, not merely guessed in the answer. |
Reading the failure correctly
Current documentation states that an agent configured with MCP tools stops with an error when none are available at run start, rather than silently answering without them. Inspect that error for connection or access loss. If a tool is available but never called, investigate model support and task wording after establishing the binding (LibreChat feature documentation).
What completes the check
The correction belongs to the missing boundary: chat selection, agent binding, user authentication, or model tool capability. A single connected status cannot substitute for all four checks.
Related background: llama.cpp server: a local API from a GGUF model, VRAM for LLMs: why model size is only part of the calculation.