H2OGPTe MCP Server
H2OGPTe MCP Server is a Model Context Protocol (MCP) server that prifor the H2OGPTe project. The server is just a local proxy forwarding traffic to REST API endpoints of H2OGPTe executed as commnad.
Installation
From Pypi
pip install h2ogpte-mcp-server
From Github
# Clone git repository
git clone https://github.com/h2oai/h2ogpte-mcp-server.git
# Use the latest release version
git checkout $(git describe --tags)
make setup
make build
# The command will install h2ogpte-mcp-server to the current python environment
make install
Usage
Environment Variables
- H2OGPTE_API_KEY - (required) H2OGPTe access key. See documentation on how to get the key.
- H2OGPTE_SERVER_URL - The url of H2OGPTe server. Default value is https://h2ogpte.genai.h2o.ai.
- H2OGPTE_ALL_ENDPOINTS_AS_TOOLS - A boolean flag, specifing whether all REST API endpoints should be represented as MCP tools. If disabled, GET endpoints will be represented as resources. Default value is
true. - H2OGPTE_ENDPOINT_SET - A set of REST API endpoints that will be used for MCP tools or resources. The default value is
all_without_async_ingest. Possible values:all- All REST API endpoints on the H2OGPTe serverall_without_async_ingest- All endpoints without asynchronous ingestion endpoints. These endpoints start and returns a job. E.g.:create_ingest_upload_jobbasic- A mininal set of endpoints for chatting with collections and ingesting new documents.custom- A set of endpoints defined by the user. If chossen, theH2OGPTE_CUSTOM_ENDPOINT_SET_FILEvariable must be set.
- H2OGPTE_CUSTOM_ENDPOINT_SET_FILE - A path to file with the list of REST API endpoints. Each endpoint name must be an a separate line. The name of the endpoint is the
operationIdattribute in REST API spec file (e.g.: https://h2ogpte.genai.h2o.ai/api-spec.yaml) - H2OGPTE_CUSTOM_OPENAPI_SPEC_FILE - A path to OpenAPI spec file in YAML format describing REST API of the H2OGPTe server. If not specified, the file is obtained from the H2OGPTe server itself. This environement variable should be used only for debugging purposes.
Example Configuration
An example MCP server configuration for MCP clients. E.g.: Cursor, Claude Desktop
{
"mcpServers": {
"h2ogpte-mcp-server": {
"command": "h2ogpte-mcp-server",
"env": {
"H2OGPTE_API_KEY": "sk-...",
"H2OGPTE_SERVER_URL": "https://h2ogpte.genai.h2o.ai",
"H2OGPTE_ALL_ENDPOINTS_AS_TOOLS": "true"
}
}
}
}
Metadata
Release files for h2ogpte-mcp-server 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| h2ogpte_mcp_server-0.1.6-py3-none-any.whl | Python 3 | none | any | Details for h2ogpte_mcp_server-0.1.6-py3-none-any.whl |
Release files / h2ogpte_mcp_server-0.1.6-py3-none-any.whl
| Download URL | h2ogpte_mcp_server-0.1.6-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3aef0107042bf0469e755d59dc96c553107e73624fc82a3f03594b0e4ae2208
|
|
BLAKE2b-256 checksum How to use checksums |
5ab81b788e4f21e05f53ad9e878c82c4b31ebae1a9886f83960fd5ee31b60438
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.4
|
Security for h2ogpte-mcp-server 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.