NEAR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACCOUNT_ID | Yes | Your NEAR account ID for authentication | |
| ACCOUNT_KEY | Yes | Private key for your NEAR account (ed25519: or secp256k1: format) | |
| NEAR_NODE_URL | No | Custom NEAR RPC endpoint | |
| NEAR_GAS_LIMIT | No | Gas limit for transactions | |
| NEAR_NETWORK_ID | No | NEAR network ("mainnet", "testnet", "betanet") | mainnet |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| watch_near_eventC | Start watching for specific events on a NEAR contract and process them with AI responses |
| stop_watching_near_eventC | Stop watching for specific events on a NEAR contract |
| list_watched_near_eventsA | List all currently watched NEAR events and their status |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: listing, stopping, or starting event watches. No overlap or ambiguity.
All tools use a verb_near_event pattern (list_watched, stop_watching, watch). Minor inconsistency in tense (watched vs watching) but overall predictable.
3 tools is appropriate for a focused event-watching server. Not over- or under-scoped.
Covers the basic lifecycle: create (watch), read (list), delete (stop). Missing update but that is often unnecessary for event filters.