write_contract

Initiate state-changing smart contract functions on Ethereum-compatible blockchains. Specify contract details, ABI, function, and arguments, then sign and send transactions securely.

Instructions

Write data to a smart contract by calling a state-changing function. This modifies blockchain state and requires gas payment and transaction signing.

Input Schema

Name	Required	Description
`abi`	Yes	The ABI (Application Binary Interface) of the smart contract function, as a JSON array
`args`	Yes	The arguments to pass to the function, as an array (e.g., ['0x1234...', '1000000000000000000'])
`contractAddress`	Yes	The address of the smart contract to interact with
`functionName`	Yes	The name of the function to call on the contract (e.g., 'transfer')
`network`	No	Network name (e.g., 'ethereum', 'optimism', 'arbitrum', 'base', 'polygon') or chain ID. Defaults to Ethereum mainnet.
`privateKey`	Yes	Private key of the sending account in hex format (with or without 0x prefix). SECURITY: This is used only for transaction signing and is not stored.

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "abi": {
      "description": "The ABI (Application Binary Interface) of the smart contract function, as a JSON array",
      "type": "array"
    },
    "args": {
      "description": "The arguments to pass to the function, as an array (e.g., ['0x1234...', '1000000000000000000'])",
      "type": "array"
    },
    "contractAddress": {
      "description": "The address of the smart contract to interact with",
      "type": "string"
    },
    "functionName": {
      "description": "The name of the function to call on the contract (e.g., 'transfer')",
      "type": "string"
    },
    "network": {
      "description": "Network name (e.g., 'ethereum', 'optimism', 'arbitrum', 'base', 'polygon') or chain ID. Defaults to Ethereum mainnet.",
      "type": "string"
    },
    "privateKey": {
      "description": "Private key of the sending account in hex format (with or without 0x prefix). SECURITY: This is used only for transaction signing and is not stored.",
      "type": "string"
    }
  },
  "required": [
    "contractAddress",
    "abi",
    "functionName",
    "args",
    "privateKey"
  ],
  "type": "object"
}

EVM MCP Server

write_contract

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from EVM MCP Server

Related Tools

MCP directory API