Higress AI-Search MCP Server
by cr7258
README.md
[](https://mseep.ai/app/cr7258-higress-ai-search-mcp-server)
# Higress AI-Search MCP Server
## Overview
A Model Context Protocol (MCP) server that provides an AI search tool to enhance AI model responses with real-time search results from various search engines through [Higress](https://higress.cn/) [ai-search](https://github.com/alibaba/higress/blob/main/plugins/wasm-go/extensions/ai-search/README.md) feature.
<a href="https://glama.ai/mcp/servers/gk0xde4wbp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/gk0xde4wbp/badge" alt="Higress AI-Search Server MCP server" />
</a>
## Demo
### Cline
https://github.com/user-attachments/assets/60a06d99-a46c-40fc-b156-793e395542bb
### Claude Desktop
https://github.com/user-attachments/assets/5c9e639f-c21c-4738-ad71-1a88cc0bcb46
## Features
- **Internet Search**: Google, Bing, Quark - for general web information
- **Academic Search**: Arxiv - for scientific papers and research
- **Internal Knowledge Search**
## Prerequisites
- [uv](https://github.com/astral-sh/uv) for package installation.
- Config Higress with [ai-search](https://github.com/alibaba/higress/blob/main/plugins/wasm-go/extensions/ai-search/README.md) plugin and [ai-proxy](https://github.com/alibaba/higress/blob/main/plugins/wasm-go/extensions/ai-proxy/README.md) plugin.
## Configuration
The server can be configured using environment variables:
- `HIGRESS_URL`(optional): URL for the Higress service (default: `http://localhost:8080/v1/chat/completions`).
- `MODEL`(required): LLM model to use for generating responses.
- `INTERNAL_KNOWLEDGE_BASES`(optional): Description of internal knowledge bases.
### Option 1: Using uvx
Using uvx will automatically install the package from PyPI, no need to clone the repository locally.
```bash
{
"mcpServers": {
"higress-ai-search-mcp-server": {
"command": "uvx",
"args": [
"higress-ai-search-mcp-server"
],
"env": {
"HIGRESS_URL": "http://localhost:8080/v1/chat/completions",
"MODEL": "qwen-turbo",
"INTERNAL_KNOWLEDGE_BASES": "Employee handbook, company policies, internal process documents"
}
}
}
}
```
### Option 2: Using uv with local development
Using uv requires cloning the repository locally and specifying the path to the source code.
```bash
{
"mcpServers": {
"higress-ai-search-mcp-server": {
"command": "uv",
"args": [
"--directory",
"path/to/src/higress-ai-search-mcp-server",
"run",
"higress-ai-search-mcp-server"
],
"env": {
"HIGRESS_URL": "http://localhost:8080/v1/chat/completions",
"MODEL": "qwen-turbo",
"INTERNAL_KNOWLEDGE_BASES": "Employee handbook, company policies, internal process documents"
}
}
}
}
```
## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.TDQS
A3.7/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined as a unified search interface.
Naming Consistency5/5
Only one tool exists, so naming consistency is trivially met. The name 'ai_search' is descriptive and follows a reasonable pattern.
Tool Count4/5
A single search tool is slightly under the typical 3-15 range, but it consolidates multiple search capabilities (internet, academic, internal) into one unified interface, which can be reasonable for a focused server.
Completeness4/5
The tool covers key search domains (internet, academic, internal knowledge), but lacks explicit support for advanced features like filters, pagination, or custom sources, which may be needed for complex queries.
Maintenance
ActivityInactive
ResponsivenessNo issues