Compatible with every major AI agent and IDE
What is the Open WebUI MCP Server?
Connect your Open WebUI instance to any AI agent and take full control of your local and cloud LLM orchestration through natural conversation.
What you can do
- Model Management — Use
list_modelsto fetch all available models including Ollama, OpenAI, and Open WebUI Functions. - RAG & Knowledge Base — Upload files with
upload_file, process web content viaprocess_web_url, and organize them into collections usingadd_file_to_collection. - Chat Orchestration — Create and manage backend-controlled chats with
create_new_chator use OpenAI/Anthropic compatible endpoints likechat_completionsandsend_message. - Native Ollama Support — Directly interact with the Ollama API using
ollama_generate,ollama_tags, andollama_embedfor local inference tasks. - File Processing — Monitor the status of your document ingestion with
get_file_statusto ensure your RAG context is ready.
How it works
- Subscribe to this server
- Enter your Open WebUI Base URL and API Key
- Start managing your LLM infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- AI Engineers — automate the testing of different models and RAG configurations without leaving the terminal or IDE.
- Knowledge Managers — quickly ingest documentation and web URLs into Open WebUI collections via simple commands.
- DevOps Teams — monitor local Ollama instances and manage model availability across the organization.
Built-in capabilities (12)
Add a file to a knowledge collection
Run outlet filters for completed chat
OpenAI-compatible chat completion
Must generate UUIDs for message IDs. Create a new chat (Backend-Controlled Flow)
Check file processing status
Retrieve all models
Ollama API Embeddings
Ollama API Generate Completion
List Ollama models
Process a web URL into a collection
Anthropic-compatible message generation
Content is extracted and stored in the vector DB. Provide file content as base64. Upload a file for RAG
Why CrewAI?
When paired with CrewAI, Open WebUI becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Open WebUI 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
Open WebUI in CrewAI
Open WebUI and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Open WebUI 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 Open WebUI in CrewAI
The Open WebUI 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 12 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
Open WebUI for CrewAI
Every tool call from CrewAI to the Open WebUI 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 check if a model is available in my Open WebUI instance?
You can use the list_models tool. It will return a complete list of all configured models, including those from Ollama, OpenAI, and internal Open WebUI functions.
Can I add a website to my RAG collection using just a URL?
Yes! Use the process_web_url tool. Provide the URL and the target collection name, and the server will scrape and index the content for you.
How do I know when my uploaded file is ready for querying?
After using upload_file, you can check the ingestion progress by calling get_file_status with the returned File ID. It will tell you if the status is 'completed' or 'pending'.
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 →
SMPTE Timecode Calculator
3 toolsStop LLMs from melting down over base-60 math. Add, subtract, and convert video SMPTE timecodes natively.

Clearout.io
8 toolsVerify email addresses and deliverability via Clearout — track validation jobs, monitor credit balance, and audit list health directly from any AI agent.

Jibble
10 toolsTrack time, attendance, and projects via Jibble API.

Strava Training
12 toolsAnalyze Strava activities, segments, streams (HR, power, GPS), zones, laps, and athlete stats.
