LibreChat MCP. Control your self-hosted agents directly from any client.
LibreChat MCP connects your self-hosted AI instances to any agent client. It lets you manage custom agents, list all available models, and generate chat completions using an OpenAI-compatible interface for your private LLM setups.
Give Claude and any AI agent real-world access
You can ask the MCP for a full list of every agent and model configured in your LibreChat instance.
The MCP sends messages to specific agents, generating responses that mimic standard chat completion APIs.
You prompt the agent for output and receive a highly structured response using the Open Responses API format.
The MCP allows you to log in directly with your email and password, obtaining required access tokens without needing static API keys.
Ask an AI about this
Waiting for input…
What AI agents can do with LibreChat: 4 Tools for Agent Operations
These tools let you manage authentication, list available agents, send chat prompts, and force structured data output directly from your self-hosted LibreChat environment.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using LibreChat MCPChat Completions
Creates a chat completion using the Agents API, allowing you to send prompts and get model responses.
List Models
Retrieves a list of all available models and agents configured in your LibreChat...
Login
Authenticates you with your credentials, retrieving necessary access and refresh...
Open Responses
Generates a structured AI output using the Open Responses API specification.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with LibreChat, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by LibreChat. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The pain of model sprawl
Today, getting your agent client to talk to different private models is a nightmare. You have to jump between five different dashboards, copy-pasting keys and unique endpoints every time you want to test something new or run a report.
With this MCP, you plug it in once. Your agent client talks directly to the LibreChat MCP. You simply list your agents using `list_models`, then send all your prompts through one unified API call, regardless of which underlying model actually answers.
LibreChat MCP: Accessing Every Model
You eliminate the manual steps of finding agent IDs, managing disparate keys, and writing wrapper code for every unique LLM endpoint you use.
The result is simple: your agents feel like they live in one place. You get instant, programmatic access to your entire private model catalog.
What LibreChat MCP does for your AI
Connecting your own LibreChat environment through this MCP gives your AI client direct control over your private language model ecosystem. Instead of relying on a single provider's features, you can treat your self-hosted agents like any other tool right inside Claude or Cursor. You first use the login tool to authenticate with your credentials and grab necessary access tokens.
Once authenticated, you can list everything available using list_models. After that, you send requests via chat_completions to run chats against specific agents. Need structured data? The open_responses tool handles that too. This makes building complex agent workflows simple, letting your AI client talk directly to the models you set up yourself.
It’s a solid way to centralize access to multiple private LLMs through one secure interface on Vinkius.
019e38b7-ad28-7040-9c37-38d0f1a714b2 How to set up LibreChat MCP
The bottom line is, it gives your AI client programmatic access to run and manage every model in your self-hosted LibreChat environment.
Subscribe to the LibreChat MCP and provide your Base URL. If you don't have an API key, use the login tool with your email and password.
Use list_models to confirm that all desired agents are visible to your AI client.
Send a prompt using either chat_completions or open_responses, targeting the specific agent ID you need.
Who uses LibreChat MCP
This MCP is for the developer or engineer who runs their own private LLM infrastructure. If you spend time connecting different APIs just to keep your models running, this is for you.
You use the MCP to connect complex, self-hosted agent systems into automated IDE workflows or production code.
You monitor and query model configurations across multiple private environments, ensuring consistent access for your teams.
You need to centralize access to several niche or experimental LLMs without having dozens of API keys scattered everywhere.
Benefits of connecting LibreChat MCP
You get centralized control over multiple private LLMs. Instead of managing separate API keys for every model, you connect once to the LibreChat MCP and gain access to everything.
The chat_completions tool lets you run complex chats against agents using a standard OpenAI-compatible interface, making integration painless for your developers.
Authentication is easier with login. You can log in directly using credentials (email/password) instead of relying solely on static API keys.
Structured data output is guaranteed via the open_responses tool. If you need JSON or a specific schema from an agent, this ensures your response format is consistent every time.
The list_models capability instantly shows you what agents are available, saving you the headache of guessing which IDs to use in your workflows.
LibreChat MCP use cases
Building an internal research assistant
A researcher needs their agent client to talk to five different specialized models. Instead of configuring five separate API endpoints, they connect the LibreChat MCP, run list_models to verify all agents are online, and then use chat_completions to route queries dynamically based on the prompt topic.
Automating compliance reporting
A DevOps team needs an agent to summarize operational data into a strict JSON format. They connect via LibreChat MCP and use open_responses, forcing the model output into a predictable, machine-readable structure that can be automatically ingested by another system.
Integrating legacy LLMs
A developer has an older, specialized agent running on custom hardware. They connect it through LibreChat MCP and expose its functionality via chat_completions, allowing modern tools like Cursor to interact with the old system without code changes.
Testing new agents quickly
A power user wants to test an experimental agent before deploying it widely. They first use login for quick authentication, then run list_models to find the specific ID, and finally execute a few test prompts using chat_completions.
LibreChat MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Using single-purpose APIs
Trying to connect your agent client only through an 'OpenAI Completions' wrapper when you actually need access to specialized, self-hosted agents.
Use the LibreChat MCP. It provides a unified interface that accepts custom, private LLMs and exposes them through both chat_completions for chat flow and open_responses for structured data.
Hardcoding API keys
Storing static API keys in your client configuration file, which is a major security risk if the repo gets compromised.
Start with the login tool. It lets you authenticate securely using your email and password to obtain temporary access tokens for your session.
Assuming model availability
Writing code that calls an agent ID (agent_xyz) without first verifying if that agent is actually configured or online in the LibreChat instance.
Always run list_models first. This ensures your agent client knows exactly which models are currently available and ready to take requests.
When to use LibreChat MCP
Use this MCP if your primary pain point is managing a diverse, self-hosted collection of AI agents or LLMs that aren't connected via one single service. This connector lets you treat multiple private systems (like custom internal tools) as one cohesive unit for your agent client. Don't use it if all the models you need are already hosted under a single commercial endpoint with no customization required, because then a generic API wrapper will suffice. If you only need basic chat completion and don't care about structured output or managing multiple agents, this MCP gives you too much power—and that's usually what you want.
Frequently asked questions about LibreChat MCP
How do I get started with the LibreChat MCP? +
You start by subscribing to the MCP and running the login tool using your credentials. This authenticates you and gives your agent client the necessary tokens for subsequent calls.
Can I use chat_completions with agents that aren't OpenAI-compatible? +
Yes, that is the point of this MCP. It provides an OpenAI-compatible interface layer over your self-hosted LibreChat environment, making diverse models appear uniform to your client.
Is there a way to check which agents are active in my LibreChat instance? +
Use the list_models tool. It provides an immediate overview of all available agents and model configurations, saving you from guessing IDs.
What if I need the output data to be perfectly formatted JSON? +
For guaranteed structure, use the open_responses tool. This API is specifically designed to force your agent's response into a predictable format that downstream systems can read.
Does this MCP require me to modify my core AI client code? +
No. You connect the LibreChat MCP through your existing compatible client (Claude, Cursor, etc.). The tool handles the complex routing and API translation for you.