Skip to content
MagicFrog

Ecosystem

Models, tools, and distribution grow on your infrastructure

Your keys for models, the official registry for tools, your own distribution for artifacts.

Three provider channels

MagicFrog has exactly three model channels, and every one is bring-your-own-key: CodeBuddy, CodeBuddy, and custom CodeBuddy-compatible endpoints. There is no vendor catalog to browse and no subscription login path.

01

CodeBuddy

Run /connect and choose CodeBuddy, paste your API key, then /model to pick a model.

02

CodeBuddy

Run /connect and choose CodeBuddy, paste your API key; the official endpoint accepts both chat completions and Responses shapes.

03

Custom CodeBuddy-compatible endpoint

Most providers expose an CodeBuddy-compatible API: store the key, then declare the provider in magicfrog.json.

Providers doc →
The official MCP registry

In-product: the official registry plus your custom sources.

Distribution surface

  • Client and server artifacts ship from the dedicated magicfrog-downloads bucket with direct downloads — no proxy in between.
  • Downloads are verified by SHA-256 digest plus byte size.
  • Container images live at ghcr.io/gsc-org/magicfrog; image publishing will be announced separately.
Self-hosting guide →

Start with one command

Bring keys, pick tools, own the distribution.