4,000+ servers built on vurb.ts
Vinkius

Open WebUI MCP Server for CrewAIGive CrewAI instant access to 12 tools to Add File To Collection, Chat Completed, Chat Completions, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Open WebUI through Vinkius, pass the Edge URL in the `mcps` parameter and every Open WebUI tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Open WebUI MCP Server for CrewAI is a standout in the Loved By Devs category — giving your AI agent 12 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Open WebUI Specialist",
    goal="Help users interact with Open WebUI effectively",
    backstory=(
        "You are an expert at leveraging Open WebUI tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Open WebUI "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Open WebUI
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

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.

What you can do

  • Model Management — Use list_models to fetch all available models including Ollama, OpenAI, and Open WebUI Functions.
  • RAG & Knowledge Base — Upload files with upload_file, process web content via process_web_url, and organize them into collections using add_file_to_collection.
  • Chat Orchestration — Create and manage backend-controlled chats with create_new_chat or use OpenAI/Anthropic compatible endpoints like chat_completions and send_message.
  • Native Ollama Support — Directly interact with the Ollama API using ollama_generate, ollama_tags, and ollama_embed for local inference tasks.
  • File Processing — Monitor the status of your document ingestion with get_file_status to ensure your RAG context is ready.

The Open WebUI MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 12 Open WebUI tools available for CrewAI

When CrewAI connects to Open WebUI through Vinkius, your AI agent gets direct access to every tool listed below — spanning llm-management, rag, model-inference, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add file to collection on Open WebUI

Add a file to a knowledge collection

chat

Chat completed on Open WebUI

Run outlet filters for completed chat

chat

Chat completions on Open WebUI

OpenAI-compatible chat completion

create

Create new chat on Open WebUI

Must generate UUIDs for message IDs. Create a new chat (Backend-Controlled Flow)

get

Get file status on Open WebUI

Check file processing status

list

List models on Open WebUI

Retrieve all models

ollama

Ollama embed on Open WebUI

Ollama API Embeddings

ollama

Ollama generate on Open WebUI

Ollama API Generate Completion

ollama

Ollama tags on Open WebUI

List Ollama models

process

Process web url on Open WebUI

Process a web URL into a collection

send

Send message on Open WebUI

Anthropic-compatible message generation

upload

Upload file on Open WebUI

Content is extracted and stored in the vector DB. Provide file content as base64. Upload a file for RAG

Connect Open WebUI to CrewAI via MCP

Follow these steps to wire Open WebUI into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Open WebUI

Why Use CrewAI with the Open WebUI MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Open WebUI through the Model Context Protocol.

01

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

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

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

04

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 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Open WebUI MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Open WebUI for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Open WebUI, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Open WebUI tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Open WebUI against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Open WebUI in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Open WebUI immediately.

01

"List all models available in my Open WebUI instance."

02

"Process the URL 'https://docs.openwebui.com/' into my 'Documentation' collection."

03

"Generate a response using the 'llama3' model for the prompt 'Explain quantum computing'."

Troubleshooting Open WebUI MCP Server with CrewAI

Common issues when connecting Open WebUI to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

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.

Open WebUI + CrewAI FAQ

Common questions about integrating Open WebUI MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →