near-contract
Enables Claude to interact with NEAR smart contracts: read state, call view methods, decode transactions, and explain contract interfaces.
README
MCP Server: NEAR Smart Contract Interaction
An MCP (Model Context Protocol) server that allows Claude to read NEAR smart contract state, call view methods, decode transactions, and understand contract interfaces.
Features
- Contract Metadata: Fetch code hash, storage usage, and detect implemented standards (NEP-141, NEP-171, etc.)
- View Method Calls: Call any read-only method on any NEAR contract
- Transaction Decoding: Decode and explain transaction actions, gas usage, and outcomes
- State Reading: Read raw contract state with optional key prefix filtering
- Interface Explanation: AI-friendly explanation of contract purpose and functions
Installation
npm install @near-mcp/contract-interaction
Or run directly:
npx @near-mcp/contract-interaction
Claude Desktop Configuration
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"near-contract": {
"command": "npx",
"args": ["@near-mcp/contract-interaction"]
}
}
}
Available Tools
1. get_contract_metadata
Fetches contract metadata including code hash, storage usage, and detected methods/standards.
Input:
{
"contract_id": "wrap.near",
"network": "mainnet"
}
Output:
{
"contract_id": "wrap.near",
"network": "mainnet",
"code_hash": "ABC123...",
"storage_usage_bytes": 12345,
"storage_usage_near": "0.12345 NEAR",
"detected_methods": ["ft_transfer", "ft_balance_of", "ft_metadata"],
"detected_standards": ["NEP-141 (Fungible Token Standard)"]
}
2. call_view_method
Calls a view (read-only) method on any NEAR smart contract.
Input:
{
"contract_id": "wrap.near",
"method_name": "ft_balance_of",
"args": { "account_id": "example.near" },
"network": "mainnet"
}
Output:
{
"contract_id": "wrap.near",
"method": "ft_balance_of",
"args": { "account_id": "example.near" },
"result": "1000000000000000000000000",
"blockHeight": 123456789,
"blockHash": "ABC...",
"logs": []
}
3. decode_transaction
Decodes and explains a NEAR transaction, including all actions and their effects.
Input:
{
"tx_hash": "ABC123...",
"sender_id": "example.near",
"network": "mainnet"
}
Output:
{
"hash": "ABC123...",
"signerId": "example.near",
"receiverId": "wrap.near",
"actions": [
{
"type": "FunctionCall",
"description": "Calls method \"ft_transfer\" with 0.0100 NEAR attached",
"details": {
"method_name": "ft_transfer",
"args_decoded": { "receiver_id": "bob.near", "amount": "1000000" },
"gas": 30000000000000,
"deposit": "1"
}
}
],
"outcome": {
"status": "Success",
"gasUsed": "2.5432 TGas",
"tokensBurned": "0.000254 NEAR"
}
}
4. get_contract_state
Reads raw contract state entries, optionally filtered by key prefix.
Input:
{
"contract_id": "example.near",
"key_prefix": "",
"network": "mainnet"
}
Output:
{
"contract_id": "example.near",
"network": "mainnet",
"total_entries": 42,
"state_entries": [
{
"key": "base64...",
"keyDecoded": "STATE",
"value": "base64...",
"valueDecoded": "{\"owner\": \"alice.near\"}"
}
],
"truncated": false
}
5. explain_contract_interface
Analyzes a contract and provides a human-readable explanation of its purpose and main functions.
Input:
{
"contract_id": "wrap.near",
"network": "mainnet"
}
Output:
{
"contract_id": "wrap.near",
"network": "mainnet",
"summary": "Wrapped NEAR (wNEAR) - A fungible token contract implementing the NEP-141 standard...",
"detected_standards": ["NEP-141 (Fungible Token Standard)", "NEP-145 (Storage Management)"],
"main_functions": {
"token_operations": ["ft_transfer", "ft_transfer_call"],
"queries": ["ft_balance_of", "ft_total_supply", "ft_metadata"],
"storage": ["storage_deposit", "storage_withdraw"]
},
"token_info": {
"name": "Wrapped NEAR",
"symbol": "wNEAR",
"decimals": 24
},
"example_usage": [
"Check token balance: call_view_method(\"wrap.near\", \"ft_balance_of\", {\"account_id\": \"user.near\"})",
"Get token info: call_view_method(\"wrap.near\", \"ft_metadata\", {})"
]
}
Supported Contract Standards
The server automatically detects contracts implementing:
- NEP-141: Fungible Token Standard
- NEP-171: Non-Fungible Token Standard
- NEP-145: Storage Management
- NEP-148: Fungible Token Metadata
Networks
Both mainnet and testnet are supported. Default is mainnet.
{ "network": "testnet" }
Development
# Install dependencies
npm install
# Build
npm run build
# Run locally
npm start
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 模型以安全和受控的方式获取实时的网络信息。