How to Use the Better Stack MCP in LlamaIndex

Q: How does LlamaIndex index data from the Better Stack MCP Server?

The McpToolSpec loads tools like listmonitors directly into your LlamaIndex agent. The agent executes the tool, retrieves the JSON payload, and converts it into document nodes for your index.

Q: Can I use LlamaIndex to query historical Better Stack incidents?

Yes, by combining listincidents with a vector store, you can run semantic searches over past outages. Your agent can quickly find which team resolved similar issues in the past.

Q: How does LlamaIndex handle real-time Better Stack updates?

Your LlamaIndex agent calls getmonitor dynamically during a query to fetch real-time uptime status. This keeps your RAG system updated with live telemetry.

Q: How do I configure the MCP tool limits in LlamaIndex?

You can use the allowedtools filter in LlamaIndex to restrict your agent's access. For example, you can expose only listmonitors while blocking destructive tools like deletemonitor.

Index your Better Stack incident history and monitor states directly into LlamaIndex vector stores.

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

Build a queryable knowledge base of your incidents

This MCP Server lets your LlamaIndex pipeline pull historical incident data using `list_incidents`. Instead of just reading the raw text, the framework indexes these events into your vector database. When an outage occurs, your agent queries this index to find past resolutions. It matches the current `get_incident` payload against historical post-mortems to suggest immediate fixes.

Keep your monitor configurations searchable in LlamaIndex

Run `list_monitors` to pull down your entire uptime configuration. LlamaIndex ingests this structured data, turning your live infrastructure setup into a searchable document store. You can ask your agent which endpoints lack coverage. It compares your active monitors against your actual API documentation to highlight gaps in your testing strategy.

Track heartbeat trends and status page updates

Your RAG applications pull live status data using this MCP integration. This ensures your context window is always grounded in actual, live system health metrics rather than outdated static files. This live grounding prevents your agent from hallucinating system statuses. It knows exactly which cron jobs are failing because it pulls the real-time heartbeat records via `list_heartbeats` on every query.

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

The `McpToolSpec` loads tools like `list_monitors` directly into your LlamaIndex agent. The agent executes the tool, retrieves the JSON payload, and converts it into document nodes for your index.

Yes, by combining `list_incidents` with a vector store, you can run semantic searches over past outages. Your agent can quickly find which team resolved similar issues in the past.

Your LlamaIndex agent calls `get_monitor` dynamically during a query to fetch real-time uptime status. This keeps your RAG system updated with live telemetry.

You can use the `allowed_tools` filter in LlamaIndex to restrict your agent's access. For example, you can expose only `list_monitors` while blocking destructive tools like `delete_monitor`.

Your Better Stack credentials are encrypted at rest and never exposed to the LLM or your vector database. The Vinkius sandbox ensures that only the raw tool outputs, like monitor metadata and incident histories, are sent to your pipeline.

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