> ## Documentation Index
> Fetch the complete documentation index at: https://docs.berachain.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Developer

> Use Berachain docs with AI assistants and MCP. Server URL, stack coverage, and how to ask for the right doc.

Use Berachain docs inside **AI assistants** and **MCP-compatible clients** (e.g. Cursor, Claude Code) by adding our MCP server. This page gives the server URL, what the docs cover, and how to ask so the AI uses the right content.

## MCP server

Add the Berachain docs MCP server so the AI can read the latest docs instead of relying on training data:

**URL:** [https://docs.berachain.com/mcp](https://docs.berachain.com/mcp)

Configure this in your MCP client; then the AI can query our pages, guides, and contract references directly.

## What we have examples for

The docs and [Community Developers](/build/guides/community-guides) catalog cover these parts of the stack. Each area has at least one guide with a **Guide** page (requirements, quick start, key files, raw README link for MCP).

| Area                      | What’s covered                                                                                          | Where                                                                                                                                                                   |
| ------------------------- | ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Wallet connections**    | Next.js + WalletConnect, ThirdWeb, Particle, RainbowKit, Expo                                           | [Community Developers](/build/guides/community-guides) → Wallet Connections                                                                                             |
| **Bridging**              | ERC20 to Berachain via LayerZero V2 OFT                                                                 | [Community Developers](/build/guides/community-guides) → Bridging                                                                                                       |
| **Smart contracts**       | Deploy (Ethers, Viem, Hardhat, Foundry), verify on Berascan, ERC20, ERC1155, upgradeable (OpenZeppelin) | [Community Developers](/build/guides/community-guides) → Smart Contract Deployment & Verification; [Verifying smart contracts](/build/guides/verifying-smart-contracts) |
| **Indexing & querying**   | Goldsky subgraph, Envio ERC20 indexer (+ The Graph, SubQuery linked)                                    | [Community Developers](/build/guides/community-guides) → Indexing and Querying                                                                                          |
| **Verifiable randomness** | Gelato VRF, Pyth Entropy (e.g. provably fair NFTs)                                                      | [Community Developers](/build/guides/community-guides) → Verifiable Randomness                                                                                          |
| **Oracles**               | Pyth price feeds (on-demand updates)                                                                    | [Community Developers](/build/guides/community-guides) → Oracles                                                                                                        |
| **Governance**            | Reward Vault proposals (BRIP-style)                                                                     | [Community Developers](/build/guides/community-guides) → Governance                                                                                                     |
| **Storage**               | Irys uploads paid with \$BERA (Node.js)                                                                 | [Community Developers](/build/guides/community-guides) → Storage                                                                                                        |

Core references (network, RPC, chain IDs, deployed addresses, ABIs): [Developer tools](/build/getting-started/developer-tools), [Deployed contracts](/build/getting-started/deployed-contracts). Protocol-specific: **Build** tab → BEX, Bend; **Nodes** tab for validators and staking pools.

## How to get the right doc

* **Contract addresses / ABIs / network config** → “Use the Berachain **Deployed contracts** page” or “What’s the RPC and chain ID for Berachain mainnet in the docs?”
* **Verify a contract** → “Follow the Berachain **Verifying smart contracts** guide” or “How do I verify with Hardhat/Forge on Berascan?”
* **A specific integration** → Name the stack and, if relevant, the guide: “Using the **Pyth Oracle** guide on Berachain, how do I call `updatePrice`?” or “From the **LayerZero OFT** guide, what’s the exact deploy order?”
* **Chain and network** → Say “Berachain mainnet” or “Berachain testnet (Bepolia)” so the AI picks the right RPC, faucet, and addresses.

The **Guides** dropdown (under Community Developers) lists each example; each guide page includes a raw README link so MCP can fetch the full repo README when needed.