MCP Connector for Open WebUI

Created By
ivanusera year ago
Connect Open WebUI to MCP (Model Context Protocol) servers
Overview

What is MCP Connector for Open WebUI?

MCP Connector for Open WebUI is a tool that connects Open WebUI to MCP (Model Context Protocol) servers, enabling users to utilize MCP-compatible AI models directly within the Open WebUI environment.

How to use MCP Connector?

To use the MCP Connector, install it via GitHub or through the Open WebUI interface, configure your MCP servers in the settings, and enable the function to access the models in the dropdown menu.

Key features of MCP Connector?

  • Connect to multiple MCP servers simultaneously
  • Support for API key authentication
  • Automatic model discovery from MCP servers
  • Support for streaming responses
  • Robust error handling and timeout management
  • Debug mode for troubleshooting

Use cases of MCP Connector?

  1. Integrating various AI models into Open WebUI for enhanced functionality.
  2. Facilitating seamless communication between Open WebUI and multiple AI model servers.
  3. Enabling developers to test and deploy AI models efficiently within a user-friendly interface.

FAQ from MCP Connector?

  • What is MCP?

MCP (Model Context Protocol) is a standardized protocol for AI model interactions, similar to the OpenAI API specification.

  • How do I install the MCP Connector?

You can install it from GitHub using pip or directly through the Open WebUI interface.

  • What should I do if I encounter connection issues?

Check your server URL, network connectivity, and consider increasing the connection timeout.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ivanuser
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago