How to Use the Goldsky (Web3 Data Indexing & Subgraphs) MCP in LlamaIndex

Q: Can LlamaIndex query historical errors from Goldsky (Web3 Data Indexing & Subgraphs) using this MCP Server?

Yes, your LlamaIndex agent uses getpipelineerrorcount to gather error counts over specific time windows. These metrics are indexed into your vector store, allowing you to run semantic queries on historical pipeline health.

Q: How does the Goldsky (Web3 Data Indexing & Subgraphs) MCP Server help LlamaIndex agents debug broken subgraphs?

The agent calls getpipelinelogs to fetch the raw stack traces from your active indexing pipelines. It parses these logs, indexes them, and matches them against known Web3 error patterns in your knowledge base.

Q: Can I use LlamaIndex to pause or resume Goldsky (Web3 Data Indexing & Subgraphs) pipelines based on query volume?

Yes, your agent can call pausepipeline or resumepipeline based on rules defined in your index. If your vector database reaches storage limits, the agent can pause ingestion until resources clear.

Q: How do I validate new subgraphs using LlamaIndex before deploying them?

Your agent feeds the YAML definition to validatepipeline to check for schema errors. LlamaIndex can compare the validation output against historical deployment configurations to flag potential logical issues.

Index live Web3 indexing pipeline states and error logs directly into your LlamaIndex vector store for semantic search.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Goldsky (Web3 Data Indexing & Subgraphs) MCP to LlamaIndex

Create your Vinkius account to connect Goldsky (Web3 Data Indexing & Subgraphs) to LlamaIndex 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 Goldsky (Web3 Data Indexing & Subgraphs) with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

LlamaIndex-Powered Log Search

This MCP Server provides the `get_pipeline_logs` and `get_pipeline_error_count` tools to inject live debugging data straight into your LlamaIndex RAG pipeline. Your indexer fetches raw execution logs and converts them into searchable document nodes. When debugging a failing subgraph, you query your LlamaIndex knowledge base to find past occurrences of similar errors. The agent retrieves the exact log context, helping you identify repeating patterns in blockchain ingestion failures.

Knowledge-Augmented Pipeline Management

The `list_pipelines` and `get_pipeline` tools allow your LlamaIndex agent to build a real-time map of your Web3 data architecture. The agent queries your active pipelines, indexes their configurations, and stores them as vector embeddings. This enables you to ask natural language questions about which pipelines write to specific database sinks. The agent answers based on actual, live API configurations rather than outdated static documentation.

State-Aware Query Routing

You can use `get_pipeline_status` and `get_pipeline_state` to route user queries in LlamaIndex based on real-time indexing sync health. The agent checks if a pipeline is fully synced before querying its database sink. If `get_pipeline_status` reports a degraded or paused state, the router diverts the query to a fallback database or warns the user about stale data. Don't let stale Web3 data break your application.

Setup guide

Set up Goldsky (Web3 Data Indexing & Subgraphs) MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Goldsky (Web3 Data Indexing & Subgraphs) MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Goldsky (Web3 Data Indexing & Subgraphs) tools.",
)
response = await agent.run("List recent Goldsky (Web3 Data Indexing & Subgraphs) data")

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 Goldsky. 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 Goldsky (Web3 Data Indexing & Subgraphs) 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 Goldsky (Web3 Data Indexing & Subgraphs) MCP in LlamaIndex

Yes, your LlamaIndex agent uses `get_pipeline_error_count` to gather error counts over specific time windows. These metrics are indexed into your vector store, allowing you to run semantic queries on historical pipeline health.

The agent calls `get_pipeline_logs` to fetch the raw stack traces from your active indexing pipelines. It parses these logs, indexes them, and matches them against known Web3 error patterns in your knowledge base.

Yes, your agent can call `pause_pipeline` or `resume_pipeline` based on rules defined in your index. If your vector database reaches storage limits, the agent can pause ingestion until resources clear.

Your agent feeds the YAML definition to `validate_pipeline` to check for schema errors. LlamaIndex can compare the validation output against historical deployment configurations to flag potential logical issues.

All pipeline configurations and API credentials are kept inside the ephemeral Vinkius sandbox. The MCP Server processes requests in memory, ensuring your sensitive Web3 database credentials are never written to disk or exposed to the LLM provider.

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