Skip to main content
Version: v1.6.47-dev1 🚧

h2oGPTe MCP Server

Overview​

The official h2oGPTe MCP server provides access to Enterprise h2oGPTe's REST API through the MCP protocol. This is a separate package that you install outside of Enterprise h2oGPTe. It is primarily designed for external clients that want to access Enterprise h2oGPTe functionality through the MCP protocol.

For more information, visit the h2oGPTe MCP Server GitHub repository.

When to Use​

This MCP server is useful for:

  • Enabling external MCP clients (such as Cursor or Claude Desktop) to access Enterprise h2oGPTe functionality through the MCP protocol
  • Integrating Enterprise h2oGPTe capabilities into third-party applications that support MCP
  • Building custom applications that require Enterprise h2oGPTe functionality through a standardized MCP interface
  • Exposing Enterprise h2oGPTe REST API endpoints as MCP tools for use in external workflows

Requirements​

Before configuring this MCP server, ensure you have:

  • Enterprise h2oGPTe instance with API access
  • Enterprise h2oGPTe access key (format: sk-...)
  • Python environment with pip installed (for PyPI installation)
  • Or Git and Make (for source installation)

Key Features​

The h2oGPTe MCP server provides the following capabilities:

  • Access to Enterprise h2oGPTe REST API endpoints through MCP protocol
  • Configurable endpoint exposure (all endpoints, selected sets, or custom configurations)
  • Support for both tools and resources based on endpoint types
  • Flexible configuration for different use cases and security requirements
  • Integration with external MCP clients and third-party applications

Installation​

1. From PyPI:​

pip install h2ogpte-mcp-server

2. From GitHub source:​

git clone https://github.com/h2oai/h2ogpte-mcp-server.git
cd h2ogpte-mcp-server
git checkout $(git describe --tags)
make setup
make build
make install

Configuration​

Add the following configuration in Agents > Tools > New Tool > Remote MCP Tools:

{
  "h2ogpte-mcp-server": {
    "command": "h2ogpte-mcp-server",
    "env": {
      "H2OGPTE_API_KEY": "os.environ/H2OGPTE_API_KEY",
      "H2OGPTE_SERVER_URL": "os.environ/H2OGPTE_SERVER_URL",
      "H2OGPTE_ALL_ENDPOINTS_AS_TOOLS": "true",
      "H2OGPTE_ENDPOINT_SET": "basic"
    }
  }
}

Authentication​

Set up the following environment variables in Agents > Authentication:

Required:

  • H2OGPTE_API_KEY: Your Enterprise h2oGPTe access key (format: sk-...)
  • H2OGPTE_SERVER_URL: Enterprise h2oGPTe server URL (default: https://h2ogpte.genai.h2o.ai)

Optional:

  • H2OGPTE_ALL_ENDPOINTS_AS_TOOLS: Set to true to expose all endpoints as tools, or false to expose GET endpoints as resources (default: true)
  • H2OGPTE_ENDPOINT_SET: Endpoint selection (default: all_without_async_ingest)
    • all: All REST API endpoints
    • all_without_async_ingest: All endpoints except async ingestion
    • basic: Minimal set for core functionality
    • custom: User-defined endpoint set (requires H2OGPTE_CUSTOM_ENDPOINT_SET_FILE)
  • H2OGPTE_CUSTOM_ENDPOINT_SET_FILE: Path to text file with one endpoint per line
  • H2OGPTE_CUSTOM_ENDPOINT_SPEC_FILE: Path to custom OpenAPI spec file (for debugging)

Notes​

  • This MCP server uses STDIO transport protocol.
  • This is a remote MCP server that runs as a separate process outside of Enterprise h2oGPTe.
  • Primarily designed for external MCP clients, but can also be configured within Enterprise h2oGPTe for advanced use cases.
  • The server must be installed and accessible in the environment where Enterprise h2oGPTe is running.
Feedback