MCP server de GABS
Commit 30 sept 2026Inicia y supervisa procesos de juegos locales, para luego reflejar las herramientas de puente de cada juego en MCP, permitiendo que un agente de IA pueda descubrir y controlar el juego en ejecución.
También conocido como pardeike/GABS
- Stars
- 37
- Herramientas
- 10
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 30 sept 2026
- Licencia
- MIT
¿Qué es GABS MCP?
Inicia y supervisa procesos de juegos locales, para luego reflejar las herramientas de puente de cada juego en MCP, permitiendo que un agente de IA pueda descubrir y controlar el juego en ejecución. Expone 10 herramientas, como games_list, games_show, games_start.
Resumen generado a partir del README del proyecto
Acerca del MCP server de GABS
GABS permite gestionar y controlar procesos de juegos locales mediante un agente de IA. Este MCP server basado en configuración permite a los desarrolladores declarar juegos en un archivo de configuración JSON y supervisar su ciclo de vida. Una vez que un juego se conecta a través de un puente GABP, el servidor refleja esas herramientas específicas del juego en una interfaz MCP estable, lo que permite que un cliente de IA descubra y ejecute comandos específicos del juego directamente.
Los usuarios interactúan con el sistema a través de un MCP server para agentes de IA o una CLI para control manual. La configuración requiere una instalación local del binario de GABS en Windows, macOS o Linux. Para conectarse a un cliente de IA como Claude Desktop, debes añadir el servidor a tu configuración de MCP. El servidor admite varios modos de lanzamiento, incluyendo rutas directas, SteamAppId y EpicAppId, y proporciona herramientas como games_start, games_stop y games_call_tool para gestionar la carga de trabajo.
Qué puedes hacer con él
- 1Gestión automatizada de procesos de juegosUn agente de IA puede iniciar, detener o forzar el cierre de un proceso de juego específico basándose en las peticiones del usuario.
- 2Descubrimiento dinámico de herramientas para juegosUn cliente de IA puede consultar el servidor para encontrar todas las herramientas específicas del juego disponibles una vez que un puente está activo.
- 3Perfiles de lanzamiento de juegos configurablesLos desarrolladores pueden definir contextos de lanzamiento repetibles con argumentos y variables de entorno específicos mediante perfiles.
- 4Control directo del juego mediante IAUn agente puede ejecutar acciones específicas dentro del juego llamando a herramientas reflejadas, como la gestión del inventario.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Herramientas de GABS MCP 10
Detectado desde el READMEgames_listgames_showgames_startgames_stopgames_killgames_statusgames_connectgames_tool_namesgames_tool_detailgames_call_tool
| games_list | — | |
| games_show | — | |
| games_start | — | |
| games_stop | — | |
| games_kill | — | |
| games_status | — | |
| games_connect | — | |
| games_tool_names | — | |
| games_tool_detail | — | |
| games_call_tool | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblepardeike/gabs is public and reachablegithub.com/pardeike/gabs ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-09-30github.com/pardeike/gabs ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubGABS - Game Agent Bridge Server
Compatible with GABP v1.1 on wire major gabp/1.
GABS is a configuration-first MCP server that manages local game processes and mirrors each game's GABP bridge tools into a stable MCP surface. You declare your games once in a config file; GABS starts and supervises those processes, and when a game's GABP bridge connects, GABS mirrors that bridge's tools into MCP. An AI agent then discovers and controls a running game entirely through GABS.
If you are installing GABS from a release archive, start with Quick Start below. For the full copy-paste setup guide, read the AI Client Setup Guide.
How GABS works
Each launch resolves along one axis:
stable game identity → optional named profile → optional declared, typed launch inputs
- Games are declared in a config file. GABS re-reads it on the next call —
edits to game entries apply automatically, with no GABS or MCP-client
restart. After an edit,
games_show <id>shows the new profiles, inputs, warnings, or the exact error. Top-level settings (apiKey,toolNormalization,portRanges,timeouts,stripOutputSchema) are read at startup only and still require a GABS restart. - Profiles select a repeatable launch context (args, env, working directory,
lifecycle overrides) without changing the game's identity or transport. A bare
start uses the
defaultProfile. - Launch inputs add bounded, declared per-launch variation: the config
author declares named, typed inputs (
boolean/string/integer), and callers may supply only those. GABS never exposes raw argument/environment passthrough on MCP. - Lifecycle hooks (
status,stop,kill) let you integrate wrapped or containerized process management — GABS runs your commands to observe and control the workload.
Two frontends share one implementation:
- MCP server (
gabs server) — for AI agents. - CLI (
gabs games ...) — for humans and scripts.
The mental model most users need:
- Your AI client starts
gabs server - GABS starts or attaches to your game
- If the game-side bridge speaks GABP, GABS mirrors that bridge's tools into MCP
AI Agent ← MCP → GABS ← GABP Client → GABP Server (Game Bridge) ← Game API → Game
In the GABP layer, your game-side bridge is the server and GABS is the client.
Quick Start
1. Download and verify the binary
Download the latest release bundle for your system from GitHub Releases.
Available archives are named like:
- Windows x64:
gabs-<version>-windows-amd64.zip - macOS Apple Silicon:
gabs-<version>-darwin-arm64.zip - macOS Intel:
gabs-<version>-darwin-amd64.zip - Linux x64:
gabs-<version>-linux-amd64.zip - Linux ARM64:
gabs-<version>-linux-arm64.zip
Each archive contains the gabs binary (gabs.exe on Windows), README.md,
the full docs/ folder, example-config.json, and LICENSE.
After unzipping:
Windows
.\gabs.exe version
macOS / Linux
chmod +x gabs
./gabs version
2. Configure a game
Games live in your config file (~/.gabs/config.json by default). You can write
entries by hand or let the interactive setup do it for you:
gabs games add mygame
A minimal entry looks like this — see example-config.json for a fully profiled
game with launch inputs and lifecycle hooks:
{
"version": "1.0",
"games": {
"mygame": {
"id": "mygame",
"name": "My Game",
"launchMode": "DirectPath",
"target": "/opt/mygame/bin/server",
"stopProcessName": "server",
"defaultProfile": "dev",
"profiles": {
"dev": { "description": "Fast local iteration" }
}
}
}
}
launchMode may be a direct path, a managed Steam game, an Epic App ID, or a
custom command. For launcher URL modes such as SteamAppId and EpicAppId,
games_stop and games_kill need a way to reach the real game process:
declare stopProcessName, or a game-level status hook plus a stop or
kill hook — either satisfies the requirement. Because game-entry edits apply
automatically, gabs games show mygame always reflects what an edit would
launch.
3. Add GABS to your AI client
Paste one of these into your AI client's MCP config.
Claude Desktop:
{
"mcpServers": {
"gabs": {
"command": "/path/to/gabs",
"args": ["server"]
}
}
}
Codex CLI:
[mcp_servers.gabs]
command = "/absolute/path/to/gabs"
args = ["server"]
Generic MCP client:
{
"command": "/absolute/path/to/gabs",
"args": ["server"]
}
If your client uses strict OpenAI-style tool naming, enable toolNormalization
in ~/.gabs/config.json. See
OpenAI Tool Normalization. If your client
disconnects after tools/list because it rejects a public tool's outputSchema
fields, set stripOutputSchema to true (see the
Configuration Guide). If a game or bridge starts slowly,
tune the background connection budget with timeouts.startup; games_start
still returns after a bounded initial wait so MCP clients do not time out while
the game keeps loading.
From a configured game to a tool call
One end-to-end flow, from a declared game to calling a game-specific tool:
1. See what's configured (CLI or the games_list MCP tool):
gabs games list
2. Start the game. From the CLI:
gabs games start mygame --profile dev
Pass --input NAME=VALUE (repeatable) to supply declared launch inputs — see the
fully profiled world input in example-config.json. The CLI verifies the
launch and then exits without holding a bridge connection
(outcome started_attachment_deferred). From an agent session, games_start
starts the game and keeps the bridge attached; if the game was started from the
CLI, an agent picks it up with games_connect.
3. Discover and call the game's mirrored tools (agent / MCP session). Once
the bridge connects, GABS mirrors its GABP tools into strict-safe MCP names.
The public tools/list stays core-only, so discovery goes through the core
surface:
games_connect {"gameId": "mygame"}
games_tool_names {"gameId": "mygame", "brief": true}
games_tool_detail {"tool": "mygame_inventory_get"}
games_call_tool {"tool": "mygame_inventory_get", "arguments": {...}}
Discovery entries contain the callable name, optional tags, and a summary
when brief: true. A single-game response carries gameId once at the top
level; discovery across games includes gameId per entry. Pass name unchanged
to detail or call. See the discovery response contract and migration note
if your client previously read name aliases from the list.
games_tool_names may be empty right after start while the bridge is still
connecting (started_bridge_pending) — retry rather than assuming a tool is
missing.
In an agent chat this is just: "Start mygame, then show me its game-specific tools."
Core MCP tools
Release builds expose strict-safe MCP tool names by default because some clients reject dots in tool names:
games_list- List configured game IDs (with profiles + warning counts)games_show- Show one saved game config, profiles, and launch inputsgames_start- Start a game (profile,launchInputsoptional)games_stop- Stop a game gracefullygames_kill- Force stop a gamegames_status- Check whether a game is runninggames_connect- Reconnect to a running game's bridgegames_tool_names- List mirrored game-specific tools after a bridge connectsgames_tool_detail- Show the schema for one mirrored toolgames_call_tool- Call a connected game tool through the stable core surface
Mirrored game tools are named like mygame_inventory_get (the bridge's
canonical inventory/get in strict-safe form); profile names never appear in
mirrored tool names. Older dotted names such as games.list remain accepted as
call aliases, but tools/list advertises strict-safe names unless you disable
normalization. For the full MCP surface, see the
AI Integration Guide.
Common Setup Notes
- Steam/Epic stopping: use the real game process name, not the launcher name.
- Steam bridge games: prefer
SteamManagedlaunch. It resolves the Steam app manifest to the installed executable, starts Steam if needed, and launches with GABP environment variables. On macOS, GABS first proves that Steam's IPC/global-user interface, the configured app's subscription/install state, and a process-local Steamworks API initialization are ready; a merely running Steam process or connected global user is not enough.store_client_not_readymeans no game process was started: retry the same request after Steam settles (a largertimeoutcan help when the reason isreadiness_timeout). Some managed apps can still relaunch the final process without those variables;games_statusreports that asprocess-bridge-environment-missing. Usegabs games doctor <id>to inspect a config,gabs games repair <id>to convert an olderSteamAppIdlauncher-URL config, andDirectPathorCustomCommandwhen the final process does not inherit the bridge environment. - More than one AI session: that is fine. GABS coordinates ownership per game
with a short active-owner lease.
games_connecttakes over naturally after the previous session goes idle, while active game-bound calls are still protected. - Game bridge cannot find GABP configuration: the game-side bridge should
read
GABP_SERVER_PORT,GABP_TOKEN, andGABS_GAME_IDfrom its process environment. Thebridge.jsonfile is GABS' endpoint cache/debug artifact, not runtime input for game-side bridge code. - Start says the endpoint cache port is already in use: use
games_connectif an existing game-side bridge owns that endpoint. Usegames_startwithresetEndpoint: trueonly after confirming the cache should be rotated. - Confusing bridge state: start with
games_status. Ifdiagnostics.codeisprocess-bridge-environment-missing, the running process is visible but not attachable through the expected GABP environment; adjust the launch mode instead of retryinggames_connect.
Documentation
- AI Client Setup Guide - Install a release bundle and connect Claude Desktop, Codex CLI, or generic MCP clients
- v1.1.0 Release Notes - Upgrade order, compatibility changes, and profile-migration guidance
- Configuration Guide - Config schema, profiles, launch inputs, lifecycle hooks, and tool normalization
- AI Integration Guide - Connect GABS to different AI tools and deployment scenarios
- GABP Bridge Development Guide - Add GABP support to your game integrations
- Advanced Usage Guide - Multiple instances, HTTP mode, scripting, and more
- Deployment Guide - Production deployments and cloud setups
- OpenAI Tool Normalization - Configure tool name compatibility for OpenAI API
- Dynamic Tools Guide - How AI agents handle expanding tool sets
- AI Dynamic Tools FAQ - Common questions about dynamic tool discovery
For Bridge Developers
Want your game to work with GABS? Add GABP support to your game-side bridge:
-
Read GABP configuration from environment variables when your game starts:
GABS_GAME_ID- Your game's identifierGABP_SERVER_PORT- Port your game-side bridge should listen onGABP_TOKEN- Authentication token for GABS connections
The
bridge.jsonfile is GABS' endpoint cache/debug artifact. Do not read it as game-side runtime configuration. -
Start a local GABP server to listen for GABS connections (your game-side bridge = server, GABS = client).
-
Implement the current GABP runtime methods (
session/hello,tools/list,tools/call) or use the officialgabp-runtimelibrary so your schemas match what GABS expects.- For GABP v1.1 bridges, advertise optional attention support through capabilities before exposing
attention/current,attention/ack, and the attention lifecycle channels.
- For GABP v1.1 bridges, advertise optional attention support through capabilities before exposing
-
Expose game features as tools, resources, and events using canonical GABP tool names such as
inventory/getorcore/ping.
See the GABP Bridge Development Guide for complete examples in C#, Java, and Python.
Build from Source
Requirements: Go 1.22+
# Simple build
go build ./cmd/gabs
# Build with version information (recommended)
make build
# Build with custom version
go build -ldflags "-X github.com/pardeike/gabs/internal/version.Version=vX.Y.Z" ./cmd/gabs
Contributing & Support
- Issues & Ideas: GitHub Issues
- GABP Protocol: GABP Repository
- Example Configuration: See
example-config.jsonfor sample configurations
License
MIT License - see LICENSE for details.
GABS makes AI-game interaction simple. Configure once, control naturally.
Preguntas sobre GABS MCP
¿Qué herramientas proporciona GABS MCP?
Expone 10 herramientas, incluidas games_list, games_show, games_start, games_stop, games_kill.
¿Cómo controla un agente de IA un juego en ejecución a través de GABS?
GABS inicia o se conecta al juego configurado y, una vez que el puente GABP del juego se conecta, refleja las herramientas de ese puente en una interfaz MCP estable. El agente puede entonces listar y llamar a esas herramientas reflejadas a través de las herramientas principales.
¿Necesito reiniciar GABS después de editar una entrada de juego en la configuración?
No. GABS vuelve a leer la configuración en la siguiente llamada, por lo que los cambios en las entradas de los juegos se aplican automáticamente sin necesidad de reiniciar GABS ni el cliente MCP. Los ajustes de nivel superior sí requieren un reinicio.
¿Cómo añado GABS a Claude Desktop?
Añade una entrada gabs a mcpServers cuyo command sea la ruta al binario de gabs y cuyos args sean ["server"].
¿Qué modos de lanzamiento puede usar GABS para iniciar un juego?
launchMode puede ser una ruta directa, un juego de Steam gestionado, un Epic App ID o un comando personalizado.
¿Por qué games_tool_names está vacío justo después de iniciar un juego?
Es posible que el puente aún se esté conectando, por lo que la lista puede estar vacía mientras el juego está en el estado started_bridge_pending. Intenta de nuevo en lugar de asumir que falta una herramienta.