Katana MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WALLET_PRIVATE_KEY | Yes | A wallet private key with funds on supported networks. |
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 |
|---|---|
| bridgeAssetsB | Bridge tokens from supported chains to Katana network. Automatically generates deposit address and sends tokens from your wallet. Also inform user their tokens will be automatically bridged to ETH on Katana. |
| getTokenBalancesA | Get token balances for your wallet on Katana network (uses address from private key in environment) |
| getYearnVaultInfoB | Get detailed information about Yearn vaults on Katana network |
| depositToYearnVaultB | Deposit tokens into a Yearn vault on Katana network. Only works with tokens already on Katana (USDC, ETH, WBTC, USDT, AUSD). |
| withdrawFromYearnVaultB | Withdraw tokens from a Yearn vault on Katana chain |
| getUserYearnPositionsA | Get detailed information about your Yearn vault positions (uses address from private key in environment) |
| getSushiQuoteA | Get a quote for swapping tokens on SushiSwap on Katana network |
| executeSushiSwapB | Execute a token swap on SushiSwap on Katana network |
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 8 tools
Each tool targets a distinct operation: bridging assets, swapping on SushiSwap (with a separate quote tool), and Yearn vault actions (deposit, withdraw, info). No two tools have overlapping purposes.
All tool names follow a consistent camelCase verb_noun pattern (e.g., bridgeAssets, getTokenBalances, depositToYearnVault). Verbs like 'get', 'execute', 'deposit', 'withdraw' are used consistently.
With 8 tools covering bridging, swapping, and yield operations, the count is well-scoped for the server's purpose. Each tool serves a clear role without redundancy.
The tool set covers core workflows: bridging, swapping with quotes, and full Yearn vault management. Minor gaps exist (e.g., no approval tool or token listing), but agents can execute the primary actions without dead ends.