New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Blockrun Setup

by BlockRunAI in BlockRunAI/blockrun-mcp

A skill your agent uses when asked to install, add, configure, or set up the BlockRun MCP server (@blockrun/mcp) in Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, Grok or another MCP…

MITAuto-check passedAgent Workflows

Install Blockrun Setup

skills CLI
$ npx skills add BlockRunAI/blockrun-mcp --skill blockrun-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install BlockRunAI/blockrun-mcp blockrun-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/BlockRunAI/blockrun-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/blockrun-setup .claude/skills/blockrun-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
blockrun-setup
GitHub stars
392
Token cost
~2k tokens
SKILL.md length
909 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when asked to install, add, configure, or set up the BlockRun MCP server (@blockrun/mcp) in Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, Grok or another MCP…

  • Works in 5 steps: Check Node first → Install — pick the client → Restart, then prove it → …
  • Asked to install
  • SKILL.md covers 1. Check Node first, 2. Install — pick the client, 3. Restart, then prove it and 4. The wallet and how paying…, plus 2 more sections
  • Calls claude, npx and node; needs BLOCKRUN_API_KEY

What it does

Blockrun Setup is an agent skill from BlockRunAI/blockrun-mcp. Use when asked to install, add, configure, or set up the BlockRun MCP server (@blockrun/mcp) in Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, Grok or another MCP client — including first-run wallet creation, funding with USDC, choosing a tool profile, and proving the install works. Also use when a fresh install 'doesn't show up' or a user asks how to pay for calls.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol, Circle USDC and Homebrew. The repository describes itself as: Live data for AI agents — search, research, markets, crypto, X/Twitter. Pay-per-call via x402 micropayments. The licence is MIT.

When your agent uses it

  • Asked to install
  • Set up the BlockRun MCP server (@blockrun/mcp) in Claude Code
  • Another MCP client — including first-run wallet creation
  • Funding with USDC

Example prompts

  • “t show up”
  • “/blockrun-setup”

Requirements

  • Node.js
  • A credential in BLOCKRUN_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Check Node first
  2. Install — pick the client
  3. Restart, then prove it
  4. The wallet and how paying works
  5. Optional: install the agent skills

What it can do on your machine

Read from SKILL.md and the folder at commit a7a9b3c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • claude
    • npx
    • node
    • codex
    • nvm
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • user.blockrun.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • BLOCKRUN_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Blockrun Setup loads about 2k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 909 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from BlockRunAI/blockrun-mcp at commit a7a9b3c, republished under its MIT licence (© BlockRunAI). 909 words, ~2,004 tokens.

Download SKILL.mdSave it as .claude/skills/blockrun-setup/SKILL.md (or your agent's skills folder).
name
blockrun-setup
description
Use when asked to install, add, configure, or set up the BlockRun MCP server (@blockrun/mcp) in Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, Grok or another MCP client — including first-run wallet creation, funding with USDC, choosing a tool profile, and proving the install works. Also use when a fresh install 'doesn't show up' or a user asks how to pay for calls.
triggers
install blockrun, add blockrun mcp, set up blockrun, blockrun setup, claude mcp add blockrun, grok mcp add blockrun, blockrun unavailable, mcp server timed…

Installing BlockRun MCP

One command per client, then one tool call to see the wallet. Do it in this order; the PATH step is the one people skip and then spend an hour on.

1. Check Node first

bash
node -v      # must print v20.19 or newer
which npx

If node is from nvm, Homebrew, fnm, volta or asdf, assume the client's launcher will NOT find it. GUI-launched apps and Claude Code's MCP spawner do not source your shell profile. The fix is to pass your shell's PATH through at install time — not to pin nvm alias default, not to edit .zshrc, not to symlink node into /usr/local/bin.

2. Install — pick the client

Claude Code (recommended; -s user = every project):

bash
claude mcp add blockrun -s user -e PATH="$PATH" -- npx -y @blockrun/mcp@latest

The -- matters: it stops -y being parsed by claude mcp add. The -e PATH="$PATH" is the nvm/Homebrew fix from step 1; it is harmless on a system Node, so always include it.

Codex CLI (--env is Codex's equivalent of -e; config lands in ~/.codex/config.toml):

bash
codex mcp add blockrun --env PATH="$PATH" -- npx -y @blockrun/mcp@latest

Claude Desktop / Cursor / Windsurf — JSON, in the client's MCP config file:

json
{ "mcpServers": { "blockrun": { "command": "npx", "args": ["-y", "@blockrun/mcp@latest"] } } }
ClientFile
Claude Desktopclaude_desktop_config.json (Settings → Developer → Edit Config)
Cursor~/.cursor/mcp.json · Windows %APPDATA%\Cursor\mcp.json
Windsurf~/.codeium/windsurf/mcp_config.json · Linux ~/.config/.codeium/windsurf/mcp_config.json

For a JSON client with nvm/Homebrew Node, put the absolute npx path (which npx) in command — there is no -e PATH equivalent there.

Grok — raise the startup timeout BEFORE the first run. Grok waits startup_timeout_sec (default 30) for the server to answer, and a cold npx -y has to download this package and its dependencies first: measured 17s on a fast connection, 42-46s on a slower box. Lose that race and the UI says blockrun [unavailable] for an install that is merely still downloading. In ~/.grok/config.toml:

toml
[mcp_servers.blockrun]
command = "npx"
args = ["-y", "@blockrun/mcp@latest"]
enabled = true
startup_timeout_sec = 120

Or sidestep it: npm install -g @blockrun/mcp@latest then grok mcp add blockrun -- blockrun-mcp, which launches an already-installed binary. Only the first run is slow either way — npx caches by exact spec.

Optional flags (append after @latest): --profile trading|research|media|chat exposes a smaller tool set so the client loads fewer schemas. Omit for all <!-- br:mcp.tools -->19<!-- /br:mcp.tools --> tools.

Optional env (-e KEY=value on Claude Code, "env": {} in JSON): BLOCKRUN_CONFIRM_SPEND=on asks before each paid call on clients that support MCP elicitation; BLOCKRUN_CONFIRM_THRESHOLD=0.05 limits that to calls above $0.05; BLOCKRUN_BUDGET_LIMIT=5 hard-caps the process at $5.

3. Restart, then prove it

Restart the client — for Claude Code that means quit and relaunch claude; a running session does not pick up a new server. Then:

bash
claude mcp list        # expect:  blockrun: npx -y @blockrun/mcp@latest - ✓ Connected
claude mcp get blockrun  # confirms the scope and that PATH / any -e vars were captured

Inside the session, call blockrun_wallet with no arguments. It prints the wallet address, chain, and balance. That call is free and needs no funds — if it returns, the install works. Do not "test" with a paid tool.

Show full SKILL.md (488 more words)Show less

4. The wallet and how paying works

  • The server creates the wallets on first use: an EVM key in ~/.blockrun/.session and a Solana key in ~/.blockrun/.solana-session (both 0600). On a new install the funded one is the Solana key — that is where the USDC goes by default. On macOS/Linux both are also mirrored into the OS keychain, but the files stay authoritative unless the user opts into BLOCKRUN_KEYCHAIN=strict (then the keychain entries are the copies to export). Tell the user to back up both files — they are the only copies of the keys; BlockRun cannot recover them.
  • Payment is per call, and there are two ways to pay. Free tools (blockrun_wallet, blockrun_models, blockrun_dex, crypto blockrun_price, blockrun_chat mode:"free") need neither.

Wallet (the default — no account, no signup). USDC over x402. New installs default to Solana; an install that already has a Base wallet stays on Base.

  • blockrun_wallet action:"setup" shows the address and a QR. Send USDC (SPL) on Solana — Coinbase (pick "Solana"), Phantom, Solflare or Backpack. $5 covers hundreds of calls.
  • To use Base instead: blockrun_wallet action:"chain" chain:"base" then action:"setup", and send USDC on the Base network. No restart either way.
  • Only blockrun_defi, blockrun_modal and claude-* chat with thinking are Base-only; they say so rather than charging.

API key (for teams who cannot hand a wallet to an agent). Ask the user whether they want this before setting it up — it is a real account, not a local file.

  1. Sign in at https://user.blockrun.ai (Google).
  2. Mint a key at https://user.blockrun.ai/dashboard/keys — brk_live_…, shown once.
  3. Add credit at https://user.blockrun.ai/dashboard/credits (card or wire).
  4. Set BLOCKRUN_API_KEY in the client's MCP server config, e.g. claude mcp add blockrun -s user -e BLOCKRUN_API_KEY=brk_live_… -- npx -y @blockrun/mcp@latest
  5. Confirm with blockrun_wallet action:"status" — it must say "Paying with: BlockRun account API key".

In this mode no wallet is created or read, billing is post-hoc at exact usage (no per-call minimum, no transaction fee), and the ledger is https://user.blockrun.ai/dashboard/activity. Polymarket trading, wallet balances/top-ups and blockrun_realface action:"list" need a keypair and are unavailable; everything else works.

5. Optional: install the agent skills

The package ships 17 skills (which tool to use, worked examples, this one). Claude Code users: /plugin marketplace add BlockRunAI/blockrun-mcp. Everyone else:

bash
npx -y @blockrun/mcp@latest skills install              # → ./.claude/skills
npx -y @blockrun/mcp@latest skills install --global     # → ~/.claude/skills
npx -y @blockrun/mcp@latest skills install --to ~/.codex/skills

Common mistakes

MistakeWhy it bites
Omitting -e PATH="$PATH" on nvm/Homebrewspawn npx ENOENT / "Failed to connect" — the #1 support issue
Omitting -- before npx-y is eaten by claude mcp add; npx then prompts and hangs
Testing with a paid toolYou cannot tell "unfunded" from "broken". Use blockrun_wallet.
Sending USDC on Ethereum mainnetWrong network; the Base address is the same string but the funds are elsewhere. Say "Base".
Funding inside a sandboxed client (Claude Desktop / Cowork / Web bash)The wallet lives in the sandbox and dies with it. Test: if ~/.blockrun/.session is gone in the next session, you are sandboxed — install on the user's real machine.

If the install is done and something still fails, switch to the blockrun-debug skill.

© BlockRunAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/blockrun-setup of BlockRunAI/blockrun-mcp.

Open the folder on GitHubat commit a7a9b3c

Compare with similar skills

Blockrun Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Blockrun Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Blockrun Setup this skillBlockRunAI/blockrun-mcp392—~2kAutomated safety check: PassMIT
Install Lanes Desktoplanes-sh/app273—~1.6kAutomated safety check: PassNone
Gearcoleco Debuggingdrhelius/Gearcoleco141—~3.5kAutomated safety check: PassGPL-3.0
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official37k11 repos~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Install Lanes Desktop

    lanes-sh/app

    A skill your agent uses when installing, updating, or repairing the Lanes desktop app on a Mac, or when someone wants the Lanes issue board running for the first time.

    273 GitHub stars~1.6k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Gearcoleco Debugging

    drhelius/Gearcoleco

    Debug and trace ColecoVision and Super Game Module games using the Gearcoleco emulator MCP server.

    141 GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check passed

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    37k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Fastmcp Client CLI

    PrefectHQ/fastmcp

    Query and invoke tools on MCP servers using fastmcp list and fastmcp call.

    28k GitHub starsUsed in 1 repo~823 tokens
    Agent WorkflowsAuto-check passed

More from BlockRunAI/blockrun-mcp

All 17 skills in this repo

  • Signal To Trade Demo

    BlockRunAI/blockrun-mcp

    Prepare or run a polished BlockRun trading demo that discovers a current Polymarket market, combines live price, probability history, smart-money, and liquidity evidence into a balanced signal…

    392 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Blockrun

    BlockRunAI/blockrun-mcp

    Pay-per-call access to AI models, real-time data, media generation and multi-chain RPC over x402 micropayments (USDC on Base or Solana), or a BlockRun account API key.

    392 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Blockrun Debug

    BlockRunAI/blockrun-mcp

    A skill your agent uses when the BlockRun MCP server (@blockrun/mcp) is installed but misbehaving — 'Failed to connect', spawn npx ENOENT, blockrun missing from claude mcp list, HTTP 402 /…

    392 GitHub stars~3k tokensUpdated yesterday
    Auto-check passed

  • Blockrun Upgrade

    BlockRunAI/blockrun-mcp

    A skill your agent uses when the BlockRun MCP server prints 'Update available', when asked to upgrade, update, or pin @blockrun/mcp, when a fix 'should be in the new version' but the client still…

    392 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • Crypto Data

    BlockRunAI/blockrun-mcp

    A skill your agent uses for any crypto data question — token/coin prices, FX, commodities, stocks, OHLC history, DEX pairs and liquidity, DeFi TVL, yield/APY pools, or raw JSON-RPC against a chain…

    392 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

  • Decide

    BlockRunAI/blockrun-mcp

    A skill your agent uses when the user wants to try BlockRun's free typed-judgment endpoint (POST api.blockrun.ai/v1/decide, served by OpenJev) on their own data from Claude Code — yes/no, labelled…

    392 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Blockrun Setup

What does Blockrun Setup do?

A skill your agent uses when asked to install, add, configure, or set up the BlockRun MCP server (@blockrun/mcp) in Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, Grok or another MCP…. Blockrun Setup is an agent skill from BlockRunAI/blockrun-mcp. Use when asked to install, add, configure, or set up the BlockRun MCP server (@blockrun/mcp) in Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, Grok or another MCP client — including first-run wallet creation, funding with USDC, choosing a tool profile, and proving the install works.

When should I use Blockrun Setup?

Blockrun Setup fits situations like: asked to install; set up the BlockRun MCP server (@blockrun/mcp) in Claude Code; another MCP client — including first-run wallet creation; funding with USDC.

How do I install Blockrun Setup in Claude Code?

Run `npx skills add BlockRunAI/blockrun-mcp --skill blockrun-setup -a claude-code`. Or copy the skill folder (skills/blockrun-setup in BlockRunAI/blockrun-mcp) into .claude/skills/blockrun-setup in your project. Claude Code loads it when a task matches its description.

How do I install Blockrun Setup in Codex?

Run `npx skills add BlockRunAI/blockrun-mcp --skill blockrun-setup -a codex`. Or copy the skill folder (skills/blockrun-setup in BlockRunAI/blockrun-mcp) into .agents/skills/blockrun-setup in your project. Codex loads it when a task matches its description.

Can I use Blockrun Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BlockRunAI/blockrun-mcp --skill blockrun-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blockrun-setup, .gemini/skills/blockrun-setup, .github/skills/blockrun-setup and .opencode/skills/blockrun-setup in your project.

What does Blockrun Setup need to run?

Going by SKILL.md and its folder, Blockrun Setup needs the command-line tools its instructions call (claude, npx, node, codex, nvm and npm) and credentials named BLOCKRUN_API_KEY. Our summary lists: Node.js; A credential in BLOCKRUN_API_KEY.

Does Blockrun Setup access the network?

SKILL.md names 1 domain. As links in the text: user.blockrun.ai. This is read from the text; nothing was executed.

Is Blockrun Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Blockrun Setup use?

Blockrun Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Blockrun Setup use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Blockrun Setup?

Skills that share tags, products or a category with Blockrun Setup: Install Lanes Desktop (lanes-sh/app, 273 stars), Gearcoleco Debugging (drhelius/Gearcoleco, 141 stars), MCP Server Builder (anthropics/skills, 180k stars) and MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Blockrun Setup?

BlockRunAI (a GitHub organization) maintains it in BlockRunAI/blockrun-mcp, which has 392 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.

Source: BlockRunAI/blockrun-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.