Bring Incident Management
to CrewAI
Create your Vinkius account to connect Better Stack to CrewAI and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Better Stack MCP Server?
Connect your Better Stack (Better Uptime) account to any AI agent and empower it to act as your Level 1 Site Reliability Engineer (SRE). Let your AI diagnose incidents, manage escalations, and audit monitoring configs securely via conversation.
What you can do
- Incident Response — Rapidly list firing incidents, inspect technical downtime payloads, acknowledge alerts, and force resolve states inline
- Uptime Monitors — Fetch exact definitions of active HTTP endpoint pings, DNS probes, and latency constraints across your fleet
- Cron Heartbeats — Investigate passive tracking endpoints validating background workers and server limits
- On-Call Management — Expose active shifts and team schedules to determine explicitly who is getting paged in real-time
- Status Pages — Read configured public dashboards tracking your global infrastructure
How it works
- Subscribe to this server
- Enter your Better Stack API Token
- Empower Claude, Cursor, or your preferred agent to respond to alerts interactively
Stop switching context between your terminal and incident dashboards during critical outages.
Who is this for?
- DevOps & SREs — audit on-call matrices safely, track firing pages, and orchestrate initial debugging workflows without leaving chat
- Engineering Managers — review recent downtime timelines and resolve dormant alerts quickly
- Backend Developers — rapidly debug failing cron heartbeats while simultaneously patching code
Built-in capabilities (10)
Acknowledge an ongoing explicit incident halting paging
Get explicit details of a passive heartbeat node
Retrieve the native timeline payload of an explicit incident
Get full details of a specific Better Stack monitor
List all configured cron heartbeats securely
List all explicit incidents on Better Stack
List all monitors on Better Stack (Better Uptime)
List exact On-Call routing calendars
List all explicit Status Pages
Force resolve a specific incident
Why CrewAI?
When paired with CrewAI, Better Stack becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Better Stack tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Better Stack in CrewAI
Why run Better Stack with Vinkius?
The Better Stack connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Better Stack using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Better Stack and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Better Stack to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Better Stack for CrewAI
Every request between CrewAI and Better Stack is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Can my AI automatically acknowledge an incident so my phone stops ringing?
Yes! Running the acknowledge_incident capability pushes a verified API command halting escalation cycles (like SMS and phone calls) natively while you debug.
Is it possible to see the exact HTTP response body or headers that caused a monitor to fail?
Yes, pulling details via get_incident exposes the raw nested trace containing the root cause payloads and server errors Better Stack historically received when the check failed.
Can the agent create new monitors automatically?
No. The integration focuses safely on observation, alerting resolution, and tracking currently. Creation endpoints represent mutation vectors decoupled to ensure you preserve billing and account structure intentionally.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
The Movie Database (TMDb)
15 toolsSearch movies, TV shows, people, get details, cast, trailers, and discover content via TMDb API.
Kargo
10 toolsAutomate logistics and loading dock operations via Kargo — track shipments and sync data directly from your AI agent.
TestMonitor
10 toolsList QA projects, extract test runs, read user assignments, and fetch tracked issues strictly from your AI chat.
Grepsr
12 toolsAutomate web scraping via Grepsr — manage reports, trigger crawls, and retrieve data directly via AI.