Higress Documentation

repository·main·Indexed 27 days ago

https://github.com/higress-group/higress

A CNCF sandbox cloud-native gateway project built on Envoy and Istio, designed for high-performance traffic management and extensibility via Wasm plugins. Includes documentation for installation via Helm charts, configuration of gateway metrics, proxy settings, and Redis. Also features the hgctl CLI for creating, deploying, and managing AI Agents and Model Context Protocol (MCP) servers, with support for local deployment via AgentScope and cloud deployment via Alibaba Cloud Function Compute (AgentRun).

Tokens
284.6K
Snippets
504
Records
1.4K
Agent score
93%

What's inside Higress

  1. Overview of MCP Server Golang Filter Plugin

    main

    The MCP Server is an Envoy-based Golang Filter plugin for Higress that provides a unified Model Context Protocol (MCP) service interface. It enables integration with various backend services, including:

    • Database Services: Access and management via GORM support.
    • Configuration Centers: Integration with Nacos.
    • Custom Implementations: Extensible architecture for integrating other services.

    Requirement: You must use Higress version 2.1.0 or higher.

  2. Overview of Higress Capabilities

    main

    Higress is a cloud-native API gateway based on Istio and Envoy. It supports Wasm plugin development using Go, Rust, or JS and provides dozens of ready-to-use generic plugins and a management console.

    Key Use Cases:

    • AI Gateway: Connects to major LLM providers with unified protocols. Supports AI observability, multi-model load balancing/fallback, token flow control, and AI caching. It also supports self-built models like DeepSeek via vllm/ollama.
    • MCP Server Hosting: Hosts Model Context Protocol (MCP) servers via its plugin mechanism, allowing AI Agents to call tools and services with unified authentication, authorization, rate limiting, and observability.
    • Kubernetes Ingress Gateway: Acts as an Ingress entry point for K8s clusters. Supports the Gateway API standard and provides a smooth migration path from Nginx Ingress with significantly lower resource consumption and faster routing updates.
    • Microservices Gateway: Discovers services from registries like Nacos, ZooKeeper, Consul, and Eureka. Deeply integrated with Dubbo, Nacos, and Sentinel.
    • Security Gateway: Provides WAF capabilities and supports various authentication strategies including key-auth, hmac-auth, jwt-auth, basic-auth, and oidc.
  3. Overview of GitHub MCP Server

    main

    The GitHub MCP Server is an implementation of the Model Context Protocol (MCP) for the GitHub API. It enables AI agents to perform various GitHub operations including file manipulation, repository management, and advanced searching.

    Key features include:

    • Automatic Branch Creation: Automatically creates branches when creating/updating files or pushing changes if the branch does not exist.
    • Comprehensive Error Handling: Provides clear error messages for common issues.
    • Git History Preservation: Operations preserve full Git history and avoid force-pushing.
    • Batch Operations: Supports both single-file and batch file operations.
    • Advanced Search: Supports searching for code, issues, pull requests (PRs), and users.
  4. Overview of Cluster Rate Limiting Based on Key

    main

    The cluster-key-rate-limit plugin provides cluster-level rate limiting using Redis. This ensures globally consistent rate limiting across multiple Higress Gateway instances.

    It supports three modes:

    1. Rule-Level Global Rate Limiting: Applies a unified threshold to custom rule groups using a shared rule_name and global_threshold.
    2. Key-Level Dynamic Rate Limiting: Limits requests based on dynamic keys extracted from the request (e.g., URL parameters, headers, client IPs, consumer names, or cookies).
    3. Hybrid Rate Limiting: Combines global_threshold (as a global fallback) and rule_items (per-dimension). In this mode, all matched rules are evaluated, and if any rule is triggered, the request is rejected.
  5. Overview of Sector Market Overview MCP Server

    main
    The mcp-plate-quote tool integrates real-time market data for industry and concept sectors. It provides key indicators such as index levels, price change percentages, trading volumes, total market capitalization, sector rankings, and leading stock information. It is designed for intelligent investment research and tracking market trends through sector dynamics and constituent stock performance.
  6. Overview of Higress RAG MCP Server Tools

    main

    The Higress RAG MCP Server provides tools for knowledge management and retrieval. The availability of tools depends on your configuration:

    • Basic Functions (Knowledge Management & Search): Requires embedding and vectordb configuration.
    • Advanced Functions (Chat/RAG): Requires additional llm configuration.
    Tool NameDescriptionDependenciesRequired/Optional
    create-chunks-from-textSplits text into chunks and stores them in a vector database for knowledge base constructionembedding, vectordbRequired
    list-chunksLists stored knowledge chunks for managementvectordbRequired
    delete-chunkDeletes a specific knowledge chunkvectordbRequired
    searchPerforms semantic similarity search in the knowledge baseembedding, vectordbRequired
    chatAnswers user questions using RAG (Retrieval-Augmented Generation)embedding, vectordb, llmOptional
  7. Overview of Tool Search MCP Server

    main

    The Tool Search MCP Server is an implementation based on the Higress Golang Filter that provides semantic tool searching capabilities. It uses vector semantic search via a Milvus vector database and OpenAI-compatible Embedding APIs.

    Key Features:

    • Vector Semantic Search: Converts user queries into vectors using an Embedding API and performs similarity retrieval in Milvus.
    • Tool Metadata Support: Reads full tool definitions (JSON format) from the database and dynamically constructs tool names.
    • Full Tool List: Supports retrieving all available tools in the database.
    • Configurable Embedding Models: Supports custom models, dimensions, and API endpoints (e.g., DashScope).
    • Milvus Integration: Connects to Milvus via standard gRPC interfaces.