> For the complete documentation index, see [llms.txt](https://chaincontext.gitbook.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chaincontext.gitbook.io/help-center/getting-started.md).

# Getting Started

{% hint style="success" %}
In under 5 minutes you'll have a live MCP endpoint that AI agents like Claude can call to interact with your smart contracts.
{% endhint %}

## Quick Start

### 1. Create an account

Sign up at [app.chaincontext.dev](https://app.chaincontext.dev/auth/register). You can use email/password, Google, or GitHub.

### 2. Create a team and project

The onboarding wizard walks you through:

* **Name your team** — teams group projects and members together
* **Pick a recipe** (optional) — pre-built templates for common use cases like DeFi yield monitoring, DEX trading, or governance tracking
* **Create your project** — choose a name and slug (e.g., `my-defi-tools` → `my-defi-tools.chaincontext.dev`)

### 3. Import a contract

Paste a smart contract address and select the networks you want to support. ChainContext automatically fetches the ABI from Etherscan (EVM) or the IDL from on-chain (Solana Anchor programs).

* **EVM:** Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche, BNB Chain + testnets
* **Solana:** Mainnet and Devnet
* **Proxy contracts:** enable "Resolve proxy" to auto-detect EIP-1967 implementation ABIs

### 4. Build your tools

Use the visual block builder to create MCP tools from your contract's functions:

* **Start from a recipe** — one click applies pre-configured tools, prompts, and resources
* **Build from scratch** — drag and drop blocks: contract calls, data sources, transforms, HTTP requests, and response formatters
* **Write tools** — generate unsigned transactions with WalletConnect URIs for wallet signing

### 5. Deploy

Click **Deploy** in your project dashboard. Your MCP server goes live at:

```
https://{your-slug}.chaincontext.dev/mcp
```

Supports both Streamable HTTP and SSE transports.

### 6. Connect an AI client

Add your server to any MCP-compatible client:

{% tabs %}
{% tab title="Claude Desktop" %}
Edit `claude_desktop_config.json`:

* **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
* **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "my-project": {
      "url": "https://my-project.chaincontext.dev/mcp"
    }
  }
}
```

Restart Claude Desktop after editing.
{% endtab %}

{% tab title="Cursor" %}
Edit `.cursor/mcp.json` in your project root:

```json
{
  "mcpServers": {
    "my-project": {
      "url": "https://my-project.chaincontext.dev/mcp"
    }
  }
}
```

Cursor auto-detects config changes.
{% endtab %}

{% tab title="Windsurf" %}
Edit `~/.codeium/windsurf/mcp_config.json`:

```json
{
  "mcpServers": {
    "my-project": {
      "url": "https://my-project.chaincontext.dev/mcp"
    }
  }
}
```

{% endtab %}
{% endtabs %}

That's it — your AI agent can now call your smart contract functions as MCP tools.

## What's next?

{% content-ref url="/pages/6N7Xysna3qRNO61loRF6" %}
[Core Concepts](/help-center/core-concepts.md)
{% endcontent-ref %}

{% content-ref url="/pages/T9HBXpJG2GdYW4QrADgX" %}
[Building Tools](/help-center/building/building-tools.md)
{% endcontent-ref %}

{% content-ref url="/pages/LkVRBt5E9mZRN8VNSDeD" %}
[MCP Server Recipes](/help-center/building/recipes.md)
{% endcontent-ref %}