blue-matador-mcp-server
Official# Bluematador MCP Server
[](https://www.npmjs.com/package/blue-matador-mcp-server)
Connect your Bluematador monitoring to Claude Desktop and Claude Code **securely** with your credentials stored locally.
---
## š Quick Start
### Requirements
- **Node.js**: 16.x or higher
### Installation
Install the Bluematador MCP server as an npm package:
```bash
npm install -g blue-matador-mcp-server
```
š¦ [View on npm](https://www.npmjs.com/package/blue-matador-mcp-server)
### Configuration
1. Get your **API Key** and **Account ID** from [Bluematador Settings ā API Keys](https://app.bluematador.com/ur/app#/account/apikeys)
2. Open **Claude Desktop** ā **Settings** ā **Developer** ā **Edit Config**
3. Add the Bluematador MCP server to your configuration:
```json
{
"mcpServers": {
"bluematador": {
"command": "bluematador-mcp-server",
"env": {
"BLUEMATADOR_API_KEY": "your-api-key-here",
"BLUEMATADOR_ACCOUNT_ID": "your-account-id-here"
}
}
}
}
```
4. Save the file and restart Claude Desktop
---
## š„ļø Compatibility
### ā
Works With
- **Claude Desktop** (macOS, Windows, Linux)
- **Claude Code** (CLI tool)
- **Claude Dev** (VS Code extension)
### ā Does Not Work With
- Claude Web (claude.ai)
- ChatGPT or other AI platforms
---
## ⨠What You Can Do
Ask Claude to help with your Bluematador monitoring using natural language:
### š Cloud Integration Management
- Set up and manage AWS/Azure monitoring
- Enable, disable, or update integrations
- View integration status and troubleshoot issues
### š Monitoring & Alerts
- Check active alerts and events in real-time
- Query historical monitoring data
- Get infrastructure health summaries
- View metrics and performance data
### š Alert Management
- Create mute rules for specific alerts or resources
- Mute monitors by service type (SQS, RDS, EC2, etc.)
- Use wildcard patterns for bulk operations
- Control alert visibility and notifications
### š Notification Setup
- Configure Email, PagerDuty, OpsGenie
- Set up AWS SNS, VictorOps, SquadCast
- Manage ServiceNow integrations
- Control alert severity levels
### š„ Team & Project Management
- Invite team members
- Manage user permissions
- Organize monitoring by projects
---
## š Documentation
- **[API Reference](./docs/API-REFERENCE.md)** - Complete tool reference
---
## š Security & Privacy
- **Per-user credentials** - Each user provides their own API keys in their local configuration
- **Direct API calls** - All requests go directly to Bluematador's API
- **HTTPS only** - All connections are encrypted
- **Audit trail** - All actions logged in your Bluematador account
---
## š” Example Usage
Once connected, use natural language with Claude:
```
You: "Show me active Bluematador alerts"
You: "Create a mute rule for all SQS monitors in us-east-1"
You: "List my AWS integrations"
You: "Invite john@company.com as an admin"
You: "What EC2 instances have high CPU?"
```
---
## š ļø For Developers
If you want to contribute or run the server locally for development, see [DEV-README.md](./DEV-README.md)
---
## š License
MIT License - see [LICENSE](./LICENSE) for details
---
## š Support
- **Issues**: [GitHub Issues](https://github.com/bluematador/blue-matador-mcp-server/issues)
- **Documentation**: [Bluematador Docs](https://docs.bluematador.com)
- **MCP Protocol**: [Model Context Protocol](https://modelcontextprotocol.io)
---
**Made with ā¤ļø by Bluematador**
[Website](https://bluematador.com) ⢠[Documentation](https://docs.bluematador.com) ⢠[GitHub](https://github.com/bluematador)
TDQS
Scored across 41 tools
Each tool targets a distinct resource and action (e.g., create_aws_integration vs create_azure_integration, different notification types). Even similar tools like mute_monitors_by_service and mute_resources_by_wildcard have clear differentiation via description.
All tools follow a consistent verb_noun pattern in snake_case (e.g., 'list_integrations', 'create_pagerduty_notification', 'disable_integration'). No mixing of styles or unexpected abbreviations.
With 41 tools, the count is high but justified by the breadth of functionality: multiple integration types, notification channels, mute rules, events, and user management. Slightly above the ideal 3-15 range but not excessive for a monitoring platform.
The surface covers CRUD operations for integrations and notifications, event queries, mute rules, users, and projects. Minor gaps exist: no update for mute rules, no delete for users, and no direct tools for managing monitor definitions. Overall, core workflows are supported.