Fuel MCP Server

Most cloud and infrastructure work still happens through a UI a human drives. Fuel MCP server moves it into the conversation instead. This project provides a Model Context Protocol (MCP) server for the Fuel Network and Sway Language ecosystem. It allows IDEs (like Cursor) to search and interact with Fuel documentation directly within the development environment.

The short version

• Local semantic search of docs.fuel.network content
• No Docker dependency - runs with just Bun
• Fast file-based vector storage with Vectra
• Enhanced result filtering and formatting
• Hybrid search with keyword fallback

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: VECTRA_INDEX_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Bun: Install from bun.sh

How it compares

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by FuelLabs; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Fuel's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.