Galactic Bridge

io.github.mckellen-ethv0.1.1Updated Oct 4, 2026

Find LayerZero OFT bridge routes by contract address across 14 EVM networks.

VerifiedSTDIODesktop onlyDeveloper ToolsFinance

Overview

AI-generated overview

Finds LayerZero OFT cross-chain bridge routes by token contract address across 14 EVM networks and builds ready-to-sign transactions.

What it does
Talks to the public Galactic Bridge API to list supported networks, scan which networks a token address exists on, and resolve a bridge route between two networks. For a route it returns the OFT contract, whether the direction is currently enabled, the live fee, and, given an amount and recipient, a ready-to-sign transaction object plus an ERC-20 approval when a separate adapter is used. It never signs or sends transactions by default.
When to use it
Useful when an assistant needs to look up cross-chain bridge routes for a token contract, including tokens not listed on aggregators, or to prepare a bridge transaction for a user to review and sign in their own wallet.
Requirements
Node.js 18 or later, run locally via npx with stdio transport. Network access to the public Galactic Bridge API. No account or API key is needed for read-only use. Optional auto-signing requires the ethers package and, for some chains, an RPC override such as GB_RPC_ .
Before you install
Read-only by default and never holds a key. Setting GB_PRIVATE_KEY enables the execute_bridge tool, which signs and broadcasts transactions and moves real funds irreversibly; it is off unless explicitly enabled. Use a dedicated hot wallet holding only what you can afford to lose, and always verify a transaction before signing.

Installation

In SourceWeft

  1. Open Galactic Bridge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Galactic Bridge MCP

An MCP server that lets AI agents and MCP clients (Claude Desktop, Cursor, …) use Galactic Bridge to find LayerZero OFT bridge routes by token contract address and build ready-to-sign cross-chain transactions across 14 EVM networks — including tokens that aren't listed on aggregators like Stargate.

By default this server is read-only. It finds routes and builds transactions, but it never holds a key and never signs anything — a human or wallet does that. Auto-signing is an optional add-on you turn on yourself (see the bottom).

What it does

It talks only to the public Galactic Bridge API — the same endpoints the website calls. It does not run on the bridge's servers and changes nothing there.

Tools

ToolWhat it does
list_supported_networksThe 14 networks, with chain key, chainId, LayerZero eid and native symbol.
scan_token_networksGiven a token address, every network it exists on and its OFT contract on each.
find_bridge_routeResolves a route between two networks: OFT contract, whether the direction is enabled right now, the fee, and — with amount + recipient — a ready-to-sign transaction (plus an ERC-20 approval when the token bridges through a separate adapter).

find_bridge_route never signs or sends. It returns transaction objects ({ to, data, value, chainId }) for you to review and sign in your own wallet.

Install

Requires Node.js 18+.

Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "galactic-bridge": {      "command": "npx",      "args": ["-y", "galactic-bridge-mcp"]    }  }}

Cursor / other MCP clients

Point the client at the command npx -y galactic-bridge-mcp (stdio transport).

From source

bash
git clone https://github.com/mckellen-eth/galactic-bridge-mcp.gitcd galactic-bridge-mcpnpm installnpm run buildnode dist/index.js

Example

"Bridge 50 of token 0x90e7…d9e1 from BNB Chain to Arc, to my address 0xABC…"

The agent calls find_bridge_route and gets back a ready transaction plus the fee. You review it and sign in your wallet. If the token uses a separate adapter, you'll also get an approval transaction to sign first.

Safety

  • No keys by default. The read-only tools never see a private key.
  • You sign. Transactions are returned for review; your wallet signs them.
  • Fees and decimals are read live, so amounts are exact. Directions that a token has disabled are reported instead of returning a transaction that would revert.

Always verify a transaction before signing. This software is provided as-is, with no warranty (MIT).

Optional: auto-signing (advanced)

You can let the server sign and broadcast transactions itself by setting a private key in your environment. This moves real funds irreversibly and is off by default. Only enable it if you understand the risk, and use a dedicated hot wallet that holds no more than you can afford to lose.

json
{  "mcpServers": {    "galactic-bridge": {      "command": "npx",      "args": ["-y", "galactic-bridge-mcp"],      "env": {        "GB_PRIVATE_KEY": "0xyourHotWalletKey"      }    }  }}

When GB_PRIVATE_KEY is set, an extra tool appears — execute_bridge — which builds, signs and broadcasts the bridge transaction (and the approval first, if needed). It needs the optional ethers package (npm install ethers) and, for networks without a built-in public RPC, an override like GB_RPC_BSC=….

Without GB_PRIVATE_KEY, none of this loads and the server stays read-only.

Configuration

VariablePurpose
GB_API_URLOverride the bridge API base URL (default https://galacticbridge.app).
GB_PRIVATE_KEYOpt in to auto-signing. Unset = read-only.
GB_RPC_<CHAIN>RPC URL used by auto-signing for that chain (e.g. GB_RPC_ARC).

Source: README.md at commit e5ec942

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.1LatestOct 4, 2026