openwebui-tool-server

Created By
Oaklighta year ago
Web Search OpenAPI/MCP server for Open-WebUI, Cherry-Studio etc, via Google and SearXNG
Overview

what is Web Search OpenAPI/MCP?

Web Search OpenAPI/MCP is a server designed to facilitate web searches through Open-WebUI and Cherry-Studio, utilizing Google and SearXNG for data retrieval.

how to use Web Search OpenAPI/MCP?

To use the server, set it up in a Docker environment and configure it to connect with your desired web search APIs. You can then make API calls to retrieve search results.

key features of Web Search OpenAPI/MCP?

  • Integration with multiple web search engines (Google, SearXNG)
  • OpenAPI compliant for easy integration
  • Supports function calling for advanced search capabilities

use cases of Web Search OpenAPI/MCP?

  1. Building custom search tools for applications.
  2. Enhancing web applications with powerful search functionalities.
  3. Research and data analysis through automated web searches.

FAQ from Web Search OpenAPI/MCP?

  • What is the main purpose of this project?

The project aims to provide a flexible and powerful web search server that can be integrated into various applications.

  • Is it necessary to use Docker?

While Docker is recommended for easy setup, it is not strictly necessary; you can run the server in other environments as well.

  • Can I customize the search parameters?

Yes! The server allows customization of search parameters to tailor results to your needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Oaklight
Star
0
Language
Python
License
-

Recommend Servers

View All
Alloy

2 days ago
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)

8 hours ago
Crevio

a day ago