How to Use the Better Stack MCP in CrewAI

Q: Can I restrict which Better Stack tools a CrewAI agent can use?

Yes, you can use CrewAI's MCPServerHTTP class with a toolfilter to limit agent access. For example, you can allow a junior agent to run listincidents while blocking it from executing destructive actions like deletemonitor.

Deploy specialized teams of AI agents to manage Better Stack monitors and coordinate incident responses using CrewAI.

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

Multi-Agent Incident Triage with CrewAI

This CrewAI setup connects a cooperative team of specialized agents to the Better Stack MCP Server. An On-Call Agent runs `list_incidents` to detect active outages, while a separate Triage Agent analyzes the logs. They share context dynamically to pinpoint root causes fast. Once the problem is identified, the crew queries `list_on_calls` to find the right engineer. The agents compile a summary of the outage and send a Slack message to the engineer on shift, bypassing manual escalation steps.

Autonomous Monitor Auditing

Keep your monitoring configuration clean using this MCP toolset. A QA Agent runs `list_monitors` to audit every active endpoint check. It flags redundant tests and identifies critical APIs that lack coverage. The auditing agent can then call `create_monitor` to deploy new checks for untracked endpoints. If it finds broken or legacy tests, it suggests calling `delete_monitor` to keep your Better Stack billing in check.

Status Page Synchronization

Let your agents manage public communications during downtime. A Technical Writer Agent uses `get_incident` to understand the technical details of a failure. It then drafts clear, customer-friendly copy for your public status page. Next, a Moderator Agent reviews the draft, then calls `list_status_pages` to find the correct public dashboard. The crew ensures your users stay informed without pulling engineers away from fixing the actual database crash.

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

You configure your CrewAI agent by adding the Vinkius HTTP endpoint to the `mcps` list parameters. The agent automatically discovers tools like `list_monitors` and `get_monitor`. This allows your crew to query uptime data without manual Python tool wrappers.

Yes, you can use CrewAI's `MCPServerHTTP` class with a `tool_filter` to limit agent access. For example, you can allow a junior agent to run `list_incidents` while blocking it from executing destructive actions like `delete_monitor`.

CrewAI agents use a shared memory system to exchange tool outputs. When the monitoring agent runs `get_incident`, the resulting payload is immediately accessible to the communication agent. This prevents redundant API requests and keeps your crew synchronized.

CrewAI connects to the hosted MCP server using standard SSE or Streamable HTTP transports. This setup ensures fast, lightweight communication when fetching `list_heartbeats` or updating monitor parameters from your Python scripts.

Your Better Stack credentials are never exposed to the CrewAI framework or stored on Vinkius. The connection runs inside an ephemeral, zero-trust V8 sandbox that isolates your API keys. Only the specific uptime monitors, heartbeat configurations, and incident reports requested by your active agents are processed.

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