Bridgetek EAB MCP Server Extension

Bridgetek Eve Asset Builder (EAB) MCP server as a Visual Studio Code extension — a Model Context Protocol (MCP) server that lets AI agents drive Bridgetek EAB Tools (eab_tools.exe) to convert, compress, validate and program EVE graphics assets (images, fonts, audio, video, GIF animations, raw pixel buffers, SPI flash images).

It exposes typed per-command tools (eab_*), a natural-language assistant (the mandatory eab routing tool), Server Instructions, resources, prompt templates, workflows and sampling — all backed by a mandatory user-confirmation flow before any eab_tools.exe command runs.

This is one of three distributions of the same server — also available as an npm package and to run from source code (see public/npm/README.md and the repo-root README.md).

Github: https://github.com/BridgetekChip/EAB-CLI-MCP-Server

Quick Start

Install the extension from the VS Code Marketplace (or locally with code --install-extension <path>.vsix).
Open the Command Palette (Ctrl+Shift+P) and run EAB MCP Server: Input eab_tools.exe to select a detected EAB installation or enter the full path to eab_tools.exe.
Reload Window to start the MCP server.
Ask your agent (e.g. in Copilot Chat):
- "List the available EAB tools."
- "Convert image.png to RGB565 for BT82X."
- "Build a font from my TTF file."
- "Program this flash image onto the SPI flash."

Requirements: Bridgetek EAB installed from https://brtchip.com/eab/ (or provide the path to eab_tools.exe). The server auto-discovers eab_tools.exe under C:\Users\Public\Documents\EVE Asset Builder\<version>\tools\eab_tools.exe.

Usage Examples

Typed eab_* tools never run the CLI directly — they return a preview + requestId. Execution requires an explicit final confirmation via execute_eab_tool_call with confirm: true.

Find the right command — call eab (or ask_eab) with query = "convert an image to RGB565"; it returns img_cvt as the best match, with required flags and an example invocation.
Convert an image — call eab_img_cvt with { "input": "assets/logo.png", "output_dir": "./out", "format": "RGB565", "chip_gen": "82x" } → get a requestId; adjust options with update_eab_tool_call if needed; then execute_eab_tool_call with { "requestId": "...", "confirm": true }.
Build a font — eab_font with the TTF/OTF path and an output folder.
Program SPI flash — eab_flash_gen / eab_flash_prog (always gated behind confirmation — never auto-run).
Compress assets — eab_compress (zlib / zopfli) — a legacy "Both" command with no chip_gen.
Explain a command — explain_eab_command with command = "img_cvt" returns the chip, every option and an example invocation.

MCP Client configuration (full list)

The extension registers the EAB MCP server automatically — no mcp.json editing needed. Depending on the client:

⚠️ Official support: only GitHub Copilot, OpenAI Codex and Claude Code are officially supported and tested. Other MCP clients (Cursor, Gemini CLI, Windsurf, Continue, Cline, …) are best-effort only — they can be registered automatically, but are not officially supported.

Client	How to connect
VS Code / Copilot Chat	Automatic. The extension registers the server via `mcpServerDefinitionProviders`; it appears in MCP: List Servers and is started on demand. Just Reload Window after installing and (if prompted) trust/enable the server.
Codex (app / CLI)	Automatic + HTTP. On every VS Code launch the extension starts a local Streamable HTTP MCP server at `http://127.0.0.1:8397/mcp` and registers it with Codex (`codex mcp add` + `~/.codex/config.toml`). Restart Codex, then ask it to "list the available eab tools".
Claude Code (app / CLI)	Automatic + HTTP. On every VS Code launch the extension starts a local Streamable HTTP MCP server at `http://127.0.0.1:8397/mcp` and registers it with Claude Code (`claude mcp add` + `~/.claude.json`). Restart Claude Code, then ask it to "list the available eab tools".
Cursor / Gemini CLI / Windsurf / Continue (best-effort)	Automatic. On every VS Code launch the extension upserts the EAB entry (`eab` + `eab-stdio`) into each installed agent's config (`~/.cursor/mcp.json`, `~/.gemini/settings.json`, `~/.codeium/windsurf/mcp_config.json`, `~/.continue/config.json`) via `node:fs`; Gemini CLI also gets `gemini mcp add`. Not officially supported.
Other MCP clients (Cline, …) (best-effort)	Point them at the local HTTP endpoint `http://127.0.0.1:8397/mcp` (VS Code must be running with this extension), or use the npm package (`@bridgetek/eab-mcp-server`) for a standalone stdio server — see the npm package readme. Not officially supported.

One-shot onboarding for every installed agent — the bundled script node scripts/setup-agents.mjs scans the machine, detects which agents are installed (Codex, Claude Code, Cursor, Gemini CLI, Windsurf, Continue), and writes the EAB entry to all of their configs at once. Default stdio mode works even when VS Code is closed; add --http to point them at the VS Code-hosted HTTP server instead. See DEVELOPMENT.md for details.

Optional VS Code settings (eabMCP.*): eabToolPath (path to eab_tools.exe), specPath (alternative spec), httpEnabled / httpPort (Codex / Claude Code HTTP endpoint, default 8397), autoRegisterCodex, autoRegisterClaude, autoRegisterAgents.

License

MIT