How to Use the Kava Explorer MCP in CrewAI

Q: How do I give a CrewAI agent access to the Kava Explorer MCP Server?

Pass the Vinkius URL directly into the mcps parameter when defining your agent. The framework automatically imports the available Subscan tools.

Q: Do I restrict certain agents to specific tools?

Import MCPServerHTTP from crewai.mcp and apply a toolfilter. This lets you give one agent getblock while restricting another to getaccounttoken.

Deploy multi-agent crews to analyze the Kava blockchain. CrewAI delegates block tracking and validator scoring to specialized autonomous agents.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Kava Explorer MCP to CrewAI

Create your Vinkius account to connect Kava Explorer to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Kava Explorer with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate On-Chain Research Teams

The Kava Explorer MCP Server equips your crew with `list_blocks` and `list_events` to scan chain activity. Assign these tools to a dedicated Research Agent in CrewAI. This agent constantly monitors network traffic while passing relevant events to an Analysis Agent for processing. Shared memory keeps the crew aligned. When the researcher finds a suspicious transaction, the analyzer already knows the context. It immediately calls `get_extrinsic` to pull the exact payload and draft an incident report.

Audit Validator Performance

Scoring staking nodes requires `get_validator` and `get_account_reward_slash`. A specialized Auditor Agent uses these tools to track missed blocks and slash events across the active set. The agent compiles this data autonomously based on your hierarchical execution plan. Filter which agent gets which capability easily. Using `MCPServerHTTP` with a `tool_filter`, restrict the auditor to only see validator metrics. This prevents agents from getting distracted by unrelated account balance endpoints.

Map Account Architectures

Complex wallet structures demand deep inspection using `get_account_info` and `get_account_token`. Your Tracing Agent maps out token distributions across multiple addresses. It follows the money sequentially without needing manual prompts from a human operator. Setup takes two lines of Python. Pass your Vinkius endpoint directly into the `mcps` array of your agent configuration. CrewAI handles the HTTP transport and registers all the Subscan tools natively.

Setup guide

Set up Kava Explorer MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Kava Explorer tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Kava Explorer Analyst",
    goal="Access and analyze Kava Explorer data via MCP.",
    backstory="Expert analyst with direct Kava Explorer access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Kava Explorer transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Kava Explorer Analyst",
        goal="Access and analyze Kava Explorer data via MCP.",
        backstory="Expert analyst with direct Kava Explorer access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Kava Explorer transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Kava Explorer. 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.

Connect Kava Explorer now

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 Kava Explorer MCP in CrewAI

Pass the Vinkius URL directly into the `mcps` parameter when defining your agent. The framework automatically imports the available Subscan tools.

Import `MCPServerHTTP` from `crewai.mcp` and apply a `tool_filter`. This lets you give one agent `get_block` while restricting another to `get_account_token`.

Your crew executes tasks based on the process you define. A researcher lists validators first, passing the output to a second agent that pulls individual metrics.

Add your Vinkius endpoint token to the HTTP headers in your MCP connection config. The framework passes it with every tool invocation.

This MCP Server only reads public ledger data, such as validator slashes and extrinsic hashes. It operates entirely statelessly. Vinkius enforces zero-trust ephemeral execution, meaning no query history is retained after the HTTP request completes.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript