Higress Information Retrieval and Augmentation Service

Synopsis

An implementation of the Model Context Protocol (MCP) server designed to furnish AI models with external search intelligence via the Higress framework's ai-search functionality, coupled with internal repository access.

Demonstration

Cline Interface

https://github.com/user-attachments/assets/60a06d99-a46c-40fc-b156-793e395542bb

Claude Desktop Interface

https://github.com/user-attachments/assets/5c9e639f-c21c-4738-ad71-1a88cc0bcb46

Capabilities

• General Web Indexing: Utilizing major engines like Google, Bing, and Quark for broad informational retrieval.
• Scholarly Content Access: Integration with Arxiv for retrieving peer-reviewed scientific publications and research material.
• Proprietary Data Synthesis: Capability to query and incorporate data from internal, private knowledge assets.

Prerequisites for Deployment

• Installation utility uv for dependency management.
• Correct configuration of the underlying Higress gateway with the ai-search extension and the ai-proxy plugin.

Setup Instructions

The operational parameters for this server are managed via environment variables:

• HIGRESS_URL(optional): Specifies the endpoint for the Higress gateway service (defaults to http://localhost:8080/v1/chat/completions).
• MODEL(mandatory): The identifier of the specific Large Language Model (LLM) employed for response synthesis.
• INTERNAL_KNOWLEDGE_BASES(optional): Textual descriptions detailing the available internal data sources.

Method A: Utilizing uvx for Installation

This approach automates package acquisition directly from PyPI, negating the need for local repository cloning.

{ "mcpServers": { "higress-web-search-extension-service": { "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" } } } }

Method B: Using uv with Local Source Code

When using the 'uv' runner, the source code directory must be present locally and referenced explicitly.

{ "mcpServers": { "higress-web-search-extension-service": { "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" } } } }

Licensing

This software is distributed under the terms of the MIT License; refer to the LICENSE file for full particulars.

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea