Higress AI-Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODEL | Yes | LLM model to use for generating responses | |
| HIGRESS_URL | No | URL for the Higress service | http://localhost:8080/v1/chat/completions |
| INTERNAL_KNOWLEDGE_BASES | No | Description of internal knowledge bases |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ai_searchB | Enhance AI model responses with real-time search results from search engines. This tool sends a query to Higress, which integrates with various search engines to provide up-to-date information: š Internet Search: Google, Bing, Quark - for general web information š Academic Search: Arxiv - for scientific papers and research šØāš» Internal Knowledge Search: Company documentation, product manuals, FAQ database, and technical specifications stored in our internal systems |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined as a unified search interface.
Only one tool exists, so naming consistency is trivially met. The name 'ai_search' is descriptive and follows a reasonable pattern.
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.
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.