LayerZero OFT MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy-and-configure-oft-multichainB | Deploys an OFT contract to multiple chains, sets up peer connections, and configures enforced options. |
| bridge-oftB | Bridges OFT tokens from one chain to another using LayerZero. |
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 2 tools
The two tools have clearly distinct purposes: bridge-oft handles token transfers between existing chains, while deploy-and-configure-oft-multichain handles contract deployment and configuration across chains. There is no overlap in functionality, making it easy for an agent to select the correct tool.
Both tools use kebab-case naming, which is consistent. However, the first tool uses a simple verb-noun format (bridge-oft), while the second is more complex with multiple verbs and nouns (deploy-and-configure-oft-multichain), showing a minor deviation in naming style.
With only two tools, the server feels thin for a multichain token deployment and bridging domain. While the tools cover core operations, typical LayerZero OFT workflows might benefit from additional tools for tasks like querying deployments or managing configurations.
The tools cover deployment and bridging, which are essential operations, but there are notable gaps. Missing tools for querying deployed contracts, checking bridge status, or updating configurations could lead to agent workarounds or failures in complex workflows.