We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

1inch

MCP server by 1inch

Search 1inch docs and SDK examples, and run swaps, limit orders and product API calls for prices, portfolio and gas.

Sign-in optional (Works without an account; sign in for more)Streamable HTTP

Connect to 1inch

Sign-in is optional. Connect with 1inch’s own URL:

https://api.1inch.com/mcp/protocol

It works without signing in. Sign in with 1inch for more access.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/1inch

About

Connects an assistant to the 1inch Business platform. It can search the 1inch documentation and API reference, list and fetch SDK examples, get swap quotes and execute classic, Fusion and cross-chain swaps, build and manage limit orders, and call other 1inch product APIs such as portfolio, spot prices and gas price. It also includes Aqua position analytics, WalletConnect pairing and org-scoped request log lookup.

The server is hosted at https://api.1inch.com/mcp/protocol using streamable HTTP. Documentation search, SDK examples, Aqua analytics and WalletConnect work without sign-in. Swap, orderbook, product API and debug tools need an OAuth sign-in with a 1inch Business account, started with the authenticate tool. Wallet transactions are signed by the user in their own wallet.

What you can do

  • Search 1inch documentation and API reference
  • Browse and read SDK example source code
  • Get quotes and execute classic, Fusion and cross-chain swaps
  • Build, list and cancel limit orders via the Orderbook API
  • Call 1inch product APIs for portfolio, prices and gas
  • Read Aqua market-making position analytics
  • Pair an EVM or Solana wallet through WalletConnect
  • Look up organization request logs for debugging

Tools 10

  • searchRead-only

    Search 1inch documentation and API reference.

  • list_examplesRead-only

    List available SDK code examples.

  • get_exampleRead-only

    Get the full source code of an SDK example.

  • authenticateRead-only

    Start or confirm 1inch Business OAuth login.

  • swapCan delete

    Get swap quotes and execute classic, Fusion or cross-chain swaps. Requires sign-in.

  • orderbookCan delete

    Build, create, list and cancel limit orders via the Orderbook API. Requires sign-in.

  • product_apiCan delete

    Call any 1inch product API endpoint with the user's credentials. Requires sign-in.

  • aquaCan delete

    Aqua shared-liquidity position analytics and maker position writes.

  • walletconnectCan delete

    Pair and use an EVM or Solana wallet via WalletConnect v2.

  • debugRead-only

    Look up production API request logs for your organization. Requires sign-in.

Read from the live server on 17 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

Example prompts

  • Search the 1inch docs for how to create a Fusion order

  • Show me the SDK example for a cross-chain swap

  • Get a quote to swap 1000 USDC to USDT on Ethereum

  • What is the current gas price on Ethereum according to 1inch?

Set up

Every client connects to api.1inch.com. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http 1inch https://api.1inch.com/mcp/protocol
  1. Start Claude Code and type /mcp. 1inch should show as connected. To sign in for more access, pick it and choose Authenticate.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Customize → Connectors, click + Add, then Add custom connector.
  2. Name it 1inch and paste this URL:
https://api.1inch.com/mcp/protocol
  1. Click Add, then Connect. Signing in to 1inch is optional.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://api.1inch.com/mcp/protocol and click Add.
  2. Click Connect. Signing in to 1inch is optional.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
  2. Enter a name for the server.
  3. Under Connection, paste https://api.1inch.com/mcp/protocol as the server URL, then for authentication choose No authentication, or OAuth to sign in to 1inch for more access.
  4. Check I understand and want to continue, then select Create as a plugin.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "1inch": {
      "url": "https://api.1inch.com/mcp/protocol"
    }
  }
}

VS Code

Or from a terminal:

code --add-mcp '{"name":"1inch","type":"http","url":"https://api.1inch.com/mcp/protocol"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "1inch": {
      "type": "http",
      "url": "https://api.1inch.com/mcp/protocol"
    }
  }
}

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "1inch": {
      "serverUrl": "https://api.1inch.com/mcp/protocol"
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add 1inch --url https://api.1inch.com/mcp/protocol

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.1inch]
url = "https://api.1inch.com/mcp/protocol"

Gemini CLI

gemini mcp add --transport http 1inch https://api.1inch.com/mcp/protocol

Then, inside Gemini CLI, run /mcp auth 1inch to sign in (optional).

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "1inch": {
      "type": "http",
      "url": "https://api.1inch.com/mcp/protocol"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://api.1inch.com/mcp/protocol.

Embed

Show 1inch in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![1inch on mcp.tc](https://mcp.tc/i/1inch/badge.svg)](https://mcp.tc/i/1inch)
HTML
<a href="https://mcp.tc/i/1inch"><img src="https://mcp.tc/i/1inch/badge.svg" alt="1inch on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/1inch.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/1inch" title="1inch on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/1inch.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the 1inch card to your site.

Markdown
Add the mcp.tc card for 1inch, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/1inch.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="1inch"><a href="https://mcp.tc/i/1inch">1inch on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![1inch on mcp.tc](https://mcp.tc/i/1inch/badge.svg)](https://mcp.tc/i/1inch)
```

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:35 UTC.

Follow 1inch and we’ll email you when something changes.

  1. , Automatic check

    1 tool changed.

    Details, 17 Nov 2026, 14:53 UTC

    Changed 1

    • product_apidescription

      The text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.

  2. , Automatic check

    3 tools changed. Server instructions changed.

    New server instructions

    Details, 17 Nov 2026, 05:52 UTC

    Changed 3

    • aquadescription and input schema
      Before

      1inch Aqua (shared-liquidity market making): position analytics plus maker position writes. Write actions (OAuth, or WalletConnect + signed 1inch ToS (pass walletSessionToken after MCP session rotation); non-custodial — the user's wallet signs): create_position (two-phase: call once for a preview + previewRef, then again with confirmed:true), close_position (confirmed:true; closing is permanent). Anonymous writes execute only via WalletConnect (execute=false is rejected). REQUIRED: "action" — read actions (no OAuth): maker_stats, list_maker_strategies, strategy_overview, strategy_activity, strategy_volume, list_opened. Read the resource file://1inch-mcp/guides/aqua-workflow for per-action examples, priceRange semantics, and maker position flows. Raw HTTP: product_api with path "/aqua/v1.0/strategies/...".

      After

      1inch Aqua (shared-liquidity market making): position analytics plus maker position writes. Write actions (OAuth, or WalletConnect + signed 1inch ToS (pass the walletSessionToken from connect on anonymous writes); non-custodial — the user's wallet signs): create_position (two-phase: call once for a preview + previewRef, then again with confirmed:true), close_position (confirmed:true; closing is permanent). Anonymous writes execute only via WalletConnect (execute=false is rejected). REQUIRED: "action" — read actions (no OAuth): maker_stats, list_maker_strategies, strategy_overview, strategy_activity, strategy_volume, list_opened. Read the resource file://1inch-mcp/guides/aqua-workflow for per-action examples, priceRange semantics, and maker position flows. Raw HTTP: product_api with path "/aqua/v1.0/strategies/...". Do not parse, construct or reuse the transport's client handle across callers; carry `walletSessionToken` instead.

      • Description of walletSessionToken
        Before

        Optional durable WalletConnect token from walletconnect connect. Anonymous writes must pass it after MCP session rotation (or after any walletconnect call that already used it on this session). Ignor…

        After

        Optional durable WalletConnect token from walletconnect connect. Anonymous writes should pass it; it is the durable value to carry between calls. Ignored for authenticated callers. Treat it as a secr…

      • Description of execute
        Before

        Optional. When a WalletConnect session is active, defaults to true: the transaction is sent via the wallet (user confirms the prompt). Authenticated sessions may set execute=false to return calldata…

        After

        Optional. When a wallet is paired via WalletConnect, defaults to true: the transaction is sent via the wallet (user confirms the prompt). Authenticated callers may set execute=false to return calldat…

    • product_apidescription
      Before

      [Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Call any 1inch product API endpoint using the authenticated user's credentials (base URL is the unified gateway, e.g. https://api.1inch.com). Call authenticate first. Anonymous sessions get HTTP 401 (OAuth), not x402. After a real org login, quota-exhausted routes may return a PaymentRequired tool result; retry with a signed payment in _meta["x402/payment"] (batch-settlement scheme only — see file://1inch-mcp/guides/x402-payments). Do not treat PaymentRequired as login. Optional: if your client can read MCP resources, file://1inch-mcp/guides/api-index has live Swagger links and extra gateway notes (mirrors business.1inch.com/portal/llms.txt). Common chain IDs: Ethereum=1, BNB=56, Polygon=137, Arbitrum=42161, Optimism=10, Base=8453, Avalanche=43114, Gnosis=100, zkSync=324, Line…

      After

      [Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Call any 1inch product API endpoint using the authenticated user's credentials (base URL is the unified gateway, e.g. https://api.1inch.com). Call authenticate first. Anonymous callers get HTTP 401 (OAuth), not x402. After a real org login, quota-exhausted routes may return a PaymentRequired tool result; retry with a signed payment in _meta["x402/payment"] (batch-settlement scheme only — see file://1inch-mcp/guides/x402-payments). Do not treat PaymentRequired as login. Optional: if your client can read MCP resources, file://1inch-mcp/guides/api-index has live Swagger links and extra gateway notes (mirrors business.1inch.com/portal/llms.txt). Common chain IDs: Ethereum=1, BNB=56, Polygon=137, Arbitrum=42161, Optimism=10, Base=8453, Avalanche=43114, Gnosis=100, zkSync=324, Linea…

    • walletconnectdescription and input schema
      Before

      Pair and use an EVM and/or Solana wallet via WalletConnect v2. **No authentication required** — available to every user (including unauthenticated/anonymous). Non-custodial: the server never holds keys and the user approves every signature/transaction in their own wallet. **Pairing proposal** is controlled per request via optional `pairingTarget` on `action: "connect"`: `eth` (default, eip155 only), `solana`, or `both`. Many mobile wallets fail if eip155 and solana are proposed together; prefer `eth` or `solana` unless the user needs both in one session. **Every call must include `action`** (string). **Connect QR (critical for assistants):** On `action: "connect"`, successful responses return **(1) an MCP `type: "image"` PNG** of the pairing QR (render this even if the host has no `resources/read`), then **(2) optional `resource_link`**, then **(3) text JSON** with `pairingQrResourceUri`, `presentation`, `nextSteps`, `url`, optional `mobileDeeplinks`, etc. **Desktop / scan UX:** show…

      After

      Pair and use an EVM and/or Solana wallet via WalletConnect v2. **No authentication required** — available to every user (including unauthenticated/anonymous). Non-custodial: the server never holds keys and the user approves every signature/transaction in their own wallet. **Pairing proposal** is controlled per request via optional `pairingTarget` on `action: "connect"`: `eth` (default, eip155 only), `solana`, or `both`. Many mobile wallets fail if eip155 and solana are proposed together; prefer `eth` or `solana` unless the user needs both in one pairing. **Every call must include `action`** (string). **Connect QR (critical for assistants):** On `action: "connect"`, successful responses return **(1) an MCP `type: "image"` PNG** of the pairing QR (render this even if the host has no `resources/read`), then **(2) optional `resource_link`**, then **(3) text JSON** with `pairingQrResourceUri`, `presentation`, `nextSteps`, `url`, optional `mobileDeeplinks`, etc. **Desktop / scan UX:** show…

      • Description of action
        Before

        Required. One of: connect (start pairing), status (session info), sign (EVM + Solana WC methods), send_transaction (EVM eth_sendTransaction or Solana solana_signAndSendTransaction), accept_terms (wri…

        After

        Required. One of: connect (start pairing), status (paired-wallet status), sign (EVM + Solana WC methods), send_transaction (EVM eth_sendTransaction or Solana solana_signAndSendTransaction), accept_te…

      • Description of walletSessionToken
        Before

        Optional durable token for ANONYMOUS (unauthenticated) sessions. `connect` mints a fresh token; store it and pass it back on status/sign/send_transaction/accept_terms/disconnect (and on a later `conn…

        After

        Optional durable token for ANONYMOUS (unauthenticated) callers. `connect` mints a fresh token; store it and pass it back on status/sign/send_transaction/accept_terms/disconnect (and on a later `conne…

    Server instructions

    Before

    1inch Business MCP Server — provides SDK examples and documentation search. ## SDK Examples For code implementations, use list_examples + get_example: - Intent/Fusion swaps: "@1inch-examples/intent-swap" (EVM: src/evm/, Solana: src/solana/) - Limit orders: "@1inch-examples/limit-order" - Cross-chain swaps: "@1inch-examples/cross-chain-swap" ## Documentation Search Use search for API endpoint details not covered by examples. Always prefer example code over documentation snippets. ## Authentication Initialize HTTP 200 is **not** login — that is the mcp-free / anonymous identity. Public tools work without a real org. Paid tools need a real organization (OAuth or API key), not mcp-free. All tools are always listed so you know they exist. Some require OAuth to run: - **Public (no auth):** search, list_examples, get_example, aqua (analytics actions need nothing — write actions need a WalletConnect-verified wallet that signed the 1inch Terms of Use). - **Public (no auth), when enabled:** walletconnect — non-custodial wallet pairing/signing available to every user, including unauthenticated. - **Requires OAuth:** authenticate, swap, orderbook, product_api (and debug when enabled). **Before** paid tools, call `authenticate`. If the host returns HTTP 401, complete OAuth (`mcp_auth` / connect this server), then call `authenticate` again until it returns `{ authenticated: true, ... }`. Do not treat a PaymentRequired / x402 tool result as login. Do not skip `authenticate` because initialize succeeded. ## Swap Workflow Use the "swap" tool to execute token swaps (requires authentication). Two approaches: - **Shortcut**: Call swap directly (omit quoteOnly). Omit preferredType to let the tool pick a type, or set preferredType (classic, fusion, crosschain) to choose explicitly. Set dstChain for cross-chain. - **Full flow**: Call swap with quoteOnly=true to compare quotes and receive a recommended type, then execute with the chosen preferredType. The response includes a nextStep…

    After

    1inch Business MCP Server — provides SDK examples and documentation search. ## SDK Examples For code implementations, use list_examples + get_example: - Intent/Fusion swaps: "@1inch-examples/intent-swap" (EVM: src/evm/, Solana: src/solana/) - Limit orders: "@1inch-examples/limit-order" - Cross-chain swaps: "@1inch-examples/cross-chain-swap" ## Documentation Search Use search for API endpoint details not covered by examples. Always prefer example code over documentation snippets. ## Authentication Initialize HTTP 200 is **not** login — that is the mcp-free / anonymous identity. Public tools work without a real org. Paid tools need a real organization (OAuth or API key), not mcp-free. All tools are always listed so you know they exist. Some require OAuth to run: - **Public (no auth):** search, list_examples, get_example, aqua (analytics actions need nothing — write actions need a WalletConnect-verified wallet that signed the 1inch Terms of Use). - **Public (no auth), when enabled:** walletconnect — non-custodial wallet pairing/signing available to every user, including unauthenticated. - **Requires OAuth:** authenticate, swap, orderbook, product_api (and debug when enabled). **Before** paid tools, call `authenticate`. If the host returns HTTP 401, complete OAuth (`mcp_auth` / connect this server), then call `authenticate` again until it returns `{ authenticated: true, ... }`. Do not treat a PaymentRequired / x402 tool result as login. Do not skip `authenticate` because initialize succeeded. ## Swap Workflow Use the "swap" tool to execute token swaps (requires authentication). Two approaches: - **Shortcut**: Call swap directly (omit quoteOnly). Omit preferredType to let the tool pick a type, or set preferredType (classic, fusion, crosschain) to choose explicitly. Set dstChain for cross-chain. - **Full flow**: Call swap with quoteOnly=true to compare quotes and receive a recommended type, then execute with the chosen preferredType. The response includes a nextStep…

  3. , Automatic check

    1 tool changed.

    Details, 29 Oct 2026, 20:45 UTC

    Changed 1

    • aquainput schema
      • No longer required: chainId status limit tokens priceRange feeBpsIn confirmed
  4. , Automatic check

    1 tool changed.

    Newly required parameter

    Details, 7 Oct 2026, 13:31 UTC

    Changed 1

    • orderbookinput schema
      • New parameters: action chain listMode makerAddress makerAsset takerAsset makingAmount takingAmount expirationSeconds orderHash signature orderData order limit cursor statuses sortBy execute
      • Now required: action chain
  5. , Automatic check

    Tracking started: 10 tools.

FAQ

Can I paste mcp.tc/i/1inch into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://api.1inch.com/mcp/protocol, so your client talks to 1inch directly. The quick link is for sharing: it opens this page, with setup steps for every client.

Does 1inch need an API key or a sign-in?

Not to start. 1inch works without signing in and offers sign-in for more access.

Is 1inch a remote or a local server?

Remote. 1inch hosts it at https://api.1inch.com/mcp/protocol, and it speaks Streamable HTTP. There’s nothing to install.

What can 1inch do?

It has 10 tools, including search, list_examples and get_example. You can search 1inch documentation and API reference, browse and read SDK example source code and get quotes and execute classic, Fusion and cross-chain swaps.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to 1inch?

Yes. 1inch’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read 1inch’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with 1inch. This page was built from 1inch’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.