Context7
Up-to-date docs for AI agents
Descripción del creador (original en inglés)
Self-hosted MCP gateway and LLM proxy: OAuth 2.1, model aliases, Grok subscription as an API.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
PUBLIC_URL, OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRETLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"skgate": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PUBLIC_URL",
"-e",
"OIDC_ISSUER",
"-e",
"OIDC_CLIENT_ID",
"-e",
"OIDC_CLIENT_SECRET",
"ghcr.io/helv-io/skgate:0.28.0"
],
"env": {
"PUBLIC_URL": "your-value",
"OIDC_ISSUER": "your-value",
"OIDC_CLIENT_ID": "your-value",
"OIDC_CLIENT_SECRET": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add skgate --env PUBLIC_URL=your-value --env OIDC_ISSUER=your-value --env OIDC_CLIENT_ID=your-value --env OIDC_CLIENT_SECRET=your-value -- docker run -i --rm -e PUBLIC_URL -e OIDC_ISSUER -e OIDC_CLIENT_ID -e OIDC_CLIENT_SECRET ghcr.io/helv-io/skgate:0.28.0Completa los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"skgate": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PUBLIC_URL",
"-e",
"OIDC_ISSUER",
"-e",
"OIDC_CLIENT_ID",
"-e",
"OIDC_CLIENT_SECRET",
"ghcr.io/helv-io/skgate:0.28.0"
],
"env": {
"PUBLIC_URL": "your-value",
"OIDC_ISSUER": "your-value",
"OIDC_CLIENT_ID": "your-value",
"OIDC_CLIENT_SECRET": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"skgate": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PUBLIC_URL",
"-e",
"OIDC_ISSUER",
"-e",
"OIDC_CLIENT_ID",
"-e",
"OIDC_CLIENT_SECRET",
"ghcr.io/helv-io/skgate:0.28.0"
],
"env": {
"PUBLIC_URL": "your-value",
"OIDC_ISSUER": "your-value",
"OIDC_CLIENT_ID": "your-value",
"OIDC_CLIENT_SECRET": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub helv-io, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: PUBLIC_URL, OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.28.0) llegó al registro hace 20 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Docker en tu computadora.
En la misma categoría: Context7, Codebase Memory, Exa
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
skgate
Self-hosted MCP gateway and LLM proxy. Serve any MCP server or REST API behind OAuth 2.1 from one address, and proxy your LLM providers (OpenAI, Anthropic, Gemini, Grok, Ollama and more) through one OpenAI-compatible API with model aliases and virtual keys. Your Grok subscription works too, no API key needed.
Any MCP server. skgate can run them for you, so you do not need one container per server.
skgate /ɛsˈkɑːɡeɪt/ (ess-KAH-gate)
"sk" is how a lot of SI API keys start, and "gate" is for gateway. Not a great name, but it's ours.
The plane in the logo is an inside joke. The public wouldn't understand it, and I'm not about to explain it. Sorry.
Is it good?
Yes
You need an OIDC provider with a confidential client for skgate. Admin login is OIDC only. Trying it on one machine? docs/quickstart.md runs skgate with a bundled provider and no accounts.
# docker-compose.yml
services: skgate: container_name: skgate image: ghcr.io/helv-io/skgate:latest restart: always ports:
docker compose up -dhttps://skgate.example.com/admin and sign in through your OIDC provider.https://skgate.example.com/mcp or the site root for every included upstream, or at https://skgate.example.com/mcp/ for one upstream. Sign in when it asks.Image tags:
latest: proxy + managed MCP servers. Bundles Node.js (npx), pnpm, Bun (bunx), Deno, Python (uv, uvx), Go, .NET and git.slim: proxy onlyTo upgrade, back up ./data, then docker compose pull && docker compose up -d.
skgate is also an OpenAI-compatible API in front of your SI providers. Point your apps at one address; switch the provider behind them without changing the apps. User-defined model aliases give your apps a stable model name of your choosing.
Grok can use subscription sign-in with no API key. Other providers use that provider's API key (OpenAI, Anthropic, Gemini, Mistral, DeepSeek, Groq, OpenRouter, Ollama, LM Studio, and any OpenAI-compatible endpoint).
sk-... key; it is shown once.https://skgate.example.com/v1, API key sk-... (see Examples)./v1, /api, /api/v1, and the bare host. Use whichever form your client expects.curl: models and a chat completion
export SKGATE=https://skgate.example.com KEY=sk-...
curl -s $SKGATE/v1/models -H "Authorization: Bearer $KEY" curl -s $SKGATE/v1/chat/completions -H "Authorization: Bearer $KEY" \ -H 'Content-Type: application/json' \ -d '{"model":" ","messages":[{"role":"user","content":"Say hi"}]}'
OpenAI client
export OPENAI_BASE_URL=https://skgate.example.com/v1 OPENAI_API_KEY=sk-...
from openai import OpenAI
client = OpenAI() # reads the two variables above r = client.chat.completions.create(model=" ", messages=[{"role": "user", "content": "Say hi"}]) print(r.choices[0].message.content)
Model aliases: user-defined names for models
Aliases are user-defined: skgate ships with none. Pick any name and point it at a model. This example uses grok-latest, but the name is up to you.
Change the target in this one place and every app using that name switches at once, with no client config changes.
Grok > Aliases: New alias grok-latest, Target model grok-4.7, Add alias.
client sends {"model": "grok-latest", ...}
skgate sends {"model": "grok-4.7", ...}
Aliases are listed first in /v1/models.
Add an MCP server with Suggest configuration
Needs the latest image and an MCP helper model from any ready provider. The first time, Pick MCP helper model next to the button opens the model picker right on the page.
mcp upstreams > Add upstream > Type managed process:
| Source | Runs as |
|---|---|
@modelcontextprotocol/server-everything | npm package, npx |
pypi:mcp-server-time | PyPI package, uvx |
https://github.com/example-org/notes-mcp | git repo: clone, install, run (private: Suggest asks for a token) |
package.json, pyproject.toml, server.json).The MCP helper model proposes the command, args, install step, and env names (secret or not, required or optional). The Manual configuration fields fill in, with a confidence and any warnings.
Nothing is saved yet. Set the variables the server needs.
https://skgate.example.com/mcp/ .If the button is greyed out, hover it. Use Pick MCP helper model beside it, or add a provider on status first.
MCP client: one upstream or all of them
| URL | Serves |
|---|---|
https://skgate.example.com/mcp/ | One upstream |
https://skgate.example.com/mcp | Every upstream marked In /mcp |
https://skgate.example.com/ (MCP clients) | Same aggregate as /mcp when Accept/Content-Type look like MCP; browsers still go to /admin |
Hosted connectors use OAuth (leave client ID and secret empty). Scripts and CLIs send a key:
{"mcpServers": {"skgate": {"type": "http", "url": "https://skgate.example.com/mcp/<alias>",
"headers": {"Authorization": "Bearer sk-..."}}}}
On-demand MCP servers: no RAM while idle
On a RAM-constrained homelab, idle MCP servers should cost nothing.
Managed servers (npx, pnpm dlx, bunx, deno, uvx, git) are child processes of skgate.
By default (Lifecycle on-demand) one starts on its first request and stops after 10 minutes without requests; the next request starts it again.
before 3 MCP servers = 3 containers, always running
after 1 skgate container; 0 server processes while idle, 1 per server in use
stopped --request--> starting --> running --10 min idle--> stopped
always-on starts the server at boot instead.idleTimeoutSeconds in import JSON (default 600; not in the form):{"mcpServers": {"time": {"command": "uvx", "args": ["mcp-server-time"], "skgate": {"idleTimeoutSeconds": 120}}}}
/mcp includes remote, OpenAPI and always-on upstreams marked In /mcp. On-demand servers are left out, so /mcp never starts them. Point a client at /mcp/ to use one.Managed MCP server: npx (stdio)
mcp upstreams > import JSON > paste > Import. Needs the latest image.
{"mcpServers": {"everything": {"command": "npx", "args": ["-y", "@modelcontextprotocol/server-everything"]}}}
Served at https://skgate.example.com/mcp/everything. The same package runs with any bundled runner:
| Runner | command | args |
|---|---|---|
| npm | npx | ["-y", " "] |
| pnpm | pnpm | ["dlx", " "] |
| Bun | bunx | [" "] |
| Deno | deno | ["run", "-A", "npm: "] |
| Python | uvx | [" "] |
Managed MCP server: git repository
mcp upstreams > import JSON > paste > Import. skgate clones the repo, runs install, then the command.
{"mcpServers": {"notes": {"command": "node", "args": ["server.js"],
"skgate": {"gitUrl": "https://github.com/example-org/notes-mcp.git", "gitRef": "main", "install": "npm ci"}}}}
Remote MCP server
mcp upstreams > Add upstream > Type remote server, or import:
{"mcpServers": {"docs": {"type": "http", "url": "https://mcp.example.com/mcp",
"headers": {"Authorization": "Bearer ..."}}}}
| Feature | What it does |
|---|---|
| Grok sign-in | Device code or browser paste-back; tokens refresh |
| Other providers | OpenAI, Anthropic, Gemini and more by API key (docs) |
| Model aliases | User-defined model names; change the target once |
| API | /v1, /api/v1, /api, no prefix; SSE (docs) |
| Virtual keys | Hashed; tokens in/out per key (docs) |
| MCP | Remote, stdio and git servers behind OAuth 2.1 (docs) |
| Live tool updates | Connected clients hear when an upstream's tools change after an update, a reinstall or a tool switched on or off, and pick up the new tools without reconnecting |
| REST APIs as tools | Give an OpenAPI description, pick the operations (or let Suggest names and selection name them and pick a core set), and MCP clients get them as tools (docs) |
Clients tested by the author against a live skgate. Status is what happened, not a promise.
| Client | Status | Notes |
|---|---|---|
| ChatGPT | OK | |
| Claude | OK | |
| Grok | OK | |
| Hermes | OK | |
| Open WebUI | OK | Use OAuth 2.1; register and authorize the client. |
| Gemini | Warning | Connects, but never calls tools. |
| Home Assistant | Warning | Needs a manual OAuth client ID and secret. Only one MCP upstream can be used. |
| Cline | Untested | |
| Continue | Untested | |
| Cursor | OK | |
| Goose | Untested | |
| LibreChat | Untested | |
| VS Code | Untested | |
| Windsurf | Untested | |
| Zed | Untested |
skgate stdio starts a small read-only MCP server on stdin and stdout. It exists so MCP directories and scanners, which start a server and ask what it offers, can look at skgate. It is not for real use: to run skgate, use the Docker image above.
It needs no settings, opens no port, reads no database and uses no network. It has three tools: about, list_features and config_help. They describe skgate and nothing else. More in docs/mcp.md.
A rough guide from each project's docs as of 2026-10-13. Check them for current features.
| | skgate | [LiteLLM](https://github.com/Berr
Solo se muestra el principio; lee el resto en el repo