# Gelato Network MCP

> Gelato Network MCP automates complex Web3 infrastructure workflows using natural conversation. It lets you submit signed transactions, estimate gas costs for UserOperations, and monitor the status of relayed tasks across multiple blockchains—all without leaving your chat client. Stop hopping between block explorers to manage cross-chain activity; this MCP handles the heavy lifting from account abstraction (ERC-4337) through reliable transaction relaying.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Tags:** web3, ethereum, account-abstraction, relayer, gasless-transactions

## Description

Managing complex Web3 actions used to mean juggling dozens of tabs: connecting wallets, submitting forms on multiple chains, and waiting for confirmations on separate block explorers. Now you can automate all that complexity using your agent directly within any MCP-compatible client. This connection lets you treat advanced blockchain operations like simple conversation. You submit a signed transaction and the MCP relays it to various networks; you request gas estimates and get precise pricing data, or you check the full lifecycle status of a previously submitted task. Whether you're building a decentralized application or running infrastructure monitoring, this capability drastically cuts down on manual effort. Because Vinkius hosts this connector in its catalog, you access robust Web3 reliability right alongside your other developer tools.

## Tools

### bundler_estimate_user_operation_gas
Calculates the required gas limits needed to execute a specific UserOperation.

### bundler_get_user_operation_by_hash
Retrieves all details about an ERC-4337 UserOperation using its unique hash.

### bundler_get_user_operation_gas_price
Fetches the current gas pricing specifically for UserOperations.

### bundler_get_user_operation_receipt
Retrieves the final receipt confirming the outcome of a completed UserOperation.

### bundler_send_user_operation
Submits an ERC-4337 UserOperation to initiate an action on the blockchain.

### bundler_supported_entry_points
Lists all active EntryPoint addresses supported by the network for smart contract interaction.

### relayer_get_capabilities
Checks which payment tokens and fee collector addresses are valid across supported chains.

### relayer_get_fee_data
Gets current token exchange rates alongside gas price data for multiple networks.

### relayer_get_fee_quote
Provides a precise fee quote based on a specified amount of required gas.

### relayer_get_status
Checks the status of any previously relayed transaction using its unique task ID.

### relayer_send_transaction_sync
Submits a signed transaction and waits synchronously until it has been confirmed on the chain.

### relayer_send_transaction
Accepts a signed transaction and returns a unique task ID that you can use to track its relay status.

## Prompt Examples

**Prompt:** 
```
Relay this signed transaction data to address 0x123... on Polygon (chainId 137).
```

**Response:** 
```
I've submitted the transaction to Gelato Relayer. Your Task ID is 0xabc123... You can check its status anytime using this ID.
```

**Prompt:** 
```
What is the current status of Gelato task 0x550e8400-e29b-41d4-a716-446655440000?
```

**Response:** 
```
The task is currently 'ExecSuccess'. It was included in block 1523421. Would you like to see the full transaction receipt?
```

**Prompt:** 
```
Estimate gas for this UserOperation on Optimism (chainId 10).
```

**Response:** 
```
I've calculated the gas limits for your UserOperation on Optimism. The estimated callGasLimit is 45000 and verificationGasLimit is 120000.
```

## Capabilities

### Estimate UserOperation Costs
Calculates the necessary gas limits and pricing for submitting an ERC-4337 UserOperation.

### Submit Account Abstraction Transactions
Sends a fully formed, signed ERC-4337 UserOperation to initiate complex on-chain actions.

### Relay and Track General Transactions
Submits general signed transactions for relaying across various chains and provides unique IDs to track their execution status.

### Check Transaction Status
Retrieves the current, real-time status of any task or transaction ID submitted through the MCP.

### Obtain Fee Intelligence
Gets accurate gas price data and token exchange rates to predict costs before execution.

## Use Cases

### Automating a cross-chain asset transfer
A protocol team needs to move tokens from Chain A to Chain B. Instead of writing dedicated, complex code for each chain's relay mechanism, they ask their agent to 'Relay this signed transaction data to Polygon.' The MCP handles the full process and provides a unique task ID that can be tracked using `relayer_get_status` until completion.

### Testing complex smart contract interactions
A developer needs to test an ERC-4337 workflow. They first use `bundler_estimate_user_operation_gas` to confirm the cost, then use `bundler_send_user_operation` to submit the transaction for testing purposes, getting immediate feedback on the process.

### Monitoring failed or stuck transactions
A DevOps engineer suspects a scheduled payment job failed. They input the original task ID and use `relayer_get_status`. The MCP confirms the current state, allowing them to determine if a simple resubmission (using `relayer_send_transaction`) is necessary.

### Performing immediate gas cost analysis
A user needs to know how much an action will cost right now. They ask the agent for pricing, and the MCP uses `relayer_get_fee_data` or `relayer_get_fee_quote` to return real-time token exchange rates and gas prices.

## Benefits

- Stop manually calculating gas limits. Use `bundler_estimate_user_operation_gas` to get precise cost estimates for any ERC-4337 action before you commit funds.
- Don't worry about transaction failure. If a complex task gets stuck, use `relayer_get_status` with the unique ID to check its exact on-chain status without guessing.
- Handle account abstraction and gasless interactions easily. The MCP processes your signed transactions using `bundler_send_user_operation`, abstracting away low-level wallet details.
- Avoid cross-chain errors by first checking capabilities with `relayer_get_capabilities`. This ensures the correct payment tokens are ready for deployment on any network.
- Gain instant cost clarity. Before submitting anything, run `relayer_get_fee_quote` to lock down the expected fees based on required gas amounts.

## How It Works

The bottom line is: you talk to your agent naturally, and it handles all the complicated cross-chain blockchain plumbing for you.

1. Connect your API key to the MCP and designate which blockchain networks you need access for.
2. Tell your agent what needs doing, like 'Estimate gas for a UserOperation on Polygon' or 'Relay this signed transaction data'.
3. The MCP executes the necessary calls, providing immediate feedback, task IDs, or the final status of the action.

## Frequently Asked Questions

**How does Gelato Network MCP handle cross-chain fee quoting?**
It gets accurate rates by calling tools like `relayer_get_fee_data` and `relayer_get_fee_quote`. This ensures you know the exact cost before initiating a transaction, regardless of which token or chain is involved.

**Is Gelato Network MCP only for Ethereum?**
No. It supports multiple chains. You can use its capabilities to manage transactions on various supported blockchains by specifying the correct network ID in your prompt.

**What is the difference between `relayer_send_transaction` and `bundler_send_user_operation`?**
Relaying handles general signed transactions, giving you a tracking ID. Bundling specifically handles complex actions using the ERC-4337 standard for account abstraction.

**Can I check the status of an old task with Gelato Network MCP?**
Yes. You can use `relayer_get_status` by providing the unique task ID. This tool checks the current, definitive state of that transaction on-chain.

**Does this MCP help me avoid manual gas calculations for my dApp?**
Absolutely. Use `bundler_estimate_user_operation_gas` to calculate gas limits and costs needed for your UserOperation, removing guesswork from deployment.