create_tx
Create a cross-chain swap transaction via the deBridge DLN protocol
LABSCO SUMMARY
It builds the transaction; the signature stays with you.
No private key appears anywhere in the surface: both creation tools take addresses and return a transaction, which puts the irreversible step outside this server entirely. The three read tools exist because the two write tools need exact values — a chain that is genuinely supported, and a token resolved to its address on that chain. get_instructions telling you to call it first is unusual advice and worth taking, because create_tx's argument list is long and order-authority addresses are precisely the kind of value that gets guessed wrongly.
What it is
A five-tool deBridge server covering the instruction guide, token and chain lookup, and cross-chain or same-chain swap transaction creation.
What you get
- get_instructions, returning the full guide for this server — its own description says to call it first
- search_tokens across the deBridge token database by name, symbol or contract address, scoped to a chain
- get_supported_chains, the networks deBridge covers for cross-chain swaps
- create_tx, building a cross-chain swap through the DLN protocol from source and destination chains, tokens and amounts, the order authority address on each chain, the recipient, an affiliate fee and an operating-expense flag
- transaction_same_chain_swap, building a same-chain swap with slippage, a source-chain priority level and an affiliate fee
Requirements
Nothing configured through this server. Both creation tools take the addresses as arguments — the sender, the order authority on each chain and the recipient — and neither signs anything.
Setup effort
Add the hosted endpoint — paste it into your client
USE CASES
01
Turning a swap request into a transaction to sign
Read the server's guide first, confirm both networks are supported, resolve each token to the address the protocol expects, and build the cross-chain order with an authority address on each side.
02
Resolving a contract address someone pasted
Look the address up in the token database to get the name and symbol behind it, and check the chain it sits on is one deBridge covers before planning anything around it.
03
Swapping inside one chain with a slippage limit you set
The same-chain path takes the two tokens, the amount, a sender and recipient, and your own slippage and priority level, so the trade is composed to your tolerance rather than a default.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_instructions
Returns the full guide for the deBridge MCP server. CALL THIS FIRST.
get_supported_chains
List all blockchain networks supported by deBridge for cross-chain swaps
search_tokens
Search for tokens by name, symbol, or contract address in the deBridge token database
transaction_same_chain_swap
Create a same-chain token swap transaction via deBridge
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
ENDPOINT URL
https://agents.debridge.com/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add debridge --transport http https://agents.debridge.com/mcpCursor
CURSOR · JSON
{
"mcpServers": {
"debridge": {
"url": "https://agents.debridge.com/mcp"
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"debridge": {
"type": "http",
"url": "https://agents.debridge.com/mcp"
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"debridge": {
"type": "streamable-http",
"serverUrl": "https://agents.debridge.com/mcp"
}
}
}Cline
CLINE · JSON
{
"mcpServers": {
"debridge": {
"type": "streamableHttp",
"url": "https://agents.debridge.com/mcp"
}
}
}Continue
CONTINUE · YAML
mcpServers:
- name: debridge
type: streamable-http
url: https://agents.debridge.com/mcpZed
ZED · JSON
{
"context_servers": {
"debridge": {
"url": "https://agents.debridge.com/mcp"
}
}
}OpenClaw
OPENCLAW · JSON
{
"plugins": {
"entries": {
"mcp-adapter": {
"enabled": true,
"config": {
"servers": [
{
"name": "debridge",
"transport": "http",
"url": "https://agents.debridge.com/mcp"
}
]
}
}
}
}
}Any MCP client — npx
ANY MCP CLIENT — NPX · JSON
{
"mcpServers": {
"debridge": {
"command": "npx",
"args": [
"-y",
"@debridge-finance/debridge-mcp@latest"
]
}
}
}Only for a client that cannot connect to a remote HTTP endpoint: this runs the npm package as a local stdio proxy that forwards every request to https://agents.debridge.com/mcp. It needs Node.js 18 or later.
