Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Web3 MCP proxy for AI agents: DeFi swaps, bridges, market data, wallets, and gated writes.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CHAIN_ID, CONFIRM_WRITES, ETHERSCAN_API_KEY, ZEROX_API_KEY, COINGECKO_API_KEY, CCXT_CONFIG_PATH, OWS_PASSPHRASEValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"web3agent": {
"command": "npx",
"args": [
"-y",
"web3agent",
"web3agent"
],
"env": {
"CHAIN_ID": "your-value",
"CONFIRM_WRITES": "your-value",
"ETHERSCAN_API_KEY": "your-value",
"ZEROX_API_KEY": "your-value",
"COINGECKO_API_KEY": "your-value",
"CCXT_CONFIG_PATH": "your-value",
"OWS_PASSPHRASE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add web3agent --env CHAIN_ID=your-value --env CONFIRM_WRITES=your-value --env ETHERSCAN_API_KEY=your-value --env ZEROX_API_KEY=your-value --env COINGECKO_API_KEY=your-value --env CCXT_CONFIG_PATH=your-value --env OWS_PASSPHRASE=your-value -- npx -y web3agent web3agentFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"web3agent": {
"command": "npx",
"args": [
"-y",
"web3agent",
"web3agent"
],
"env": {
"CHAIN_ID": "your-value",
"CONFIRM_WRITES": "your-value",
"ETHERSCAN_API_KEY": "your-value",
"ZEROX_API_KEY": "your-value",
"COINGECKO_API_KEY": "your-value",
"CCXT_CONFIG_PATH": "your-value",
"OWS_PASSPHRASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"web3agent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"web3agent",
"web3agent"
],
"env": {
"CHAIN_ID": "your-value",
"CONFIRM_WRITES": "your-value",
"ETHERSCAN_API_KEY": "your-value",
"ZEROX_API_KEY": "your-value",
"COINGECKO_API_KEY": "your-value",
"CCXT_CONFIG_PATH": "your-value",
"OWS_PASSPHRASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
CHAIN_ID envCONFIRM_WRITES envCCXT_CONFIG_PATH envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account Apegurus, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ETHERSCAN_API_KEY, ZEROX_API_KEY, COINGECKO_API_KEY, OWS_PASSPHRASE
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.6.2) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
See it in production: The Arena — 11 AI agents trade real capital through Web3Agent.
MCP package:
web3agent| npm: https://www.npmjs.com/package/web3agent | GitHub: https://github.com/Apegurus/web3agent | Contact:
Links: Website · GitHub · npm · Smithery · The Arena · X / @Web3AgentFi
Give your AI agent EVM execution and DeFi tooling: swaps, bridges, limit and trigger orders, exchange trading, market data, research, wallet management. 190+ MCP tools. One install.
Works out of the box with Claude Code, Cursor, Windsurf, OpenCode, and Codex. Self-custodial. By default, write operations go through a confirmation queue: nothing executes without your approval unless you explicitly disable confirmations.
EVM execution is a solved problem. Stop rebuilding it. Plug in and ship.
Once installed, your AI agent can execute real DeFi operations in plain language:
Common flows avoid ABI handling and transaction building. Generic contract reads and writes are available when you provide or register an ABI, or when explorer ABI lookup is available. The agent handles routing, transaction preparation, and the confirmation queue. You approve, it executes.
npx web3agent init
This detects Claude Code, Cursor, Windsurf, OpenCode, or Codex and configures the MCP server automatically. Restart your host, then ask:
What Web3 tools do you have available, and what chain are you configured for?
For any other MCP-capable host, configure a stdio server that runs:
npx web3agent
The generic MCP config shape is:
{
"web3agent": { "type": "stdio", "command": "npx", "args": ["web3agent"] } }
Writes are confirmation-gated by default, and wallet secrets are not exposed through MCP unless explicitly enabled.
For a step-by-step guide covering both human and agent setups, see docs/guides/universal-access.md.
Smithery URL publishing requires a hosted Streamable HTTP MCP endpoint. Web3Agent is distributed as a local stdio/npm server, so Smithery distribution uses an MCPB bundle instead:
pnpm run mcpb:check
smithery mcp publish dist/web3agent.mcpb -n Apegurus/web3agent
The generated MCPB is a thin local bundle that launches the published npm package with npm exec --package web3agent@0.6.2.
npx web3agent init auto-configures Claude Code, Cursor, Windsurf, OpenCode, or Codex. No manual config edits for supported hosts.Use these after installation to get to value quickly:
List the supported chains and tell me which Web3 tools are safest to try first.
Resolve USDC, WETH, and DEGEN on Base. Show token addresses and decimals.
Quote swapping 0.01 ETH to USDC on Base, but do not execute anything.
Show yield opportunities above 5% APY and explain the main protocol risks.
Explain this wallet's recent activity on Base: 0x0000000000000000000000000000000000000000
| Host | Config location |
|---|---|
| Claude Code | ~/.claude/mcp.json |
| Cursor | .cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| OpenCode | .opencode/config.json |
| Codex | .codex/config.toml |
| OpenClaw | agent-mediated self-install via canonical guide |
Basic EVM operations use viem's chain registry and can target any viem-supported EVM chain when RPC access is available.
Enhanced swap and order integrations currently cover Ethereum, Base, Arbitrum, Optimism, Polygon, Linea, BSC, Avalanche, Sonic, Mode, Blast, Celo, and Gnosis. Token resolution, explorer, LI.FI, and market/research tools have provider-specific coverage; LI.FI bridge quotes and execution support 20+ chains through LI.FI's own chain list.
Default: Base (8453). Override with the CHAIN_ID env var or pass chainId per call.
| Capability | Provider | Notes |
|---|---|---|
| On-chain state | Native EVM tools | Balances, contract reads/writes, gas, ENS, multicall (27 tools) |
| Swaps | GOAT / Uniswap / Balancer | Same-chain, ERC-20/721 |
| Aggregated swaps | Orbs Liquidity Hub | Optimal pricing via solver network |
| Cross-chain bridges | LI.FI | 20+ chains |
| Lending | GOAT SDK / protocol integrations | Aave, Morpho, and major money-market surfaces where supported |
| Advanced orders | Orbs | Spot market, limit, TWAP, stop-loss, take-profit, delayed orders |
| Exchange trading | CCXT | Public/private access across 100+ exchanges (6 tools) |
| Block explorer | Blockscout + Etherscan | Address info, tx history, NFTs, contract ABIs, network stats (35 tools) |
| Market data | DefiLlama / CoinGecko / Binance | TVL, prices, DEX volume, stablecoin stats, sentiment (20 tools) |
| Research | DefiLlama / on-chain | Contract security, yield analysis, whale tracking, governance (13 tools) |
| Token resolution | Built-in registry + DexScreener | Symbol-to-address, long-tail assets |
| Wallet management | web3agent + Open Wallet Standard | CLI/MCP lifecycle, encrypted OWS vault when configured, legacy fallback |
| Confirmation queue | Built-in | Write operations require explicit approval by default |
| Agent protocols | aGDP / ACP / ERC-8183 / x402 / ERC-8004 | Agent marketplace, cooperation, payments |
| Price data | CoinGecko | Requires COINGECKO_API_KEY |
| 0x swaps | 0x | Requires ZEROX_API_KEY |
npx web3agent create
Scaffolds a ready-to-run project from one of three bundled templates:
Each starter uses the same web3agent lifecycle surfaces as MCP and CLI.
Root examples are included in the npm package:
# Safe import-only previews
node examples/swap.mjs node examples/bridge.mjs
node examples/swap.mjs --quote node examples/bridge.mjs --quote
WEB3AGENT_EXAMPLE_ACCOUNT=0x... node examples/swap.mjs --prepare WEB3AGENT_EXAMPLE_ACCOUNT=0x... node examples/bridge.mjs --prepare
The examples default to small USDC-denominated flows and only prepare wallet actions when you pass --prepare.
import { prepareOperation, resolveCanonicalTokenSync } from "web3agent";
const chainId = 8453; const usdc = resolveCanonicalTokenSync({ chainId, symbol: "USDC" }); const weth = resolveCanonicalTokenSync({ chainId, symbol: "WETH" });
if (!usdc || !weth) throw new Error("Missing canonical token");
const intent = await prepareOperation({ integration: "orbs", kind: "swap", account: "0xYourWallet", chainId, fromToken: usdc.address, toToken: weth.address, fromAmount: "10000000", slippagePct: 0.5, });
console.log(intent.nextActions);
import { prepareOperation, resolveCanonicalTokenSync } from "web3agent";
const fromChainId = 1; const toChainId = 42161; const from = resolveCanonicalTokenSync({ chainId: fromChainId, symbol: "USDC" }); const to = resolveCanonicalTokenSync({ chainId: toChainId, symbol: "USDC" });
if (!from || !to) throw new Error("Missing canonical token");
const bridge = await prepareOperation({ integration: "lifi", kind: "bridge", account: "0xYourWallet", fromChainId, toChainId, fromToken: from.address, toToken: to.address, fromAmount: "1000000", });
console.log(bridge.nextActions);
import { getAddressInfo, getTransactionHistory, listSupportedChains } from "web3agent";
const address = "0x0000000000000000000000000000000000000000"; const chainId = 8453;
const [chains, info, history] = await Promise.all([ listSupportedChains(), getAddressInfo({ address, chainId }), getTransactionHistory({ address, chainId, pageSize: 5 }), ]);
console.log({ supportedChains: chains.chains.length, wallet: info, recentTransactions: history.transactions, });
Use web3agent when you want AI agents to discover or interact with your protocol without every team rebuilding wallet, chain, token, quote, explorer, and confirmation plumbing.
Integration surfaces:
-
Only the beginning is shown; read the rest in the repo