A
securityA
licenseA
qualityMCP Server for the Notion API, enabling Claude to interact with Notion workspaces.
Last updated -
18
329
825
MIT License
Enables containerized deployment of the Neo N3 MCP server, supporting isolated and consistent execution environments across different platforms.
Hosts the source code repository for the Neo N3 MCP server, enabling version control and collaboration on the codebase.
Supports comprehensive testing of the Neo N3 MCP server functionality, ensuring reliability of blockchain interactions.
Hosts the Neo N3 MCP documentation website, providing users with comprehensive guides and API references for interacting with the Neo N3 blockchain.
Provides tools for running the Neo N3 MCP server as an NPM package using Node.js, offering a simple way to access the blockchain functionality.
Allows installation and distribution of the Neo N3 MCP server as a package through the NPM registry, making it easily accessible to users.
Used for implementing the Neo N3 MCP server with strong typing, providing enhanced development experience and code reliability.
Neo N3 Model Context Protocol (MCP) v1.4.0
The Neo N3 Model Context Protocol (MCP) provides a standardized interface for AI agents and applications to interact with the Neo N3 blockchain. This server implementation aims for simplicity and ease of use, running directly via npx without requiring manual environment configuration for standard usage.
Adding the MCP to a Client (e.g., VS Code)
Configure your client to use the standard I/O server via npx:
Option A: VS Code User Settings (JSON)
Add the following to your User Settings JSON (Ctrl+Shift+P > Preferences: Open User Settings (JSON)):
{
"mcp": {
"servers": {
"neo-n3": { // You can choose any name
"command": "npx",
"args": [
"-y", // Auto-confirm npx installation/update
"@r3e/neo-n3-mcp"
]
}
}
}
}
Option B: Workspace Configuration (
Create a file named mcp.json inside the .vscode directory:
{
"servers": {
"neo-n3": { // You can choose any name
"command": "npx",
"args": [
"-y", // Auto-confirm npx installation/update
"@r3e/neo-n3-mcp"
]
}
}
}
Option C: Other Clients (e.g., Cursor)
Follow your client's instructions for adding an MCP server using a command. Provide the command npx and the arguments ["-y", "@r3e/neo-n3-mcp"].
Available Tools
For detailed parameters and examples, please refer to the
Configuration & Network
Tool | Description | Key Parameters |
| Get the currently configured network mode | None |
| Set the active network mode for subsequent calls |
: "mainnet_only", "testnet_only", or "both" |
Blockchain Information
Tool | Description | Key Parameters |
| Get current height and general network info |
|
| Get the current block height |
|
| Get block details by hash or height |
,
|
| Get transaction details by transaction ID |
,
|
| Check if a transaction is confirmed |
,
|
Wallet & Account Management
Tool | Description | Key Parameters |
| Create a new encrypted wallet file |
|
| Import existing wallet from WIF/private key |
,
|
| Get token balances for an address |
,
|
Asset Transfers
Tool | Description | Key Parameters |
| Send NEO, GAS, or other NEP-17 tokens |
,
,
,
,
,
|
| Estimate network and system fees for a transfer |
,
,
,
,
|
Smart Contract Interaction
Tool | Description | Key Parameters |
| List well-known contracts supported by the server |
|
| Get details (hash, methods) of a famous contract |
,
|
(replaces invoke_read/write) | Invoke a smart contract method (read or write) |
,
,
,
,
(for write),
(for write) |
NeoFS (Decentralized Storage)
Tool | Description | Key Parameters |
| Create a NeoFS storage container |
,
,
,
,
|
| List containers owned by an ID |
,
|
NeoBurger (Staking Service)
Tool | Description | Key Parameters |
| Deposit NEO to receive bNEO |
,
,
|
| Withdraw NEO by returning bNEO |
,
,
,
|
Example Requests
Get Blockchain Information
Request:
{
"name": "get_blockchain_info",
"arguments": {
"network": "mainnet"
}
}
Response:
{
"result": {
"height": 3456789,
"network": "mainnet"
}
}
Transfer Assets
Request:
{
"name": "transfer_assets",
"arguments": {
"network": "testnet",
"fromWIF": "YourSenderWalletWIF",
"toAddress": "NZNos2WqTbu5oCgyfss9kUJgBXJqhuYAaj",
"asset": "NEO",
"amount": "1",
"confirm": true
}
}
Response:
{
"result": {
"txid": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
"address": "NVbGwMfRQVudQCcChhCFwQRwSxr5tYEqQs",
"network": "testnet"
}
}
Error Handling
The MCP server returns standardized error responses:
{
"error": {
"code": "INVALID_PARAMETER",
"message": "Invalid network parameter. Must be 'mainnet' or 'testnet'."
}
}
Common error codes:
INVALID_PARAMETER: Missing or invalid parameterNETWORK_ERROR: Error connecting to Neo N3 nodeBLOCKCHAIN_ERROR: Error from the Neo N3 blockchainWALLET_ERROR: Error with wallet operationsCONTRACT_ERROR: Error with smart contract operationsUNAUTHORIZED: Operation not permittedINTERNAL_ERROR: Unexpected server error
Security Best Practices
WIF Handling: Be extremely cautious when providing Wallet Import Format (WIF) keys. Ensure the environment where the MCP server runs and the communication channel are secure. Consider running the server locally or within a trusted network. Avoid exposing the server publicly without robust authentication and transport security (HTTPS).
Store wallet files securely if using file-based approaches (though the current API seems WIF-based).
Use
confirm: truefor all state-changing operations (transfers, contract invocations) to ensure the transaction is processed by the network.Store wallet files securely with strong passwords
Use testnet for development and testing
Keep your Neo N3 MCP server updated to the latest version
HTTP Server
In addition to the MCP server, this package also provides an HTTP server that exposes the Neo N3 functionality through a RESTful API. The HTTP server is started automatically when you run the MCP server and listens on port 3002 by default.
HTTP Endpoints
Endpoint | Method | Description |
| GET | Get blockchain information |
| GET | Get the current block height |
| GET | Get block details by height |
| GET | Get transaction details by transaction ID |
| GET | Get token balances for an address |
| POST | Create a new wallet |
| GET | Get wallet information |
| POST | Import a wallet from WIF or private key |
| GET | Get the current network mode |
| POST | Invoke a smart contract method |
| POST | Deploy a new smart contract |
Example HTTP Requests
# Get blockchain information
curl http://localhost:3002/api/blockchain/info
# Get the current block height
curl http://localhost:3002/api/blockchain/height
# Get token balances for an address
curl http://localhost:3002/api/accounts/NZNos2WqTbu5oCgyfss9kUJgBXJqhuYAaj/balance
# Create a new wallet
curl -X POST -H "Content-Type: application/json" -d '{"password":"your-password"}' http://localhost:3002/api/wallets
# Get the current network mode
curl http://localhost:3002/api/network/mode
# Deploy a smart contract
curl -X POST -H "Content-Type: application/json" -d '{
"wif": "your-private-key-wif",
"script": "base64-encoded-contract-script",
"manifest": {
"name": "MyContract",
"groups": [],
"features": {},
"abi": {
"methods": [
{
"name": "myMethod",
"parameters": [],
"returnType": "Boolean",
"offset": 0
}
],
"events": []
},
"permissions": [
{
"contract": "*",
"methods": "*"
}
],
"trusts": [],
"supportedStandards": []
}
}' http://localhost:3002/api/contracts/deploy
Benefits of the HTTP Server
Accessibility: Provides access to Neo N3 blockchain functionality for applications that don't support the MCP protocol
Simplicity: Simple RESTful API that can be used with any HTTP client
Compatibility: Works with existing web applications and frameworks
Testing: Easier to test and debug than the MCP protocol
Testing
This package includes integration tests to verify the functionality of both the MCP server and the HTTP server.
Running Tests
# Build the project
npm run build
# Run the core functionality tests
npm run test:core
# Run the HTTP integration tests
npm run test:http
# Run the MCP integration tests
npm run test:integration
Resources
License
This project is licensed under the MIT License - see the LICENSE file for details.
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
Tools
An MCP server that provides seamless integration with the Neo N3 blockchain, allowing Claude to interact with blockchain data, manage wallets, transfer assets, and invoke smart contracts.
Related MCP Servers
- AsecurityAlicenseAqualityAn MCP server implementation that integrates Claude with Salesforce, enabling natural language interactions with Salesforce data and metadata for querying, modifying, and managing objects and records.Last updated -15545108MIT License
- -securityAlicense-qualityAn MCP server that allows accessing and managing ledger files through Claude by providing account listing, balance checking, and transaction register viewing capabilities.Last updated -3GPL 3.0
- AsecurityAlicenseAqualityAn MCP server implementation that integrates Claude with Salesforce, enabling natural language interactions with Salesforce data and metadata for querying, modifying, and managing objects and records.Last updated -78614MIT License