How to Use the GetBlock (Web3 RPC Provider) MCP in AutoGen
Give your AutoGen agents access to GetBlock (Web3 RPC Provider). Build multi-agent systems that debate and execute on-chain transactions.
Works with every AI agent you already use
…and any MCP-compatible client
Connect GetBlock (Web3 RPC Provider) MCP to AutoGen
Create your Vinkius account to connect GetBlock (Web3 RPC Provider) to AutoGen and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.
Consensus-Driven Execution
You don't want a single script firing off transactions blindly. AutoGen lets you build a system where a Security Agent and an Execution Agent debate the payload. The Security Agent runs `btc_analyzepsbt` to verify the inputs and outputs of a Partially Signed Bitcoin Transaction. If the analysis looks clean, the Execution Agent takes over and calls `btc_sendrawtransaction`. They negotiate the risk. If gas is too high based on `eth_estimate_gas`, a third Finance Agent can step in and veto the broadcast until the network cools down.
Multi-Agent Debugging via MCP Server
Smart contract failures require different perspectives. When a transaction reverts, your Lead Developer agent grabs the hash and orders the QA agent to run `debug_trace_transaction`. The QA agent parses the trace logs and identifies the exact failing opcode. It then hands the data back to the Lead Developer, who proposes a fix using `eth_call` to test the updated parameters against the current block state. The server acts as the shared terminal they both use to investigate the issue.
Cross-Chain Arbitrage Monitoring
You can spin up dedicated agents for different networks. Give one agent `sol_get_latest_blockhash` and `sol_get_balance`, and another agent `eth_block_number`. They monitor GetBlock endpoints independently. When conditions align, they signal a central coordinator agent. The coordinator evaluates the state of both chains and decides whether to trigger a cross-chain swap. You get autonomous monitoring without writing complex async polling loops from scratch.
Set up GetBlock (Web3 RPC Provider) MCP in AutoGen
Prerequisites
- Python 3.10+ installed
-
autogen-ext[mcp]package - Active Vinkius subscription with a valid endpoint token
- 1
Install AutoGen with MCP
Run
pip install "autogen-ext[mcp]" autogen-agentchat. The MCP extension includesmcp_server_toolsfor stateless tool access. - 2
Fetch tools from the MCP
Call
mcp_server_tools(SseServerParams(url=...))with your Vinkius endpoint. Replace[YOUR_TOKEN_HERE]with your token from cloud.vinkius.com. - 3
Run your agent
Pass the tools to
AssistantAgentand callagent.run(). The agent invokes GetBlock (Web3 RPC Provider) tools and returns structured results.
from autogen_ext.tools.mcp import SseServerParams, mcp_server_tools
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
server_params = SseServerParams(
url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
tools = await mcp_server_tools(server_params)
agent = AssistantAgent(
name="GetBlock (Web3 RPC Provider)_assistant",
model_client=OpenAIChatCompletionClient(model="gpt-4o"),
tools=tools,
)
result = await agent.run("List recent GetBlock (Web3 RPC Provider) data")
print(result.messages[-1].content) Prerequisites
- Python 3.10+ installed
-
autogen-ext[mcp]+autogen-agentchat - Active Vinkius subscription with a valid endpoint token
- 1
Install dependencies
Same packages as above.
McpWorkbenchis ideal when your agent needs stateful sessions across multiple tool calls. - 2
Use McpWorkbench as context manager
Wrap your agent in
async with McpWorkbench(...)to maintain shared state and resources. The workbench manages the full MCP session lifecycle. - 3
Run with workbench
Pass
workbench=workbenchto your agent. State is preserved across multiple tool calls within the same session.
from autogen_ext.tools.mcp import McpWorkbench, SseServerParams
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
server_params = SseServerParams(
url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
async with McpWorkbench(server_params) as workbench:
agent = AssistantAgent(
name="GetBlock (Web3 RPC Provider)_assistant",
model_client=OpenAIChatCompletionClient(model="gpt-4o"),
workbench=workbench,
)
result = await agent.run("List recent GetBlock (Web3 RPC Provider) data")
print(result.messages[-1].content) Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GetBlock. 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.
Why Choose Vinkius
Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.
Real-time monitoring
Live
visibility into every interaction
Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.
Built-in savings
60%
lower AI costs
Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.
Single dashboard
One
place for every integration
Every tool your AI connects to, managed from a single screen. One account, complete control.
Common questions about GetBlock (Web3 RPC Provider) MCP in AutoGen
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
Start using the GetBlock (Web3 RPC Provider) MCP today
We host it, we monitor it, we maintain it. You just paste one token.