Add URL parameter support for pre-selecting MCP servers in chat initialization

[abhishekag03]

Currently, LibreChat supports various URL parameters for initializing chats with specific models, endpoints, and settings (via tQueryParamsSchema), but there's no way to pre-select MCP (Model Context Protocol) servers through URL parameters. Users must manually select MCP servers from the UI after navigating to a chat.

Something like this URL would be good to have:
https://your-librechat-instance.com/c/new?endpoint=openAI&model=gpt-4&mcp=["jira","github"]

Use Cases

• Direct Links: Share links that automatically set up conversations with specific MCP tools enabled
• Bookmarks: Users can bookmark URLs for quick access to frequently-used MCP configurations
• Integration: External systems can generate deep links to LibreChat with pre-configured MCP servers
• Workflow Automation: Streamline user workflows by eliminating manual MCP selection steps
• Documentation: Link to specific chat configurations in documentation or support materials

The issue with using Agents (having the above MCP enabled) is that it takes away the freedom from users to switch model or prompts. I see use cases where users just want to use a particular mcp and struggle finding that option.

I'm happy to work on implementing this if @danny-avila thinks this would be a valuable adoption.
I'm planning to extend the existing tQueryParamsSchema

[abhishekag03]

@danny-avila what are your views on the above feature request? Shall we go about implementing this?

[EfrosIonelu]

Hi, today i installed libre chat and i see that i require this

[csalvato]

Aside from just MCPs being enabled, supporting params for all the configuration options (e.g. artifacts, shadcn, etc) would also be useful 🤔

[digas111]

Just chipping in as I have a similar use case. For me, the benefits of choosing MCP Servers without having an Agent are two:

• Agents do not support setting a promptPrefix via URL. So there is no real way of having a dynamic promptPrefix and at the same time choose a MCPServer (unless I'm missing something)
• URL parameters are most useful for embedding Librechat as an iframe. Having to manage Agents manually in Librechat just to be able to choose a MCPServer makes this much harder. MCPServers are configured in the yaml file so I can have them preconfigured with a specific name that my app knows to pass to Librechat via URL. With Agents I could not have the AgentID preconfigured.

I see that Agents are useful, but I don't see a reason why choosing an MCPServer by URL would not also make sense!

[rio100]

Great points!

What you are describing makes sense, especially if you are going to integrate other wares to make the URL calls with dynamic system prompts and MCP selections. However, I see this as a workaround to the greater need of an API layer that grants a great deal of privilege to do many novel use cases from LC.

If you guys don't get a response soon, just know that LC has been pushing up the release of the Admin Panel which is now expected this month after tying down lose ends and stuff. That implementation in itself may have to incorporate this use case as I imagine the Admin Panel will control the source of truth on LC: the who, what, when, and how. I haven't seen it but given the productions Danny and Team have done thus far, I believe it will be an epic addition.

[csalvato]

Even if there's an admin panel that let's us choose defaults (e.g. Artifacts always on), having these be configurable via URL is very powerful.

It allows easy sharing of a one-off config without the weight of using an agent.

LibreChat shines in it's easily-sharable viral nature. Having URL params drive one-off config lends to that.

[rio100]

Interesting thoughts all around. Here's a little snippet of what's to come regarding the admin panel in case you haven't seen it.

"The Admin panel will be a separate, optional app that acts as a Content Management System (CMS) for LibreChat, including management of usage, chats, users, settings, and access controls."

https://www.librechat.ai/blog/2025-02-20_2025_roadmap#focus-item-admin-panel

[abhishekag03]

+1 to @csalvato. Having these as URL params makes MCPs easily sharable - especially useful for non-tech and users new to LibreChat.

@danny-avila do let us know your thoughts on this