Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | No | The absolute path to the ARBuilder repository directory to allow Python to locate the source modules. | |
| DEFAULT_MODEL | No | The default LLM model to use for generation. | deepseek/deepseek-v3.2 |
| NVIDIA_API_KEY | Yes | Your NVIDIA API key, used for the cross-encoder reranking functionality. | |
| DEFAULT_EMBEDDING | No | The default embedding model to use for vector search. | baai/bge-m3 |
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key, used for generating embeddings and LLM calls. | |
| DEFAULT_CROSS_ENCODER | No | The default cross-encoder model to use for reranking search results. | nvidia/llama-3.2-nv-rerankqa-1b-v2 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stylus_context | Retrieve relevant Stylus documentation and code examples from the knowledge base. Use this to find examples, patterns, and documentation for Stylus development. Supports version-aware search to prioritize results matching your SDK version. |
| generate_stylus_code | Generate Stylus/Rust smart contract code based on requirements. Uses RAG context to provide relevant examples. Supports version-aware generation for different stylus-sdk versions. |
| ask_stylus | Ask questions about Stylus development, get concept explanations, or debug code issues. Supports version-specific guidance. |
| generate_tests | Generate test cases for Stylus smart contracts. |
| get_workflow | Get structured workflow information for Stylus development. Returns step-by-step commands for build, deploy, test operations. Use this when the user needs guidance on development workflows. |
| validate_stylus_code | Compile-check Stylus Rust code via cargo check and return structured errors with Stylus-specific fix guidance. Use AFTER generating code to verify correctness. Returns error codes, line numbers, and suggested fixes. Requires Docker. |
| generate_bridge_code | Generate TypeScript code for Arbitrum asset bridging using the Arbitrum SDK. Supports ETH/ERC20 bridging L1<->L2 and L1->L3. |
| generate_messaging_code | Generate TypeScript code for Arbitrum cross-chain messaging. Supports L1->L2 retryable tickets and L2->L1 messages. |
| ask_bridging | Answer questions about Arbitrum bridging and cross-chain messaging patterns. |
| generate_backend | Generate TypeScript backend code for Arbitrum dApps. Supports NestJS and Express with viem integration. |
| generate_frontend | Generate Next.js frontend code for Arbitrum dApps. Uses wagmi v2 and RainbowKit. |
| generate_indexer | Generate subgraph code for indexing Arbitrum contracts with The Graph. |
| generate_oracle | Generate Chainlink oracle integration code for Arbitrum dApps. |
| orchestrate_dapp | Scaffold a template-based dApp monorepo with starter components (contract, backend, frontend, indexer, oracle). |
| generate_orbit_config | Generate configuration code for Orbit chain deployment. Supports chain config, AnyTrust DAC setup, and custom gas token configuration using @arbitrum/orbit-sdk. |
| generate_orbit_deployment | Generate deployment code for Orbit chains. Supports rollup deployment, token bridge deployment, and full deployment with validators and batch posters. |
| generate_validator_setup | Generate code for managing Orbit chain validators, batch posters, and AnyTrust DAC keysets. |
| ask_orbit | Answer questions about Arbitrum Orbit chain deployment, configuration, validators, AnyTrust, custom gas tokens, and governance. |
| orchestrate_orbit | Scaffold a complete Orbit chain deployment project with all scripts for chain config, rollup deployment, token bridge, validator management, and node configuration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build-contract | Step-by-step guidance for building a Stylus contract |
| deploy-contract | Step-by-step guidance for deploying a Stylus contract |
| debug-error | Diagnose and fix Stylus development errors |
| optimize-gas | Optimize contract for gas efficiency and size |
| generate-contract | Generate a new Stylus contract from requirements |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Stylus CLI Commands | Complete reference for cargo-stylus CLI commands and options |
| Build Workflow | Step-by-step workflow for building Stylus contracts |
| Deploy Workflow | Step-by-step workflow for deploying Stylus contracts |
| Test Workflow | Step-by-step workflow for testing Stylus contracts |
| Network Configurations | Arbitrum network endpoints and chain configurations |
| Stylus Coding Rules | Coding guidelines and patterns for Stylus smart contracts |
| Arbitrum SDK Rules | Coding guidelines for Arbitrum SDK bridging and messaging |
| Backend Coding Rules | Guidelines for NestJS/Express Web3 backend development |
| Frontend Coding Rules | Guidelines for Next.js + wagmi + RainbowKit frontend development |
| Indexer Coding Rules | Guidelines for The Graph subgraph development |
| Oracle Coding Rules | Guidelines for Chainlink oracle integration |
| Orbit Chain Rules | Rules and constraints for Arbitrum Orbit chain deployment and configuration |