Kilo Code logo

Kilo Code + GoldRush

By Kilo Code. Runs in IDE, Extension, Terminal, Cloud.

Kilo Code is an open-source coding agent available in VS Code, JetBrains, and CLI workflows. It combines specialist modes like Code, Architect, Ask, and Debug with project-scoped rules and MCP integrations. When connected to GoldRush, Kilo Code can inspect live blockchain data inside the editor, generate typed integrations, and automate feature or debugging work with onchain context.

Step 3: Add GoldRush MCP server to the project

{
  "mcpServers": {
    "goldrush": {
      "command": "npx",
      "args": ["-y", "@covalenthq/goldrush-mcp-server"],
      "env": {
        "GOLDRUSH_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Set up Kilo Code with GoldRush

  1. 1Install Kilo Code

    You can also install the JetBrains plugin or the optional CLI if that matches your workflow.

    code --install-extension kilocode.kilo-code
  2. 2Install GoldRush CLI

    Use the CLI to verify balances, transactions, and token data before automating them in Kilo.

    npm install -g @covalenthq/goldrush-cli
  3. 3Add GoldRush MCP server to the project

    Create .kilocode/mcp.json in the repository root so the whole team shares the same server config.

    {
      "mcpServers": {
        "goldrush": {
          "command": "npx",
          "args": ["-y", "@covalenthq/goldrush-mcp-server"],
          "env": {
            "GOLDRUSH_API_KEY": "YOUR_API_KEY"
          }
        }
      }
    }
  4. 4Add Kilo project rules

    Put GoldRush-specific guidance in .kilocode/rules/ so Kilo keeps using the right chains, pagination, and API key handling patterns.

  5. 5Start in the right mode

    Use Architect or Ask to scope the change, then switch to Code or Debug and ask: "Use GoldRush to add multi-chain wallet balances to this project"

Things to ask Kilo Code

Once GoldRush is connected, ask in plain words. Kilo Code picks the calls.

  • “Use GoldRush to add a typed balance service to this TypeScript app”
  • “Switch to Debug mode and find why this transaction query fails on Base”
  • “Create an Architect-mode plan for migrating our RPC data layer to GoldRush”
  • “Build a wallet holdings page with balances, transfers, and NFT sections”
  • “Generate a project rule that standardizes GoldRush API usage in this repo”
  • “Create a CLI task that exports token holders for a contract to CSV”
  • “Use the GoldRush MCP tools to validate the shape of this API response”
  • “Refactor this feature to use GoldRush instead of three separate chain providers”

Common workflows

  • Architect then implement

    1. Open Kilo in Architect mode and define the GoldRush integration plan
    2. Capture file-by-file changes and edge cases before writing code
    3. Switch to Code mode to implement the approved plan
    4. Use GoldRush tool calls to validate real response payloads while coding
  • Debug a failing Web3 feature

    1. Switch Kilo into Debug mode and point it at the broken blockchain flow
    2. Let it inspect the code and run targeted commands
    3. Use GoldRush tools to compare expected chain data against the app output
    4. Apply the fix and rerun the smallest useful verification steps
  • Ship a wallet dashboard

    1. Add the GoldRush MCP config at the project level
    2. Ask Kilo to build the client utility, route handler, and UI cards
    3. Use real GoldRush data to tune loading, formatting, and empty states
    4. Save the final guidance as a project rule for future blockchain work
  • Standardize team setup

    1. Commit .kilocode/mcp.json with the GoldRush server config
    2. Add project rules covering API key usage, supported chains, and pagination
    3. Ask Kilo to validate the setup from a clean repo checkout
    4. Share the repo so teammates get the same MCP behavior automatically

The 37 MCP tools Kilo Code can call

Each tool is a GoldRush API call or analytics query. Kilo Code reads the descriptions and picks the tools a request needs.

Cross-chain

  • multichain_balances

    Fetch spot and historical balances for an address on up to 10 EVM chains.

  • multichain_transactions

    Fetch paginated transactions for up to 10 addresses and 10 chains.

  • multichain_address_activity

    Locate chains an address is active on with a single API call.

Balances

  • token_balances

    Get native and ERC20 token balances with spot prices and metadata.

  • historical_token_balances

    Get token balances at a specific block height or date.

  • historical_portfolio_value

    Get daily portfolio balance broken down by token.

  • erc20_token_transfers

    Get transfer-in and transfer-out events with historical prices.

  • token_holders

    Get paginated current or historical holders of a token.

  • native_token_balance

    Get native token balance with current market value.

Transactions

  • transaction

    Fetch a single transaction with decoded log events.

  • transaction_summary

    Get earliest/latest transactions and count for a wallet.

  • transactions_for_address

    Get paginated transactions with decoded logs for an address.

  • transactions_for_block

    Get all transactions in a block with decoded events.

Bitcoin

  • bitcoin_hd_wallet_balances

    Get balances for child addresses from an HD wallet xpub key.

  • bitcoin_transactions

    Get full transaction history for a Bitcoin wallet.

  • bitcoin_non_hd_wallet_balances

    Get balance for a non-HD Bitcoin address.

NFTs

  • nft_for_address

    Get ERC721 and ERC1155 NFTs held by an address.

  • nft_check_ownership

    Verify NFT ownership within a collection.

  • nft_check_ownership_token_id

    Verify ownership of a specific NFT by token ID.

Pricing

  • historical_token_prices

    Get historical prices for ERC20 and native tokens.

  • pool_spot_prices

    Get spot prices for a Uniswap V2/V3 pool.

Security

  • token_approvals

    Get token approvals categorized by spender with risk levels.

Utility

  • gas_prices

    Get real-time gas estimates for low, medium, and high speeds.

  • block

    Fetch a single block with timestamp, tx count, and miner info.

  • block_heights

    Get block heights within a date range.

  • log_events_by_address

    Get event logs emitted from a contract address.

  • log_events_by_topic

    Get event logs by topic hash across all contracts.

  • resolve_address

    Resolve an ENS, RNS or Unstoppable Domains name to an address.

Protocol analytics

  • list_entities

    List every dataset with live analytics, with its metrics and dimensions.

  • search_catalog

    Find a dataset, metric, dimension or ticker before querying it.

  • get_metadata

    Read what a dataset's metrics measure, how they split and what they can't answer.

  • get_metric

    Get one metric of a dataset as a daily, weekly or monthly series.

  • get_metrics

    Get several metrics of one dataset in a single call.

  • get_breakdown

    Split a metric by a dimension such as chain, asset or market.

  • list_members

    List the values a dimension holds, ranked, to filter on one of them.

  • compare_entities

    Compare two to ten named datasets on one metric.

  • rank_entities

    Rank every dataset that serves a metric.

GoldRush Agent Skills

Agent Skills give your agent the context it needs for every GoldRush endpoint: parameters, response shapes and credit costs. One command installs all of them.

npx skills add covalenthq/goldrush-agent-skills
  • Foundational API

    REST endpoints for historical blockchain data. Balances, transactions, NFTs, token prices, security checks, cross-chain queries across 100+ networks.

  • x402

    Pay-per-request access without API keys. Agents pay with stablecoins using the HTTP 402 protocol. No accounts, no rate limits, no key management.

  • CLI

    Terminal-first blockchain data with native MCP support. 17 commands that work for both humans and AI agents.

Tips

  • Prefer project-level .kilocode/mcp.json for shared GoldRush setup and global config for personal experiments
  • Use Architect mode before large blockchain changes so Kilo does not jump into editing too early
  • Store repo-specific GoldRush conventions in .kilocode/rules/ to keep generations consistent
  • Allow only the tools you actually need. Narrow approvals reduce noise and accidental drift

Troubleshooting

Kilo is not picking up the GoldRush MCP server
Confirm the file is named .kilocode/mcp.json at the repo root and that the JSON is valid. If the server still does not appear, restart the extension so it reloads workspace-level MCP config.
Kilo cannot start npx from the editor
Make sure Node.js and npx are on the PATH used by VS Code or JetBrains. Launch the editor from a shell with the correct environment if necessary.
Tool approvals are slowing down repetitive GoldRush tasks
Keep the config project-scoped and use Kilo's allowed tool settings for safe, repeatable read-only GoldRush tools. Avoid blanket approval for write-heavy workflows.

More agents

  • Claude Code

    Anthropic's agentic coding tool that lives in your terminal and understands your codebase end-to-end.

  • Codex

    OpenAI's cloud-native coding agent that runs tasks in a sandboxed environment with full autonomy.

  • Gemini CLI

    Google's open-source terminal AI agent powered by Gemini models with built-in MCP support and a file-based skill system.

See every agent

Kilo Code and GoldRush FAQ

Yes. Kilo Code detects project-level MCP config in .kilocode/mcp.json and applies it to the current workspace. That makes it a good place to keep shared GoldRush configuration.