blue-matador-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLUEMATADOR_API_KEY | Yes | Your Bluematador API key | |
| BLUEMATADOR_ACCOUNT_ID | Yes | Your Bluematador account ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_aws_integrationB | Create a new AWS integration in Bluematador |
| create_azure_integrationB | Create a new Azure integration in Bluematador |
| list_integrationsA | List all integrations for a Bluematador account |
| update_aws_integrationC | Update an existing AWS integration |
| update_azure_integrationC | Update an existing Azure integration |
| enable_integrationC | Enable a Bluematador integration |
| disable_integrationC | Disable a Bluematador integration |
| delete_integrationC | Delete a Bluematador integration |
| get_opened_eventsC | Get Bluematador events that were opened within a time period |
| get_active_eventsB | Get currently active Bluematador events |
| get_active_events_summaryB | Get summary of active events for the last 30 days |
| list_projectsA | List all Bluematador projects for an account |
| list_usersA | List all users in a Bluematador account |
| invite_usersB | Invite users to a Bluematador account |
| list_notificationsB | List all notification integrations for an account |
| create_email_notificationB | Create an email notification integration |
| create_pagerduty_notificationC | Create a PagerDuty notification integration |
| enable_notificationC | Enable a notification integration |
| disable_notificationC | Disable a notification integration |
| delete_notificationB | Delete a notification integration |
| list_mute_rulesB | List mute rules for an account |
| create_mute_ruleC | Create a mute rule to suppress alerts |
| get_mute_regionsA | Get available AWS and Azure regions for mute rules |
| create_opsgenie_notificationC | Create an OpsGenie notification integration |
| create_sns_notificationC | Create an AWS SNS notification integration |
| create_victorops_notificationC | Create a VictorOps notification integration |
| create_squadcast_notificationC | Create a SquadCast notification integration |
| create_servicenow_notificationC | Create a ServiceNow notification integration |
| update_email_notificationC | Update an email notification integration |
| update_pagerduty_notificationC | Update a PagerDuty notification integration |
| update_opsgenie_notificationB | Update an OpsGenie notification integration |
| update_sns_notificationC | Update an AWS SNS notification integration |
| update_victorops_notificationC | Update a VictorOps notification integration |
| update_squadcast_notificationB | Update a SquadCast notification integration |
| update_servicenow_notificationC | Update a ServiceNow notification integration |
| get_metricsB | Query Bluematador metrics data |
| get_mute_monitorsC | Get available monitors for mute rules |
| get_mute_resourcesC | Get available resources for mute rules with pagination |
| delete_mute_ruleC | Delete a mute rule |
| mute_monitors_by_serviceA | Mute monitors for specific services (e.g., SQS, RDS, EC2) by creating a targeted mute rule |
| mute_resources_by_wildcardB | Mute monitors for resources using wildcard patterns (e.g., "sqs-", "-prod", "app-*-db") |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.