Schema | NEAR Contract Deployer MCP Server

NEAR Contract Deployer MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
deploy_contractB	Deploy a WebAssembly (WASM) smart contract to a NEAR account. Requires the deployer account to have sufficient balance for storage costs.
initialize_contractA	Call an initialization method on a deployed contract. Most contracts require this after deployment.
upgrade_contractA	Upgrade an existing contract with new WASM code. The contract must be owned by the signer.
get_deployment_statusA	Check if a NEAR account has a smart contract deployed and get deployment details.
estimate_deployment_costA	Calculate the storage cost for deploying a WASM contract before actually deploying.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jim-agent/mcp-near-deploy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server