---
title: Overview
description: Use the Explorer MCP server to let AI agents inspect blocks,
  transactions, accounts, and on-chain ABIs.
source_url:
  html: https://thru.org/docs/api-ref/explorer-mcp/overview/
  md: https://thru.org/docs/api-ref/explorer-mcp/overview.md
---

# Overview

Use the Explorer MCP server when an agent needs live chain context from the explorer without scraping pages or guessing from stale context.

## Use This When

- you want an agent to inspect a block, transaction, account, or program ABI
- you want to debug deployed behavior against a specific network
- you want recent chain activity or account transaction history
- you want a tool-friendly way to search unknown `ta...`, `ts...`, or slot values

Choose another interface when:

- you need to send transactions or mutate chain state: use [CLI Reference](https://thru.org/docs/cli-reference/overview.md) or the relevant SDK
- you need a typed application integration: use the [gRPC API](https://thru.org/docs/api-ref/grpc/overview.md) or the appropriate SDK
- you are still deciding which docs to read: start with [Build with LLMs](https://thru.org/docs/getting-started/build-with-an-llm.md)

## Installation

Use the public Explorer MCP endpoint:

```text
https://scan.thru.org/api/mcp
```

### Claude Code

```bash
claude mcp add --transport http thru-explorer https://scan.thru.org/api/mcp
claude mcp list
```

### Codex

```bash
codex mcp add thruExplorer --url https://scan.thru.org/api/mcp
codex mcp list
```

## What It Exposes

The explorer app hosts an MCP server at `/api/mcp` and exposes these tools:

On the public explorer, the MCP endpoint is:

```text
https://scan.thru.org/api/mcp
```

- `get_block`
- `get_transaction`
- `get_account`
- `list_account_transactions`
- `list_recent_blocks`
- `list_recent_transactions`
- `search`
- `get_program_abi`

Every tool ultimately calls the explorer API with `format=toon`, which means the returned content is optimized for LLM consumption instead of browser rendering.

## RPC Override

The MCP endpoint accepts an optional `?rpc=<url>` query parameter.

Use that when:

- you are debugging a non-default network
- you want the same agent workflow against devnet, staging, or another explorer-compatible RPC endpoint

If the `rpc` value is missing or invalid, the explorer falls back to its default network.

## Start Here

- [Tools Reference](https://thru.org/docs/api-ref/explorer-mcp/tools-reference.md): See each Explorer MCP tool, its arguments, and when to use it.
- [Build with LLMs](https://thru.org/docs/getting-started/build-with-an-llm.md): Learn the recommended doc traversal and guardrails for agent-driven Thru development.