---
title: "MCP quickstart"
description: "Connect an AI client to the public ENS.Tools MCP endpoint."
canonical: "https://ens.tools/docs/mcp-quickstart"
section: "Developers"
stability: "beta"
version: "server 3.0 · 80 MCP tools · platform contract v1"
verifiedAt: "2026-07-29"
owner: "ENS.Tools Developer Platform"
---

# MCP quickstart

Connect an AI client to the public ENS.Tools MCP endpoint.

## Overview

Both MCP profiles are public, stateless Streamable HTTP. Start with the stable 25-tool lite profile for lower context use, or use the unchanged full profile when maximum compatibility matters.

## What this covers

- Lite endpoint: https://ens.tools/mcp-lite — 25 workflow tools plus search_tools.
- Full endpoint: https://ens.tools/mcp — the complete canonical catalogue.
- Current protocol revision: 2025-11-25.
- Compatible revisions: 2025-06-18, 2025-03-26, and 2024-11-05.
- Each runtime tools/list is deterministic; search_tools never mutates the lite list.
- No server-initiated SSE stream or issued session ID.

## Before you run this workflow

### Networks

- Ethereum mainnet for onchain plans
- HTTPS for MCP and public APIs

### Prerequisites

- JSON-RPC 2.0 client for MCP
- Read the live platform contract and tool schemas at runtime

### Wallet permissions

- MCP never receives private keys
- Prepared writes must be reviewed, signed, and broadcast by a separate wallet

### Expected result

- Structured JSON data or an unsigned plan with chain, target, calldata, value, and safety metadata

### Errors and recovery

- Call tools/list again after schema errors
- Back off after rate limits
- Simulate immediately before signing

## How to use it

1. **Choose a profile.** Use lite for common workflows and lower context use. Choose full when the client must call any tool directly.
2. **Initialize.** Negotiate a supported protocol revision and identify your client.
3. **Discover tools.** Call tools/list at runtime. On lite, search_tools returns matching full-catalogue schemas and the full endpoint for non-lite calls.
4. **Start with a read.** Try lookup_domain or get_agent_context before preparing any action.

## Examples

### Claude Code · Lite

```
claude mcp add ens-tools-lite --transport http https://ens.tools/mcp-lite
```

### Claude Code · Full

```
claude mcp add ens-tools --transport http https://ens.tools/mcp
```

### JSON configuration

```
{
  "mcpServers": {
    "ens-tools-lite": {
      "url": "https://ens.tools/mcp-lite",
      "transport": "streamable-http"
    }
  }
}
```

## Related guides

- [Complete MCP tool catalogue](https://ens.tools/docs/mcp-tools)
- [Unsigned transaction plans](https://ens.tools/docs/unsigned-plans)
- [Public APIs and manifests](https://ens.tools/docs/public-apis)