Compatible with every major AI agent and IDE
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 CrewAI?
When paired with CrewAI, LibreChat becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call LibreChat tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
LibreChat in CrewAI
LibreChat and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect LibreChat to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Telegram Bot
13 toolsControl Telegram bots programmatically — send messages, photos, documents, and manage chats via AI.

Beeline
10 toolsManage your external workforce via Beeline VMS — list assignments, requisitions, and timesheets directly from any AI agent.

Open Brewery DB Alternative
11 toolsSearch and discover craft breweries worldwide — find locations, types, and contact info via AI.

Cloud Assess
8 toolsManage vocational training and assessments via Cloud Assess — track students, monitor enrolments, and audit assessment records directly from any AI agent.
