How to Use the Better Stack MCP in LlamaIndex

Q: Can LlamaIndex query past Better Stack incidents?

Yes. By indexing the results of listincidents, your RAG application can semantic-search past outages to find matching error patterns.

Q: How do I restrict LlamaIndex from using specific Better Stack tools?

Use the allowedtools filter when converting the spec. You can expose read-only tools like getmonitor while hiding mutation tools like resolveincident.

Index your Better Stack incident history into searchable vector stores with this LlamaIndex MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Better Stack MCP to LlamaIndex

Create your Vinkius account to connect Better Stack 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 Better Stack with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Turn outages into LlamaIndex knowledge

Past incidents hold the answers to current outages. LlamaIndex takes the output from this MCP Server and embeds it directly into your vector store. You run `list_incidents` and `get_incident` to pull historical timelines. The framework indexes that raw payload so your query engine can fetch exact mitigation steps the next time a similar alert fires.

Ground pipelines in live monitoring data

Stop relying on outdated documentation for infrastructure states. Your query engine can hit `list_monitors` and `get_monitor` to pull the live configuration of your endpoints. That live state merges with your static docs. When an engineer asks about a specific service, the answer includes real-time uptime metrics straight from the API.

Build context-aware MCP queries

Finding the right person during a crisis is usually a manual scramble. You can index your routing calendars by calling `list_on_call` and `list_heartbeats`. The agent knows exactly who to ping because the schedule is part of the queryable index. If a cron job fails, the system cross-references the heartbeat failure with the active pager rotation.

Setup guide

Set up Better Stack 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 Better Stack 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 Better Stack tools.",
)
response = await agent.run("List recent Better Stack 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 Better Stack. 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 Better Stack 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 Better Stack MCP in LlamaIndex

Wrap your HTTP URL in an MCP client instance. Set up a BasicMCPClient, wrap it in an McpToolSpec, and pass the async tool list to your agent.

Yes. By indexing the results of `list_incidents`, your RAG application can semantic-search past outages to find matching error patterns.

You need to trigger the update. Set up a routine that calls `list_monitors` and updates your index so the query engine always reads fresh state.

Use the allowed_tools filter when converting the spec. You can expose read-only tools like `get_monitor` while hiding mutation tools like `resolve_incident`.

Vinkius processes your requests in isolated, short-lived environments. Pager schedules and heartbeat configurations exist only during the active connection and leave no trace on our infrastructure.

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