Higress OPS MCP Server

What is Higress OPS MCP Server?

Higress OPS MCP Server is a Model Context Protocol (MCP) server implementation for comprehensive configuration and management of Higress, the cloud-native API gateway. It also includes an MCP client built on LangGraph and LangChain MCP Adapters, enabling AI-agent-based interaction with Higress operations. This server is designed for developers and operators who want to manage Higress programmatically or via natural language interfaces.

How to use Higress OPS MCP Server?

Copy the .env.example file to .env and fill in the required environment variables. Then run uv run client.py from the command line to start both the MCP client and the MCP server in stdio mode. The server automatically registers all tools, and write operations listed in SENSITIVE_TOOLS require human confirmation before execution.

Key features of Higress OPS MCP Server

• MCP server for configuring and managing Higress gateways
• Client with LangGraph-based agent flow architecture
• Extensible tool registration via custom tool classes
• Sensitive write operations require human confirmation
• Built on FastMCP and Higress Console API
• Supports adding routes, service sources, request block plugins, and more

Use cases of Higress OPS MCP Server

• Automate gateway route creation and updates via AI agents
• Manage upstream service sources with natural language commands
• Configure request blocking plugins without manual console access
• Integrate Higress operations into larger LangGraph workflows

FAQ from Higress OPS MCP Server

What runtime and dependencies are required?

Python, uv as the package manager, and the libraries listed in the project (FastMCP, LangGraph, LangChain MCP Adapters, and a custom Higress client) are required.

How do I add a new tool to the server?

Create a tool class with a register_tools method, add methods to utils/higress_client.py if needed, then register the class in the tool_classes list in server.py. Optionally add the tool name to SENSITIVE_TOOLS if it requires human confirmation.

How does data storage and authentication work?

The server communicates with the Higress Console API. Authentication credentials are provided via environment variables (see .env.example). No data is stored locally beyond configuration; all operations affect the connected Higress instance.

What transport protocol does the server use?

The server and client communicate using the stdio transport protocol, with the MCP server process started by the client program.

Are there any known limitations?

The README does not mention specific limits. Tools that modify state (listed in SENSITIVE_TOOLS) require explicit human approval, which may impact fully autonomous workflows.