1inch MCP server
{
"mcpServers": {
"1inch-mcp": {
"type": "http",
"url": "https://api.1inch.com/mcp/protocol"
}
}
}{
"mcpServers": {
"1inch-mcp": {
"type": "http",
"url": "https://api.1inch.com/mcp/protocol"
}
}
}{
"mcpServers": {
"1inch-mcp": {
"type": "http",
"url": "https://api.1inch.com/mcp/protocol"
}
}
}{
"servers": {
"1inch-mcp": {
"type": "http",
"url": "https://api.1inch.com/mcp/protocol"
}
}
}{
"mcpServers": {
"1inch-mcp": {
"type": "http",
"url": "https://api.1inch.com/mcp/protocol"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
The 1inch MCP server exposes token swaps, limit orders, portfolio data, market prices, and documentation search for the 1inch DEX aggregator. It is for developers building AI agents and assistants that need to interact with DeFi trading, wallet data, and on-chain analytics.
- Search 1inch documentation and SDK examples to answer integration questions.
- Execute token swaps and cross-chain trades, or place limit orders on behalf of authenticated users.
- Query wallet portfolios, balances, transaction history, spot prices, and gas fees across multiple blockchains.
Tools this server exposes
| Tool | Does |
|---|---|
| search | Search 1inch documentation and get relevant results. |
| list_examples | List available SDK code examples. |
| get_example | Retrieve a specific SDK code example. |
| swap | Execute a token swap on 1inch (Classic, Fusion, or cross-chain). |
| orderbook | Create or manage limit orders. |
| product_api | Access wallet data, portfolio information, market data, gas prices, and infrastructure APIs. |
| walletconnect | Initiate non-custodial WalletConnect pairing for transaction signing. |
| aqua | Retrieve Aqua strategy analytics. |
| debug | Look up organization-scoped request logs (when enabled). |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.