A Model Context Protocol (MCP) server that provides onchain tools for Claude AI, allowing it to interact with the Polygon PoS blockchain
Polygon mcp mcp server connects Polygon MCP to AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server that provides onchain tools for Claude AI, allowing it to interact with the Polygon PoS blockchain.
A Model Context Protocol (MCP) server that provides onchain tools for Claude AI, allowing it to interact with the Polygon PoS blockchain.
Once connected, the assistant can call these 4 tools directly:
call_contract — Parameters: - contractAddress: The address of the contract to call - functionName: The name of the function to call - functionArgs: The arguments to pass toerc20_balance — Parameters: - contractAddress: The address of the contract to get the balance oferc20_transfer — Parameters: - contractAddress: The address of the contract to transfer the token from - toAddress: The address of the recipient - amount: The amount of tokensget_gas_price — The get_gas_price tool exposed by this serverSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
The server reads one environment variable: SEED_PHRASE. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Polygon MCP sits in that group, and the shape of its toolset — call_contract, erc20_balance, erc20_transfer among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| call_contract | Parameters: - contractAddress: The address of the contract to call - functionName: The name of the function to call - functionArgs: The arguments to pass to the function - abi: The ABI of the contract - value (optional): |
| erc20_balance | Parameters: - contractAddress: The address of the contract to get the balance of |
| erc20_transfer | Parameters: - contractAddress: The address of the contract to transfer the token from - toAddress: The address of the recipient - amount: The amount of tokens to transfer |
| get_gas_price | The get_gas_price tool exposed by this server. |
{
"mcpServers": {
"polygon": {
"command": "node",
"args": ["/path/to/polygon-mcp/build/index.js"],
"env": {
"SEED_PHRASE": "your twelve word seed phrase here"
},
"disabled": false,
"autoApprove": []
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SEED_PHRASE | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.