# Overview ## Arbitrum AI Hub 🚀🦾 The open-source toolkit that turns any AI coding assistant into a full-stack Arbitrum developer. **Arbitrum AI Hub** brings together two complementary projects — **MCP Tools** for blockchain actions and **Skills** for ecosystem knowledge — giving AI assistants the ability to not just *talk about* Arbitrum, but to actually *build on it* with up-to-date, verified information and direct on-chain execution. *** ### The Vision AI coding assistants are powerful, but they have two fundamental gaps when it comes to blockchain development: 1. **Knowledge gap** — Training data goes stale. SDK versions change, APIs get renamed, new features launch. An AI that suggests `stylus-sdk 0.6.0` when the current version is `0.9.0` doesn't just give a wrong answer — it gives you code that won't compile. 2. **Action gap** — Even with perfect knowledge, an AI can only *describe* how to check a balance or deploy a contract. It can't actually do it. Arbitrum AI Hub closes both gaps: | Gap | Solution | How | | ------------- | ------------------ | ---------------------------------------------------------------------------------- | | **Knowledge** | Arbitrum Skills | Up-to-date docs and source code, structured for efficient LLM consumption | | **Action** | Arbitrum MCP Tools | 30+ blockchain tools that let the AI query, deploy, analyze, and interact directly | The result: an AI assistant that gives **accurate answers** (not guesses), writes **compilable code** (not deprecated patterns), and **executes operations** (not just instructions) — all within the Arbitrum ecosystem. *** ### Important: Security & Responsibility > **By using Arbitrum AI Hub tools, you accept full responsibility for all actions performed through them.** > > Arbitrum MCP Tools give AI assistants the ability to **read blockchain data** and **execute real on-chain operations** — including contract deployments, transaction simulations, and protocol interactions. These operations may involve gas costs and are **irreversible once confirmed**. > > **Key principles:** > > * **Always review before confirming.** AI assistants may misinterpret intent or suggest incorrect parameters. Never approve an on-chain action without understanding what it does. > * **Protect your credentials.** Private keys and API keys stored in environment variables should be treated with the same care as passwords. Never share them in prompts, conversations, or public repositories. Use keystore files when possible. > * **Test on testnets first.** Before performing any operation on Arbitrum mainnet, verify the expected behavior on Arbitrum Sepolia. > * **Verify AI-generated code.** Arbitrum Skills provides reference documentation sourced from official repositories, but AI responses may still be incomplete or misinterpreted. Always cross-check critical information — especially smart contract code, configuration values, and deployment parameters — against the original source documentation. > * **Understand the tools.** Read-only tools (balance queries, block data, transaction history) carry no on-chain risk. Write tools (deploy, activate, cache, simulate) can execute real transactions. Know the difference. > > The MCP server runs **locally on your machine** and communicates only with the Alchemy API and Arbitrum RPC endpoints. No data is sent to third-party servers beyond these services. The authors make no guarantees about the correctness of AI-generated suggestions and are not liable for any financial losses or damages. *** ### What's Inside #### Arbitrum MCP Tools ⚡ **30+ Model Context Protocol tools** that give AI assistants hands-on access to the Arbitrum blockchain. Query balances, analyze transactions, deploy Stylus contracts, decode calldata, simulate transactions, and more — all through natural conversation. Supports **8 platforms**: Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, Gemini CLI, Antigravity, and OpenAI Codex. ```bash # Install in seconds npx arbitrum-mcp-tools install ``` * [Setup Guide](/docs/arbitrum-mcp-tools/setup-guide.md) * [Network MCP Tools](/docs/arbitrum-mcp-tools/network-mcp-tools.md) — Account analysis, chain data, batch operations, contract interaction, cross-chain, development * [Stylus MCP Tools](/docs/arbitrum-mcp-tools/stylus-mcp-tools.md) — Create, deploy, verify, activate, cache, debug Stylus contracts #### Arbitrum Skills 🧠 Structured, up-to-date Arbitrum knowledge — official documentation and smart contract source code from 3 key repositories — organized with a progressive disclosure architecture that keeps context usage minimal while giving the AI access to everything it needs. In a controlled [A/B test](/docs/arbitrum-skills/ab-test-results.md), Skills improved response quality by **66%** (5.3 → 8.8 out of 10) and eliminated all uncertainty flags, wrong versions, and deprecated API usage. ```bash # Install in seconds npx skills add utkucy/arbitrum-skills ``` * [Overview](/docs/arbitrum-skills/arbitrum-skills.md) — What Skills are and how they work * [Installation](/docs/arbitrum-skills/installation.md) — One-command or manual setup * [Skill Architecture](/docs/arbitrum-skills/skill-architecture.md) — Progressive disclosure design * [Topics Covered](/docs/arbitrum-skills/topics-covered.md) — 12 documentation categories + 3 smart contract repos * [A/B Test Results](/docs/arbitrum-skills/ab-test-results.md) — Quantified impact across 6 real-world questions * [Skill Generator](/docs/arbitrum-skills/skill-generator.md) — The CLI tool that builds the skill from source *** ### How They Work Together Skills and MCP Tools are designed to complement each other. Together, they cover the full development lifecycle: | Layer | Project | What It Does | Example | | ------------- | ------------------ | ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | | **Knowledge** | Arbitrum Skills | Accurate docs, correct code patterns, current API references | *"How do I write an ERC-20 in Stylus?"* → Compilable Rust code with correct `stylus-sdk 0.9.0` | | **Action** | Arbitrum MCP Tools | Direct blockchain operations — deploy, query, analyze | *"Deploy this contract to Arbitrum Sepolia"* → Actual deployment with tx hash | | **Together** | AI Hub | Full-stack AI-assisted development | *"Build and deploy a pausable ERC-20"* → Correct code + deployment + verification | Use **Skills** when you need the AI to understand Arbitrum concepts, write correct code, or provide accurate configuration. Use **MCP Tools** when you need the AI to interact with the blockchain directly. Use **both** for the complete experience. *** ### Quick Numbers | Metric | Value | | ---------------------------- | ---------------------------------------------------- | | MCP Tools | 30+ | | Supported platforms | 8 | | Skill quality improvement | +66% (A/B tested) | | Smart contract repos indexed | 3 (OpenZeppelin Stylus, Stylus SDK, Nitro Contracts) | *** ### Links | Project | Repository | | ------------------------ | ------------------------------------------------------------------------------------------------ | | Arbitrum MCP Tools | [github.com/utkucy/arbitrum-mcp-tools](https://github.com/utkucy/arbitrum-mcp-tools) | | Arbitrum Skills | [github.com/utkucy/arbitrum-skills](https://github.com/utkucy/arbitrum-skills) | | Arbitrum Skill Generator | [github.com/utkucy/arbitrum-skill-generator](https://github.com/utkucy/arbitrum-skill-generator) | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://arbitrum-ai-hub.gitbook.io/docs/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.