Bring Llm Orchestration
to Claude Desktop
Learn how to connect LibreChat to Claude Desktop and start using 4 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the LibreChat MCP Server?
Connect your LibreChat instance to any AI agent and gain programmatic control over your self-hosted AI ecosystem. This server allows you to bridge your custom agents and models with any MCP-compatible client.
What you can do
- Agent Orchestration — List all available agents and models configured in your LibreChat environment.
- Unified Completions — Create chat completions using the Agents API, providing an OpenAI-compatible interface for your custom setups.
- Open Responses — Utilize the Open Responses API specification to generate structured AI outputs.
- Session Management — Authenticate directly via email and password to retrieve access tokens when a static API key is not preferred.
How it works
- Subscribe to this server
- Provide your LibreChat Base URL and API Key (or use the login tool)
- Start interacting with your private LLM agents through Claude, Cursor, or other MCP tools.
Who is this for?
- AI Engineers — integrate self-hosted LibreChat agents into automated workflows and IDEs.
- DevOps Teams — monitor and query available model configurations across different environments.
- Power Users — centralize access to multiple private LLMs through a single, secure interface.
Built-in capabilities (4)
Model corresponds to an Agent ID. Create a chat completion using the Agents API
List available LibreChat models/agents
Login to LibreChat to get access and refresh tokens
Create a response using the Open Responses API
Why Claude Desktop?
Claude Desktop is the definitive way to connect LibreChat to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 4 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
LibreChat in Claude Desktop
LibreChat and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect LibreChat to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for LibreChat in Claude Desktop
The LibreChat MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 4 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
LibreChat for Claude Desktop
Every tool call from Claude Desktop to the LibreChat MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I see which agents are currently available in my LibreChat instance?
You can use the list_models tool. It will query your configured LibreChat instance and return a list of all accessible agents and models associated with your credentials.
Can I use this server to chat with a specific agent by its ID?
Yes! Use the chat_completions tool. Simply provide the model (which is the Agent ID) and an array of messages to generate a response from that specific agent.
What should I do if I don't have a static API key for my instance?
You can use the login tool. By providing your email and password, the server will authenticate with LibreChat and retrieve the necessary access tokens for subsequent requests.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
arXiv
2 toolsSearch 2.5M+ scientific preprints across physics, computer science, mathematics, biology, economics, and more — with full abstracts, author lists, and direct PDF download links.
RenderMe
12 toolsAutomate video generation via RenderMe (re.video) templates directly from your AI agent.
MRPeasy
10 toolsManage manufacturing and inventory via MRPeasy — track customer orders, MOs, and stock items directly from your AI agent.
Webiny CMS
9 toolsManage content models, entries, and GraphQL workflows on Webiny — the enterprise open-source headless CMS.