BitBadges Builder MCP Server
MCP server for building, auditing, and querying BitBadges collections via AI. Works with Claude Desktop and other MCP clients to generate transaction JSON for BitBadges tokens and collections (deprecated, use bitbadgesjs-sdk).
README
BitBadges Builder MCP Server
DEPRECATED — Moved to
bitbadgesjs-sdkThis standalone MCP server is deprecated and no longer maintained. The MCP builder tools have been folded into the main
bitbadgesjs-sdkpackage.What to use instead:
npm install -g bitbadgesjs-sdkThe SDK exposes the same MCP server plus a
builderCLI. See the docs:The standalone
bitbadges-builder-mcpnpm package and this repo are retained only for historical references and redirect purposes. Do not build against them — theaudit_collectionand related tools have been replaced byreview_collectionin the SDK, and no further updates will ship here.
MCP (Model Context Protocol) server for building, auditing, and querying BitBadges collections via AI. Works with Claude Desktop, Claude Code, Cursor, and any MCP-compatible client.
This MCP server does not sign or broadcast transactions. It builds transaction JSON that your application signs and broadcasts using your own wallet/signer.
Quick Start (DEPRECATED — use bitbadgesjs-sdk instead)
1. Install
# DEPRECATED: do not use
# npm install -g bitbadges-builder-mcp
# Use this instead:
npm install -g bitbadgesjs-sdk
2. Configure Your MCP Client
Claude Desktop (~/.config/claude/config.json):
{
"mcpServers": {
"bitbadges-builder": {
"command": "npx",
"args": ["bitbadges-builder-mcp"],
"env": {
"BITBADGES_API_KEY": "your-api-key-here"
}
}
}
}
Claude Code (.mcp.json in project root):
{
"mcpServers": {
"bitbadges-builder": {
"command": "npx",
"args": ["bitbadges-builder-mcp"],
"env": {
"BITBADGES_API_KEY": "your-api-key-here"
}
}
}
}
Cursor (Settings > MCP Servers > Add):
{
"command": "npx",
"args": ["bitbadges-builder-mcp"],
"env": {
"BITBADGES_API_KEY": "your-api-key-here"
}
}
3. Get an API Key
Get your free API key at: https://bitbadges.io/developer
The API key enables query tools (see below). Builder, validation, and knowledge tools work without an API key.
4. Start Building
"Create a 1000-supply NFT collection with 5 BADGE mint price"
"Build a USDC stablecoin vault with 100/day withdraw limit"
"Explain collection 123 to me"
"Audit this collection for security risks"
Environment Variables
| Variable | Required | Description |
|---|---|---|
BITBADGES_API_KEY |
For query tools | API key from https://bitbadges.io/developer |
No wallet, mnemonic, or private key is needed. This server builds transaction JSON only — your app handles signing and broadcasting.
How It Works
You describe what you want
↓
MCP builds transaction JSON (MsgUniversalUpdateCollection, MsgTransferTokens, etc.)
↓
review_collection catches security issues
↓
validate_transaction checks JSON format
↓
You sign with your wallet (MetaMask, Keplr, SDK, etc.) and broadcast
Available Tools
Validation & Analysis (no API key needed)
| Tool | Description |
|---|---|
validate_transaction |
Validate transaction JSON against critical rules |
audit_collection |
Audit for security risks, design flaws, supply inflation vectors |
explain_collection |
Generate human-readable markdown explanation of a collection |
Builders (no API key needed)
| Tool | Description |
|---|---|
build_token |
Universal token builder — any collection type from design axes |
build_smart_token |
IBC-backed smart token (stablecoin, wrapped asset) |
build_fungible_token |
ERC-20 style fungible token |
build_nft_collection |
NFT collection with minting config |
build_address_list |
On-chain address list (manager add/remove) |
build_claim |
Build claim JSON for the API (code-gated, password-gated, whitelist-gated, open) |
Components (no API key needed)
| Tool | Description |
|---|---|
generate_backing_address |
Compute deterministic IBC backing address from denom |
generate_approval |
Build approval structures by type |
generate_permissions |
Build permission presets |
generate_alias_path |
Build alias path for liquidity pools |
Utilities (no API key needed)
| Tool | Description |
|---|---|
convert_address |
Convert between ETH (0x) and BitBadges (bb1) formats |
validate_address |
Check if address is valid and detect chain type |
lookup_token_info |
Get token symbol, denom, decimals, backing address |
get_current_timestamp |
Get current time with optional offsets |
Knowledge (no API key needed)
| Tool | Description |
|---|---|
get_skill_instructions |
Get detailed instructions for a specific skill |
search_knowledge_base |
Search docs, learnings, recipes, error patterns |
diagnose_error |
Diagnose transaction errors and suggest fixes |
fetch_docs |
Fetch live documentation from docs.bitbadges.io |
Query Tools (require API key)
| Tool | Description |
|---|---|
query_collection |
Fetch collection details with field filtering |
query_balance |
Check token balance for an address |
simulate_transaction |
Dry-run transaction for validity and gas estimation |
verify_ownership |
Verify if address meets AND/OR/NOT ownership requirements |
search |
Search collections, accounts, and tokens |
search_plugins |
Search claim plugins or fetch by ID |
analyze_collection |
Query and produce structured collection analysis |
build_transfer |
Auto-query collection and build MsgTransferTokens |
build_dynamic_store |
Build dynamic store operations (create, update, set values) |
query_dynamic_store |
Query dynamic store values and metadata |
Resources
The MCP server exposes these resources that clients can read for context:
| Resource URI | Description |
|---|---|
bitbadges://rules/critical |
Critical rules for building transactions |
bitbadges://tokens/registry |
Token registry (symbol, denom, decimals) |
bitbadges://skills/all |
All skill instructions |
bitbadges://docs/concepts |
Conceptual documentation |
bitbadges://docs/examples |
Example transactions and patterns |
bitbadges://recipes/all |
Code recipes and decision matrices |
bitbadges://learnings/all |
Known gotchas, tips, and discoveries |
bitbadges://errors/patterns |
Error patterns and diagnostics |
bitbadges://workflows/all |
Step-by-step workflow chains |
bitbadges://schema/token-builder |
Token builder schema reference |
bitbadges://docs/frontend |
Reference frontend patterns |
Skills
Skills are detailed instruction sets loaded on-demand via get_skill_instructions(skillId):
| Skill ID | Description |
|---|---|
smart-token |
IBC-backed smart token with 1:1 backing |
fungible-token |
ERC-20 style fungible token |
nft-collection |
NFT collection design and minting |
subscription |
Time-dependent subscription token |
bb-402 |
Token-gated API access (HTTP 402 pattern) |
ai-criteria-gate |
AI agent as criteria verifier |
minting |
Minting strategies (public, manager, pricing) |
custom-2fa |
Custom 2FA requirements |
immutability |
Lock permissions and immutability patterns |
liquidity-pools |
Swappable tokens and trading |
payment-protocol |
Payment and pricing mechanisms |
verified |
Verified credential gates |
tradable |
Marketplace trading configuration |
address-list |
On-chain address list collections |
Supported Tokens
| Symbol | IBC Denom | Decimals |
|---|---|---|
| BADGE | ubadge (Cosmos) / abadge (EVM) | 9 / 18 |
| USDC | ibc/F082B65... | 6 |
| ATOM | ibc/A4DB47... | 6 |
| OSMO | ibc/ED07A3... | 6 |
Signing & Broadcasting (Your Responsibility)
This MCP server returns unsigned transaction JSON. To submit on-chain:
Browser (EVM wallet like MetaMask):
- Call EVM precompiles using ethers.js / viem with the transaction data
Browser (Cosmos wallet like Keplr):
- Use Keplr's
signDirectwith the transaction's SignDoc
Server-side (SDK):
import { GenericEvmAdapter, GenericCosmosAdapter } from 'bitbadgesjs-sdk';
// EVM path (recommended for server-side)
const adapter = GenericEvmAdapter.fromPrivateKey(key, 'https://evm-rpc.bitbadges.io');
// Cosmos path
const adapter = GenericCosmosAdapter.fromPrivateKey(key, 'bitbadges_50024-1');
// Sign and broadcast
const result = await adapter.signAndBroadcast(messages, fee, memo);
See BitBadges SDK docs for full signing documentation.
Related Tools
| Tool | Install | Description |
|---|---|---|
| BitBadges MCP (this) | npm i -g bitbadges-builder-mcp |
AI-powered collection builder, auditor, and explainer |
| BitBadges SDK | npm i bitbadgesjs-sdk |
TypeScript SDK for API, signing, address conversion |
| BitBadges API | https://bitbadges.io/developer | REST API for querying collections, balances, ownership |
| BitBadges Docs | https://docs.bitbadges.io | Full documentation |
| BitBadges Explorer | https://explorer.bitbadges.io | On-chain explorer |
Local Development
git clone https://github.com/bitbadges/bitbadges-builder-mcp.git
cd bitbadges-builder-mcp
npm install
npm run build
npm run dev # Run with tsx (hot reload)
npm test # Run tests
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。