Skip to content

About

Enterprise model and auth providers for Obot MCP Gateway

Resources

Stars

2 stars

Watchers

0 watching

Forks

Latest commit

 

History

33 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Enterprise Providers

This repo contains closed source, enterprise-only providers for Obot.

make build produces static Go binaries with absolute build paths and debug symbols removed. Set CGO_ENABLED=1 if a local build requires cgo.

make docker-build packages the provider registries, version metadata, and UPX-compressed binaries in a scratch image. Obot consumes the existing /obot-providers directory with COPY --from; the image has no shell or default command. A CA certificate bundle and writable /tmp are included for running a provider directly with an explicit --entrypoint.

Compression minimizes executable size at the cost of build time and startup decompression. To retain ordinary ELF binaries for debugging, binary inspection, or environments that restrict executable unpacking, build with:

docker build --build-arg COMPRESS_BINARIES=false -t enterprise-providers:uncompressed .

The Docker build cross-compiles for its target platform, including linux/amd64 and linux/arm64, without running target binaries during the build.

Provider display text

Provider YAML references backend catalog messages in name, description, and configuration parameters' friendlyName and description:

name: "${google_auth_provider_name}"
description: "${google_auth_provider_description}"

Messages live in Obot's pkg/i18n/messages/auth-providers/{locale}.json or pkg/i18n/messages/model-providers/{locale}.json. Use the YAML filename with hyphens replaced by underscores as the key prefix. Parameter keys append the lowercase configuration suffix and friendly_name or description.

Obot resolves references using Accept-Language, falling back to English for missing or empty translations. Unknown keys retain their ${key} reference. Literal text remains valid. Ship catalog additions in Obot together with updated provider registry images; catalog changes require rebuilding Obot.

About

Enterprise model and auth providers for Obot MCP Gateway

Resources

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages