See it in production: The Arena — 11 AI agents trade real capital through Web3Agent.
에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
CHAIN_ID=<value> CONFIRM_WRITES=<value> ETHERSCAN_API_KEY=<secret> ZEROX_API_KEY=<secret> COINGECKO_API_KEY=<secret> CCXT_CONFIG_PATH=<value> OWS_PASSPHRASE=<secret> claude mcp add io.github.apegurus-web3agent -- npx -y web3agent@0.6.2터미널에서 실행합니다.
{ "mcpServers": { "io.github.apegurus-web3agent": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "CHAIN_ID": "<value>", "CONFIRM_WRITES": "<value>", "ETHERSCAN_API_KEY": "<secret>", "ZEROX_API_KEY": "<secret>", "COINGECKO_API_KEY": "<secret>", "CCXT_CONFIG_PATH": "<value>", "OWS_PASSPHRASE": "<secret>" } } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
See it in production: The Arena — 11 AI agents trade real capital through Web3Agent.
Web3 MCP proxy for AI agents: DeFi swaps, bridges, market data, wallets, and gated writes.
MCP package:
web3agent| npm: https://www.npmjs.com/package/web3agent | GitHub: https://github.com/Apegurus/web3agent | Contact: [email protected]
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 [email protected].
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
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.
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
# Read-only live quote examples
node examples/swap.mjs --quote
node examples/bridge.mjs --quote
# Prepared external-wallet flows
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:
web3agent for app-owned agents and browser-wallet flowsGood first integration targets:
For protocol support or integration questions, open an issue at https://github.com/Apegurus/web3agent/issues or contact [email protected].
# Initialize for your host (run once)
npx web3agent init
# Start the MCP server
npx web3agent
# CLI fallback (for non-MCP hosts or scripting)
npx web3agent tools list --json
npx web3agent tools call resolve_token --input '{"symbol":"USDC","chainId":8453}' --json
npx web3agent doctor --json
# Local-only wallet secret flows (requires OWS_PASSPHRASE >= 12 chars and an interactive TTY)
OWS_PASSPHRASE='...' npx web3agent wallet generate
OWS_PASSPHRASE='...' npx web3agent wallet generate --mnemonic
OWS_PASSPHRASE='...' npx web3agent wallet activate --from-file ./secret.txt --type private-key
# Options
npx web3agent --help
npx web3agent --version
Wallet secret MCP tools are disabled by default so private keys and mnemonics do not enter an AI agent's inference context. Use the local web3agent wallet ... commands above for safe generation/import. If you explicitly accept the risk of agent-visible secrets, set WEB3AGENT_ALLOW_AGENT_VISIBLE_SECRETS=1 to re-enable the legacy MCP behavior.
wallet_deactivate only deactivates the current runtime session and returns to read-only ephemeral mode. Use confirmation-gated wallet_delete when you intentionally want to permanently remove persisted wallet material.
By default, web3agent keeps wallet secrets out of MCP tool responses and agent-visible inputs. The local web3agent wallet ... commands are the recommended way to generate or import private keys and mnemonics because they require an interactive TTY and refuse JSON secret output. Set WEB3AGENT_ALLOW_AGENT_VISIBLE_SECRETS=1 only if you explicitly accept that private keys or mnemonics can be sent through the MCP host and visible to the agent/inference provider.
For persisted server-side wallets, setting OWS_PASSPHRASE is not mandatory, but strongly recommended. When it is set on macOS/Linux and OWS is available, web3agent uses the Open Wallet Standard encrypted vault instead of the legacy filesystem-protected wallet store. The OWS spec minimum is 12 characters; web3agent warns on weak runtime passphrases and local wallet generation/import rejects shorter values. Use a 16+ character mixed passphrase in production. Configure it in the process that runs web3agent, whether that is npx web3agent as an MCP server or an app/service using createRuntime({ env: { OWS_PASSPHRASE: "..." } }).
If OWS_PASSPHRASE is missing, empty, OWS is unavailable, the platform is Windows, or OWS_FORCE_LEGACY=1 is set, web3agent falls back to legacy wallet storage protected by file permissions only. Migrating a legacy wallet.json leaves a plaintext wallet.json.migrated rollback backup; delete it after verifying OWS access. For multi-agent services, run separate wallet-using runtimes in separate processes until per-runtime wallet isolation is supported.
Use the package root for stable, typed EVM capabilities from another app or agent layer.
import {
getChain,
listChainTokens,
resolveCanonicalTokenSync,
resolveToken,
} from "web3agent";
const chain = getChain(8453);
const usdc = resolveCanonicalTokenSync({ symbol: "USDC", chainId: 8453 });
const tokens = listChainTokens({ chainId: 8453 });
const discovered = await resolveToken({ symbol: "DEGEN", chainId: 8453 });
console.log(
chain?.name,
usdc?.address,
discovered.address,
tokens.tokens.length,
);
Use resolveCanonicalToken() for well-known registry tokens and native-token aliases. Use resolveToken() when you also want DexScreener discovery fallback for long-tail assets.
Use the root API when your app owns the signer (e.g. a browser wallet via wagmi or AppKit).
import {
prepareOperation,
resumeOperation,
simulateTransaction,
} from "web3agent";
prepareOperation(...) returns the next wallet actions plus resumeStateresumeOperation(...) continues until the operation completesTransaction actions are only considered complete once you return a confirmed result:
{ type: "transaction", txHash: "0x...", status: "confirmed" }
resumeOperation() independently verifies the receipt before advancing.
Architecture notes: docs/architecture/browser-wallet-operations.md
Use web3agent/runtime when you need tool discovery, generic invocation, or upstream passthrough tools.
import { createRuntime } from "web3agent/runtime";
const runtime = await createRuntime();
try {
console.log(runtime.getHealth());
console.log(
runtime
.listTools()
.slice(0, 5)
.map((tool) => tool.name),
);
const result = await runtime.invokeTool("list_supported_chains");
console.log(result.structuredContent);
} finally {
await runtime.shutdown();
}
See WEB3_CONTEXT.md for the full environment variable reference.
For authenticated exchange access via CCXT tools, set CCXT_CONFIG_PATH to a JSON file containing named accounts and exchange credentials.
MIT
Web3 MCP proxy for AI agents: DeFi swaps, bridges, market data, wallets, and gated writes.
{ "mcpServers": { "io.github.apegurus-web3agent": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "CHAIN_ID": "<value>", "CONFIRM_WRITES": "<value>", "ETHERSCAN_API_KEY": "<secret>", "ZEROX_API_KEY": "<secret>", "COINGECKO_API_KEY": "<secret>", "CCXT_CONFIG_PATH": "<value>", "OWS_PASSPHRASE": "<secret>" } } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
게시자가 등록한 환경 변수: CHAIN_ID, CONFIRM_WRITES, ETHERSCAN_API_KEY, ZEROX_API_KEY, COINGECKO_API_KEY, CCXT_CONFIG_PATH, OWS_PASSPHRASE.
Web3agent은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-08. Web3 MCP proxy for AI agents: DeFi swaps, bridges, market data, wallets, and gated writes.