NEAR MCP

NEAR MCP

Interact with the NEAR blockchain through MCP calls

nearai

Developer Tools
Visit Server

Tools

system_list_local_keypairs

List all accounts and their keypairs in the local keystore by network.

system_import_account

Import an account into the local keystore. This will allow the user to use this account in other tools. Remember mainnet accounts are created with a .near suffix, and testnet accounts are created with a .testnet suffix.

system_remove_local_account

Removes a local NEAR account from the local keystore. Once removed, the account will no longer be available to the user. This does not delete the account from the NEAR blockchain, it only removes the account from the local keystore.

account_view_account_summary

Get summary information about any NEAR account. This calls the public RPC endpoint to get this information.

system_search_popular_fungible_token_contracts

Search for popular fungible token contract information on the NEAR blockchain, with a grep-like search. Use this tool to search for popular fungible token contract information. This tool works by 'grepping' through a list of contract information JSON objects. Useful for getting contract information about popular tokens like USDC native, USDT, WNEAR, and more.

account_export_account

Export an account from the local keystore to a file.

account_sign_data

Cryptographically sign a piece of data with a local account's private key, then encode the result with the specified encoding. Outputs the curve, encoded signature, and encoding used.

account_verify_signature

Cryptographically verify a signed piece of data against some NEAR account's public key.

account_create_implicit_account

Create an implicit account on the NEAR blockchain. An implicit account is a new random keypair that is not associated with an account ID. Instead the account ID is derived from the public key of the keypair (a 64-character lowercase hexadecimal representation of the public key). This implicit account id can be used just as a regular account id, but remember *it is not* an official account id with a .near or .testnet suffix. Creating implicit accounts is useful for adding new access keys to an existing account.

account_create_account

Create a new NEAR account with a new account ID. The initial balance of this account will be funded by the account that is calling this tool. This account will be created with a random public key. If no account ID is provided, a random one will be generated. Ensure that mainnet accounts are created with a .near suffix, and testnet accounts are created with a .testnet suffix.

account_delete_account

Delete an account from the NEAR blockchain. This will also remove the account from the local keystore and any associated keypair.

account_list_access_keys

List all access keys for an given account.

account_add_access_key

Add an access key to an account. This will allow the account to interact with the contract.

account_delete_access_keys

Delete an access key from an account based on it's public key.

tokens_send_near

Send NEAR tokens to an account (in NEAR). The signer account is the sender of the tokens, and the receiver account is the recipient of the tokens. Remember mainnet accounts are created with a .near suffix, and testnet accounts are created with a .testnet suffix. The user is sending tokens as the signer account. Please ensure that the sender and receiver accounts are in the same network.

tokens_send_ft

Send Fungible Tokens (FT) like USDC native, USDT, WNEAR, etc. based on the NEP-141 and NEP-148 standards to an account. The signer account is the sender of the tokens, and the receiver account is the recipient of the tokens. Ensure the contract account id exists and is in the same network as the signer and receiver accounts.

contract_view_functions

View available functions on a NEAR smart contract.

contract_get_function_args

Get the arguments of a function call by parsing the contract's ABI or by using the nearblocks.io API (as a fallback). This function API checks recent execution results of the contract's method being queried to determine the likely arguments of the function call. Warning: This tool is experimental and is not garunteed to get the correct arguments.

contract_call_raw_function_as_read_only

Call a function of a contract as a read-only call. This is equivalent to saying we are calling a view method of the contract.

contract_call_raw_function

Call a function of a contract as a raw function call action. This tool creates a function call as a transaction which costs gas and NEAR.

README

<div align="center"> <img src="assets/near-mcp.svg" alt="NEAR MCP Logo" width="200" /> </div>

npm version Telegram

NEAR MCP

This project is a Model Context Protocol (MCP) compatible server for interacting with the NEAR blockchain. This tool provides a way for LLMs and AI agents to securely access and interact with NEAR accounts and blockchain functionality.

Installing

The main way near-mcp is mean to be used is with an MCP compatible service.

Adding to the claude code cli:

claude mcp add near-mcp npx @nearai/near-mcp@latest run

Adding via JSON config:

{
  "mcpServers": {
    "near-mcp": {
      "command": "npx",
      "args": ["-y", "@nearai/near-mcp@latest", "run"],
      "env": {}
    }
  }
}

Adding to goose

┌   goose-configure
│
◇  What would you like to configure?
│  Add Extension
│
◇  What type of extension would you like to add?
│  Command-line Extension
│
◇  What would you like to call this extension?
│  near-mcp
│
◇  What command should be run?
│  npx @nearai/near-mcp@latest run
│
◇  Please set the timeout for this tool (in secs):
│  60
│
◇  Would you like to add environment variables?
│  No
│
└  Added near-mcp extension

Or you can install it globally and use it directly.

# Install globally
npm install -g @nearai/near-mcp@latest

# Or use directly with npx
npx @nearai/near-mcp@latest run

Available Tools

see TOOLS.md for a list of available tools and arguments.

Integration with AI Models

This tool is designed to be used with AI models that support the Model Context Protocol. It enables AI assistants to:

  1. Manage NEAR accounts on behalf of users
  2. Check account balances and status
  3. Sign and send transactions
  4. Create new accounts and manage access keys
  5. Inspect and execution smart contracts

Security Considerations

  • This MCP is meant to be run locally. Account private keys are stored in a local unencrypted keystore where the MCP server is running.
  • The underlying models should not have access to see the private keys of the accounts they are interacting with with one exception. The import_account tool allows the model to import an account from a private key. This requires the user to provide the private key to the model.

Contributing

We welcome contributions to the NEAR MCP server! Please see the CONTRIBUTING.md file for more information.

Reporting Issues

If you find a bug or have a feature request, please open an issue on the GitHub repository.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
MCP Package Docs Server

MCP Package Docs Server

Facilitates LLMs to efficiently access and fetch structured documentation for packages in Go, Python, and NPM, enhancing software development with multi-language support and performance optimization.

Featured
Local
TypeScript
Claude Code MCP

Claude Code MCP

An implementation of Claude Code as a Model Context Protocol server that enables using Claude's software engineering capabilities (code generation, editing, reviewing, and file operations) through the standardized MCP interface.

Featured
Local
JavaScript
@kazuph/mcp-taskmanager

@kazuph/mcp-taskmanager

Model Context Protocol server for Task Management. This allows Claude Desktop (or any MCP client) to manage and execute tasks in a queue-based system.

Featured
Local
JavaScript
Linear MCP Server

Linear MCP Server

Enables interaction with Linear's API for managing issues, teams, and projects programmatically through the Model Context Protocol.

Featured
JavaScript
mermaid-mcp-server

mermaid-mcp-server

A Model Context Protocol (MCP) server that converts Mermaid diagrams to PNG images.

Featured
JavaScript
Jira-Context-MCP

Jira-Context-MCP

MCP server to provide Jira Tickets information to AI coding agents like Cursor

Featured
TypeScript
Linear MCP Server

Linear MCP Server

A Model Context Protocol server that integrates with Linear's issue tracking system, allowing LLMs to create, update, search, and comment on Linear issues through natural language interactions.

Featured
JavaScript
Sequential Thinking MCP Server

Sequential Thinking MCP Server

This server facilitates structured problem-solving by breaking down complex issues into sequential steps, supporting revisions, and enabling multiple solution paths through full MCP integration.

Featured
Python