Use Desearch MCP in LibreChat v0.8.8

    Use Desearch MCP in LibreChat v0.8.8

    Tested 17 November 2026.

    For developers administering an existing, working LibreChat installation who want to call Desearch from chat. This guide covers the remote MCP connection and its native chat validation. Complete LibreChat's official installation and configure a tool-capable model before these steps.

    Requirements

    Tested with LibreChat v0.8.8, source commit e8f3be08623663d4ad7f7241e693c94469b63bb0, using the official Linux ARM64 image registry.librechat.ai/librechat-ai/librechat@sha256:0dba606ca84b6fdf313718d11e4fbf6874baf0122269676d83db3987377151e2 and MongoDB 8.0.20 at mongo@sha256:098862b1339f031900ca66cf8fef799e616d6324fa41b9a263f2ec899552c1ef. The test used Docker Engine 29.5.2 on Apple Silicon, a native llama.cpp b12478 server, Qwen3 0.6B GGUF weights sha256:7f4030143c1c477224c5434f8272c662a8b042079a0a584f0a27a1684fe2e1fa, 32,768 tokens of context and thinking disabled. No hosted model account was used. Other models and operating systems were not tested.

    You need a LibreChat login with permission to use MCP servers and access to its server configuration. The local open-source deployment was tested; no hosted LibreChat plan claim is made. Your model must support tool calls and have sufficient context for the discovered tool schemas. The test discovered 39 Desearch tools; discovery counts can change.

    You also need a Desearch API key with available credits and outbound HTTPS access to https://mcp.desearch.ai/mcp. Requests consume Desearch account credits; consult current pricing. The hosted endpoint's server version was not pinned, so this is a dated behavior test.

    Configure the connection

    Provide DESEARCH_API_KEY to the LibreChat server process through your secret manager. For Docker, pass the environment variable into the app container; setting it only in the host shell does not automatically expose it inside a container. Keep the value out of YAML, chat messages and browser code.

    Merge this section into the librechat.yaml used by your server, preserving your existing model and application settings:

    yaml
    mcpServers: desearch: type: streamable-http requiresOAuth: false url: https://mcp.desearch.ai/mcp timeout: 60000 headers: Authorization: "Bearer ${DESEARCH_API_KEY}"

    Restart the LibreChat application using the same configuration file and environment. The test mounted librechat.yaml read-only at /app/librechat.yaml, set CONFIG_PATH to that path, and passed DESEARCH_API_KEY by environment variable name. Use your installation's normal restart procedure. The requiresOAuth setting selects static bearer authentication; LibreChat documents that automatic OAuth detection does not include configured headers in its probe.

    Validate in native chat

    1. Log in to LibreChat and open a new chat.
    2. Use Select a model to choose your configured tool-capable model.
    3. Open MCP Servers beside the message composer and select desearch. It should show Connected.
    4. Send this exact prompt: Use exactly the function named web-search_mcp_desearch with arguments {"query":"Python official documentation"}. After the function returns, copy the first result title and link exactly.
    5. Expand the completed tool call and inspect its output. Confirm that web-search_mcp_desearch returned a nonempty data array with a title and link. A connected status or a model-written title alone does not establish a successful search.

    The real test returned a titled Python documentation result through LibreChat's native MCP tool call. Results may vary. A link beginning /go/v1/ is a Desearch redirect path; preserve the returned value. The small test model sometimes altered that path in its prose answer, so verify the tool output rather than treating its rewritten URL as authoritative.

    Troubleshooting

    If desearch is missing, check that the app loaded the intended librechat.yaml and received DESEARCH_API_KEY, then restart it. An unexpected OAuth prompt can indicate that requiresOAuth: false was omitted for this bearer-authenticated configuration.

    An unauthenticated request to LibreChat's /api/mcp/tools returned 401 during testing; log in normally. This is the app's login guard and does not validate your upstream Desearch key. Discovery may succeed before a billed search does. For a rejected search or insufficient credits, verify your key and available balance before retrying.

    If the model chooses search_mcp_desearch instead, repeat the exact web-search prompt above and inspect the actual function name. The initial small-model attempt chose the other function and returned an empty result; it was not counted as a passing web-search validation. If the tool call fails or the model never calls it, check model tool support, context capacity, app logs and network access. Do not infer successful compatibility from a prose response alone.

    Official references