Galactic Bridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GB_API_URL | No | Override the bridge API base URL (default `https://galacticbridge.app`). | https://galacticbridge.app |
| GB_PRIVATE_KEY | No | Opt in to auto-signing. Unset = read-only. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_supported_networksA | List the EVM networks Galactic Bridge supports, with their chain key, chainId, LayerZero endpoint id (eid) and native gas symbol. Use the |
| scan_token_networksA | Given a token contract address, find every supported network the token exists on and its OFT bridge contract on each. Useful to discover where a token can be bridged from and to before resolving a specific route. |
| find_bridge_routeA | Resolve the bridge route for a token between two networks: the OFT contract, whether the direction is enabled right now, the fee, and — if amount and recipient are given — a ready-to-sign transaction (plus an ERC-20 approval transaction when the token bridges through a separate adapter). This tool NEVER signs or sends; it returns transactions for a human or wallet to review and sign. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool addresses a distinct step in the bridge workflow: listing supported chains, discovering token deployments, and resolving a specific route. There is no meaningful overlap between the three tools.
All tool names follow a consistent snake_case verb_noun pattern: list_supported_networks, scan_token_networks, find_bridge_route. The naming style and verb usage are uniform across the set.
Three tools is a well-scoped and appropriate size for this server's purpose. Each tool covers a necessary leg of the bridge-route discovery process without redundancy.
The tool set fully covers the intended discovery workflow: knowing supported networks, locating a token on those networks, and resolving an executable bridge route. The explicit decision not to sign/send transactions is a stated boundary, not a gap.