NEAR Contract Deployer MCP Server
Enables AI assistants to deploy, initialize, and upgrade NEAR smart contracts with cost estimation and status checks.
README
NEAR Contract Deployer MCP Server
An MCP (Model Context Protocol) server that enables AI assistants like Claude to deploy, initialize, and upgrade NEAR smart contracts.
Features
- deploy_contract: Deploy WASM smart contracts to NEAR accounts
- initialize_contract: Call initialization methods after deployment
- upgrade_contract: Upgrade existing contracts with new code
- get_deployment_status: Check if an account has a contract deployed
- estimate_deployment_cost: Calculate storage costs before deploying
Installation
npm install
npm run build
Configuration
Credentials
The server looks for NEAR credentials in these locations (in order):
~/.near-credentials/{network}/{account_id}.json~/.near/credentials/{network}/{account_id}.json./.near-credentials/{network}/{account_id}.json
You can also provide credentials directly via the private_key parameter.
Generate Credentials
# For testnet
near login --networkId testnet
# For mainnet
near login --networkId mainnet
Usage with Claude Desktop
Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"near-deploy": {
"command": "node",
"args": ["/path/to/mcp-near-deploy/dist/index.js"]
}
}
}
Example Conversations
Deploying a New Contract
User: Deploy my contract to testnet
Claude: I'll help you deploy your contract. First, let me estimate the costs.
Tool: estimate_deployment_cost
Args: {"wasm_path": "./target/wasm32-unknown-unknown/release/my_contract.wasm"}
💰 DEPLOYMENT COST ESTIMATE
📊 Cost Breakdown:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WASM Size: 156.32 KB (160,072 bytes)
Storage Cost: 1.600720 NEAR
Estimated Gas: 11 TGas
Total Estimate: ~1.65 NEAR
💡 Recommendation:
✅ Contract size is reasonable. Deployment should proceed smoothly.
Now let me deploy it:
Tool: deploy_contract
Args: {
"account_id": "mycontract.testnet",
"wasm_path": "./target/wasm32-unknown-unknown/release/my_contract.wasm",
"network": "testnet"
}
✅ CONTRACT DEPLOYED SUCCESSFULLY
📋 Deployment Details:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Contract ID: mycontract.testnet
Network: testnet
WASM Size: 156.32 KB
Storage Cost: 1.600720 NEAR
Transaction: 7abc123...
🔗 Explorer: https://explorer.testnet.near.org/transactions/7abc123...
📝 Next Steps:
1. Initialize the contract using initialize_contract()
2. Verify deployment with get_deployment_status()
Initializing a Contract
User: Initialize the contract with owner set to my account
Claude: I'll initialize your contract with the specified owner:
Tool: initialize_contract
Args: {
"contract_id": "mycontract.testnet",
"method_name": "new",
"args": {"owner_id": "yourname.testnet"},
"network": "testnet"
}
✅ CONTRACT INITIALIZED SUCCESSFULLY
📋 Initialization Details:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Contract ID: mycontract.testnet
Method: new
Arguments: {"owner_id": "yourname.testnet"}
Transaction: 8def456...
🔗 Explorer: https://explorer.testnet.near.org/transactions/8def456...
✨ The contract is now ready to use!
Checking Deployment Status
User: Is there a contract on wrap.near?
Claude: Let me check the deployment status:
Tool: get_deployment_status
Args: {"account_id": "wrap.near", "network": "mainnet"}
✅ CONTRACT IS DEPLOYED
📋 Deployment Status:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Contract ID: wrap.near
Network: mainnet
Code Hash: 4Fh7SHqU...
Storage Used: 3,456,789 bytes
Storage Cost: 34.567890 NEAR
Balance: 1,234.567890 NEAR
🔗 Explorer: https://explorer.near.org/accounts/wrap.near
✨ Contract is ready to interact with!
Upgrading a Contract
User: Upgrade my contract with the new version
Claude: I'll upgrade your contract with the new WASM and run the migration:
Tool: upgrade_contract
Args: {
"contract_id": "mycontract.testnet",
"wasm_path": "./target/wasm32-unknown-unknown/release/my_contract_v2.wasm",
"migrate_method": "migrate",
"network": "testnet"
}
✅ CONTRACT UPGRADED SUCCESSFULLY
📋 Upgrade Details:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Contract ID: mycontract.testnet
Network: testnet
New WASM Size: 162.45 KB
Storage Cost: 1.624500 NEAR
Deploy TX: 9ghi789...
Migration TX: 0jkl012...
🔗 Explorer: https://explorer.testnet.near.org/transactions/9ghi789...
✨ Migration completed successfully!
Cost Estimation
User: How much will it cost to deploy a 500KB contract?
Claude: Let me calculate the deployment cost:
Tool: estimate_deployment_cost
Args: {"wasm_size_bytes": 512000}
💰 DEPLOYMENT COST ESTIMATE
📊 Cost Breakdown:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WASM Size: 500.00 KB (512,000 bytes)
Storage Cost: 5.120000 NEAR
(5120000000000000000000000 yoctoNEAR)
Estimated Gas: 15 TGas
Gas Cost: ~0.001500 NEAR
─────────────────────────────────
Total Estimate: 5.121500 NEAR
💡 Recommendation:
💸 Storage cost is significant. Ensure account has sufficient NEAR balance.
📝 Notes:
• Storage costs are exact (1 byte = 0.00001 NEAR)
• Gas costs may vary based on network conditions
• Add ~10% buffer for safety
API Reference
deploy_contract
Deploy a WASM smart contract to a NEAR account.
| Parameter | Type | Required | Description |
|---|---|---|---|
| account_id | string | ✅ | NEAR account to deploy to |
| wasm_path | string | ❌* | Path to WASM file |
| wasm_base64 | string | ❌* | Base64-encoded WASM |
| network | string | ❌ | "mainnet" or "testnet" (default: testnet) |
| private_key | string | ❌ | Signing key (ed25519:xxx format) |
*Either wasm_path or wasm_base64 required
initialize_contract
Call an initialization method on a deployed contract.
| Parameter | Type | Required | Description |
|---|---|---|---|
| contract_id | string | ✅ | Contract account ID |
| method_name | string | ✅ | Init method name |
| args | object | ❌ | Method arguments |
| deposit | string | ❌ | NEAR to attach (e.g., "1.5") |
| gas | string | ❌ | Gas limit in TGas (default: 100) |
| network | string | ❌ | "mainnet" or "testnet" |
| private_key | string | ❌ | Signing key |
upgrade_contract
Upgrade an existing contract with new WASM code.
| Parameter | Type | Required | Description |
|---|---|---|---|
| contract_id | string | ✅ | Contract to upgrade |
| wasm_path | string | ❌* | Path to new WASM file |
| wasm_base64 | string | ❌* | Base64-encoded new WASM |
| migrate_method | string | ❌ | Migration method to call |
| migrate_args | object | ❌ | Migration arguments |
| network | string | ❌ | "mainnet" or "testnet" |
| private_key | string | ❌ | Signing key |
get_deployment_status
Check if an account has a contract deployed.
| Parameter | Type | Required | Description |
|---|---|---|---|
| account_id | string | ✅ | Account to check |
| network | string | ❌ | "mainnet" or "testnet" (default: mainnet) |
estimate_deployment_cost
Calculate storage costs for deployment.
| Parameter | Type | Required | Description |
|---|---|---|---|
| wasm_path | string | ❌* | Path to WASM file |
| wasm_base64 | string | ❌* | Base64-encoded WASM |
| wasm_size_bytes | number | ❌* | Direct size in bytes |
*At least one required
Networks
- Mainnet: Production network (
mainnet) - Testnet: Development network (
testnet)
Default network is testnet for safety.
Security Notes
- Never share or commit private keys
- Use environment variables or credential files for keys
- Test on testnet before mainnet deployments
- Review contract code before deploying
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 模型以安全和受控的方式获取实时的网络信息。