Galactic Bridge

What Galactic Bridge MCP server does

The Galactic Bridge MCP server exposes the public Galactic Bridge API through MCP for LayerZero OFT route discovery. It covers 14 EVM networks and works from token contract addresses rather than relying on a token being listed in a bridge aggregator. Agents can identify where a token exists, inspect its OFT contracts, and determine whether a route is currently enabled.

The server is relevant to the Finance & Fintech category when an agent needs to inspect cross-chain token movement or prepare a bridge transaction. It does not operate the bridge infrastructure itself; it calls the same public API used by the Galactic Bridge website.

How it works

Three MCP tools provide the main workflow:

• list_supported_networks returns each supported network’s chain key, EVM chain ID, LayerZero endpoint ID, and native token symbol.
• scan_token_networks accepts a token address and reports the networks where that token is present, along with the corresponding OFT contract on each network.
• find_bridge_route resolves a source and destination network. Its response includes the OFT contract, whether the requested direction is enabled, and the current fee. Supplying an amount and recipient also produces transaction fields such as to, data, value, and chainId.

When a token uses a separate adapter, the route response can include an ERC-20 approval transaction that must be handled before the bridge transaction. The Galactic Bridge MCP server returns these transactions for review and signing by the user’s wallet; read-only operation does not access keys or broadcast transactions.

Setup and configuration

Node.js 18 or newer is required. For Claude Desktop, configure the server with npx -y galactic-bridge-mcp as the command and add the server under the MCP configuration. Cursor and other MCP clients can use the same command over stdio. Running from source requires cloning the repository, installing npm dependencies, building the project, and starting node dist/index.js.

GB_API_URL can replace the default API base URL, which is https://galacticbridge.app. The server remains read-only when GB_PRIVATE_KEY is not set.

Limitations and notes

find_bridge_route does not sign or send transactions in its default mode. A person or wallet must inspect and sign the returned data. Fees and token decimals are read live, and disabled directions are reported rather than producing a transaction expected to revert.

An optional auto-signing mode becomes available when GB_PRIVATE_KEY is configured. It adds execute_bridge, which can build, sign, and broadcast the bridge transaction and any required approval. This mode requires the optional ethers package and may need a GB_RPC_<CHAIN> override for networks without a built-in public RPC. It moves real funds and should be treated as an advanced, high-risk configuration. The software is provided under the MIT license and without warranty.