How to Use the Better Stack MCP in CrewAI

Q: Can I track cron job failures with this setup?

Your crew can monitor passive nodes by calling getheartbeat on a schedule. The agent reads the explicit details and alerts you if the cron job stops pinging the server.

Deploy a squad of autonomous agents to handle outages. CrewAI and this MCP Server turn manual incident response into a self-driving operation.

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 CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous Triage with CrewAI

Assigning a researcher agent to run `list_incidents` means you stop waking up at 3 AM to check a broken server. When an outage hits, that first agent grabs the native timeline payload using `get_incident` and passes it down the chain. A second analyst agent takes that timeline data and figures out exactly what broke. It reads the logs, determines the root cause, and decides if the issue requires human intervention. The entire diagnostic process happens before your lead engineer even opens their laptop.

Specialized Monitor Auditing via MCP

Executing `list_monitors` every morning with a specialized auditor agent replaces manual infrastructure checks. Keeping track of hundreds of uptime checks usually requires a dedicated site reliability engineer. The agent checks the configuration of every single endpoint to ensure nothing slipped through the cracks. Finding a passive node that stopped reporting is just as simple. The auditor calls `list_heartbeats` to verify all cron jobs are firing correctly. If a heartbeat is missing, the agent drafts a report and sends it straight to your Slack channel.

Safe Resolution with Tool Filters

Applying a strict tool filter around `acknowledge_incident` prevents your AI from making unauthorized changes. Giving an agent full write access to your production alerts is a terrible idea. That specific crew member only gets permission to silence the page and nothing else. Another senior agent might hold the keys to `resolve_incident`, but only after reviewing the junior agent's work. Hierarchical execution means actions happen in a specific, approved order. You build a resilient response team that follows your exact runbook.

Setup guide

Set up Better Stack 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 Better Stack tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Better Stack 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="Better Stack Analyst",
        goal="Access and analyze Better Stack data via MCP.",
        backstory="Expert analyst with direct Better Stack access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Better Stack 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 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 CrewAI

Pass your Vinkius endpoint URL directly into the client array when defining your agent. For more granular control, import the HTTP server class and map the specific tools you want to expose.

Yes. You can configure a researcher agent to fetch the timeline, while a responder agent executes the fix. They share memory and pass the context back and forth until the alert clears.

Apply a filter when configuring the server connection. Exclude the resolution endpoints so the agent can only read data or acknowledge the page.

Your crew can monitor passive nodes by calling `get_heartbeat` on a schedule. The agent reads the explicit details and alerts you if the cron job stops pinging the server.

Vinkius routes all agent requests through an isolated, zero-trust V8 environment. The explicit details of your passive heartbeat nodes remain completely secure during the transaction. Once the crew finishes its task, the execution sandbox is immediately destroyed.

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