NEAR Protocol Full-Featured MCP Server

What is NEAR Protocol Full-Featured MCP Server?

This server implements a Model Context Protocol (MCP) interface for the NEAR Protocol blockchain. It allows LLMs connected via MCP clients (like Claude Desktop) to query blockchain data and execute transactions using a pre-configured NEAR account. It is intended for local development and testing only.

How to use NEAR Protocol Full-Featured MCP Server?

Install the package via npm, create a .env file with your mnemonic seed phrase, network ID, and optional RPC URL, then build and run the server with npm start or node build/index.js. Connect an MCP client by editing its configuration (e.g., Claude Desktop’s claude_desktop_config.json) to point to the compiled build/index.js and pass the environment variables.

Key features of NEAR Protocol Full-Featured MCP Server

• Retrieve account balances, details, and raw contract state.
• Create sub-accounts, delete accounts, and transfer tokens.
• Call smart contract methods (view and change) with gas/deposit.
• Deploy WASM contracts and execute batch atomic actions.
• Manage access keys (list, add full or function-call keys, delete).
• Verify message signatures against a given public key.

Use cases of NEAR Protocol Full-Featured MCP Server

• An LLM assistant checking a user’s NEAR account balance or storage usage.
• Automating testnet token transfers and contract deployments from a development account.
• Managing sub-account creation and key rotation via natural language commands.
• Performing batch operations like transferring tokens and calling a contract in one transaction.

FAQ from NEAR Protocol Full-Featured MCP Server

Is this server safe for production use?

No. The server stores the private key in a plaintext environment variable (MNEMONIC). Use it only for local development and testing with accounts that do not hold significant value.

What are the prerequisites to run the server?

You need Node.js 16 or higher, npm, a NEAR account (or just a seed phrase), and knowledge of the target network (testnet or mainnet). An MCP client such as Claude Desktop is optional.

How do I connect the server to Claude Desktop?

Edit the Claude Desktop configuration file (claude_desktop_config.json) to add an entry under mcpServers with the command node, the absolute path to build/index.js, and the required environment variables (MNEMONIC and NEAR_NETWORK_ID). Restart Claude Desktop.

What happens when no account ID is provided to a tool?

The server will use its own account (derived from the mnemonic). If that account doesn’t exist on chain, it falls back to the implicit account ID derived from the seed phrase’s public key.

Which tools are available in this server?

The server exposes 15 tools including get_account_balance, view_account_state, create_sub_account, send_tokens, call_function, batch_actions, deploy_contract, view_function, get_access_keys, add_full_access_key, add_function_call_key, delete_access_key, verify_signature, delete_account, and get_account_details.