Gelato Network MCP for AI. Automate complex Web3 transactions via chat.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
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.
What AI agents can do with Gelato Network Automation
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.
Calculates the necessary gas limits and pricing for submitting an ERC-4337 UserOperation.
Sends a fully formed, signed ERC-4337 UserOperation to initiate complex on-chain actions.
Submits general signed transactions for relaying across various chains and provides unique IDs to track their execution status.
Retrieves the current, real-time status of any task or transaction ID submitted through the MCP.
Gets accurate gas price data and token exchange rates to predict costs before execution.
Ask an AI about this
Waiting for input…
What AI agents can do with Gelato Network: 12 Tools for Web3 Automation
Use these tools to submit signed transactions, calculate precise gas costs, manage account abstraction calls, and monitor the real-time status of any Web3 task.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Gelato Network on VinkiusBundler 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...
Relayer Send Transaction
Accepts a signed transaction and returns a unique task ID that you can use to track its relay status.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Gelato Network, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Gelato Network. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking Web3 activity feels like detective work., Solved with Vinkius AI Gateway
Today, moving funds or executing complex smart contract logic means jumping through hoops. You submit a transaction on one site, then you have to copy the resulting task ID and paste it into a separate block explorer tab. If it fails, you're guessing whether the issue is gas, wallet permission, or network congestion. It's manual, tedious, and frankly, slow.
With this MCP, that entire process collapses back into your chat window. You ask your agent to monitor the task status using `relayer_get_status`, and it gives you a clean answer right there. No more context switching; just reliable status updates for all your complex actions.
Use Gelato Network MCP to manage every transaction lifecycle.
You no longer need to manually verify if the correct fee collectors and payment tokens are active. You simply ask the agent, and it confirms what's supported using `relayer_get_capabilities`. This pre-check eliminates an entire class of cross-chain deployment errors.
What changes is that you get a single source of truth for your Web3 operations. From estimating costs with `bundler_estimate_user_operation_gas` to submitting the final action via `relayer_send_transaction`, everything happens through one unified interface.
What your AI can actually do with this
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.
019ea5ee-51cb-731c-b8ca-33cac0ed01fc Here's how it actually works
The bottom line is: you talk to your agent naturally, and it handles all the complicated cross-chain blockchain plumbing for you.
Connect your API key to the MCP and designate which blockchain networks you need access for.
Tell your agent what needs doing, like 'Estimate gas for a UserOperation on Polygon' or 'Relay this signed transaction data'.
The MCP executes the necessary calls, providing immediate feedback, task IDs, or the final status of the action.
Who is this actually for?
This connector is built for anyone managing complex, multi-step Web3 infrastructure. If you're tired of manually checking transaction status across five different block explorers or constantly recalculating gas costs before deployment, this MCP saves hours.
Needs to integrate account abstraction and gasless transactions directly into their codebase without writing massive boilerplate relaying logic.
Monitors the status of mission-critical, cross-chain infrastructure tasks and manages operational costs from a single terminal view.
Automates fee calculation, transaction relaying, and state monitoring for multi-protocol or cross-chain operations.
What Changes When You Connect
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.
See it in action
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.
The honest tradeoffs
Assuming simple transactions are enough
Attempting to process an advanced, multi-step action (like staking or governance vote) just by sending a raw transaction without checking the required gas limits.
Always start with bundler_estimate_user_operation_gas first. This gives you the necessary blueprint for complex actions before you attempt to submit using bundler_send_user_operation. Never guess on gas.
Ignoring confirmation status
Submitting a critical transaction via relayer_send_transaction and then assuming it went through just because the MCP accepted the request.
After submission, immediately use relayer_get_status. This tool provides the definitive truth about whether the task is pending, failed, or confirmed on-chain. Use this ID for all future checks.
Mixing up relaying and abstraction
Trying to use general transaction relay methods when the action specifically requires ERC-4337 account abstraction logic.
For smart contract actions, stick to the dedicated bundler tools. Use bundler_send_user_operation for submitting abstract calls and always check supported addresses with bundler_supported_entry_points.
When It Fits, When It Doesn't
Use this MCP if your workflow involves multiple steps that require managing gas, handling account abstraction (ERC-4337), or tracking the lifecycle of cross-chain transactions. Specifically, when you need to know why a transaction failed or what its precise cost is before submitting it, this connector shines because of tools like bundler_estimate_user_operation_gas and relayer_get_fee_data. Don't use it if all you need to do is read simple data (like checking the balance of one address). For basic reads, a standard blockchain reader tool will suffice. But for any operation that requires submitting signed payloads or ensuring robust confirmation across different chains, this MCP gives you the necessary control and visibility.
Questions you might have
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.
We've already built the connector for Gelato Network. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.