4,000+ servers built on vurb.ts
Vinkius

The Graph (Web3 Indexing) MCP Server for CrewAIGive CrewAI instant access to 8 tools to Get Evm Historical Balances, Get Evm Holders, Get Evm Swaps, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to The Graph (Web3 Indexing) through Vinkius, pass the Edge URL in the `mcps` parameter and every The Graph (Web3 Indexing) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The The Graph (Web3 Indexing) MCP Server for CrewAI is a standout in the Developer Tools category — giving your AI agent 8 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="The Graph (Web3 Indexing) Specialist",
    goal="Help users interact with The Graph (Web3 Indexing) effectively",
    backstory=(
        "You are an expert at leveraging The Graph (Web3 Indexing) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in The Graph (Web3 Indexing) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
The Graph (Web3 Indexing)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About The Graph (Web3 Indexing) MCP Server

Connect to The Graph to index and retrieve real-time blockchain data across multiple ecosystems. This MCP server allows your AI agent to query decentralized data from Ethereum, Polygon, Solana, and more through standardized tools and custom GraphQL subgraphs.

When paired with CrewAI, The Graph (Web3 Indexing) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call The Graph (Web3 Indexing) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • EVM Data Access — Retrieve token transfers, top holders, and DEX swap events (Uniswap, Curve) for any EVM-compatible chain.
  • Solana (SVM) Integration — Fetch SPL token transfers, holders, and AMM swaps (Jupiter, Raydium) directly from the Solana network.
  • Historical Analysis — Access wallet balance changes in OHLCV format to track portfolio performance over time.
  • Custom Subgraph Queries — Execute raw GraphQL queries against any specific subgraph ID for deep, specialized data extraction.
  • Market Intelligence — Monitor liquidity pool activities and token distribution metrics without manual block explorer searching.

The The Graph (Web3 Indexing) MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 8 The Graph (Web3 Indexing) tools available for CrewAI

When CrewAI connects to The Graph (Web3 Indexing) through Vinkius, your AI agent gets direct access to every tool listed below — spanning web3, ethereum, solana, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get evm historical balances on The Graph (Web3 Indexing)

Get EVM historical balances

get

Get evm holders on The Graph (Web3 Indexing)

Get EVM token holders

get

Get evm swaps on The Graph (Web3 Indexing)

) for EVM chains. Get EVM DEX swaps

get

Get evm transfers on The Graph (Web3 Indexing)

Get EVM token transfers

get

Get svm holders on The Graph (Web3 Indexing)

Get SVM (Solana) token holders

get

Get svm swaps on The Graph (Web3 Indexing)

) for Solana. Get SVM (Solana) DEX swaps

get

Get svm transfers on The Graph (Web3 Indexing)

Get SVM (Solana) token transfers

query

Query subgraph on The Graph (Web3 Indexing)

Requires THE_GRAPH_API_KEY. Query a subgraph using GraphQL

Connect The Graph (Web3 Indexing) to CrewAI via MCP

Follow these steps to wire The Graph (Web3 Indexing) into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from The Graph (Web3 Indexing)

Why Use CrewAI with the The Graph (Web3 Indexing) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with The Graph (Web3 Indexing) through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

The Graph (Web3 Indexing) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the The Graph (Web3 Indexing) MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries The Graph (Web3 Indexing) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries The Graph (Web3 Indexing), analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain The Graph (Web3 Indexing) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries The Graph (Web3 Indexing) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for The Graph (Web3 Indexing) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with The Graph (Web3 Indexing) immediately.

01

"Get the top 10 holders for the EVM token at 0x7fc66500c84a76ad7e9c93437bfc5ac33e2ddae9."

02

"Show me recent swaps for the Solana token DezXAZ8z7PnrnMcFWRSTQC8PGL9P8be3EFr9SptT5v7."

03

"Query the Uniswap V3 subgraph with ID 'ELUvFp... ' to get the latest pool prices."

Troubleshooting The Graph (Web3 Indexing) MCP Server with CrewAI

Common issues when connecting The Graph (Web3 Indexing) to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

The Graph (Web3 Indexing) + CrewAI FAQ

Common questions about integrating The Graph (Web3 Indexing) MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →