# SigNoz MCP for AI Agents AI Agent Connect

> SigNoz MCP lets you manage your infrastructure alerts directly through your AI agent. Stop digging through the SigNoz UI to create or update rules. Use this Connector to list, create, update, and delete alert rules, plus verify your service account permissions instantly. It's the fastest way to handle observability tasks without leaving your editor.

## Overview
- **Category:** cloud-infrastructure
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_RowtOWZVlXUOmyvniUEYGILOZp4nB3dMT11prDGT/ai-agent-connect
- **Tags:** alerting, infrastructure-monitoring, open-source, telemetry, incident-response

## Description

SigNoz connects your observability stack to your AI agent so you can manage alerts without jumping through hoops. Instead of navigating complex dashboards to set thresholds, you can just tell your agent what needs to happen. This Connector handles the heavy lifting of updating your monitoring rules, letting you stay focused on the actual infrastructure. It's part of the Vinkius catalog, making it easy to plug into your existing workflow with Claude, Cursor, or Windsurf. You get to audit your current setup, remove old rules that are just creating noise, and build out new monitoring for your services through simple conversation. It's about getting the job done faster by removing the manual data entry from your daily routine.

## Tools

### create_rule
Create a new alert rule with specific conditions. This helps you build out your monitoring stack quickly.

### delete_rule
Delete an alert rule from your instance. Use this to prune old alerts and keep your environment tidy.

### get_service_account_me
Get current service account details. This helps you verify your API key permissions and connectivity.

### list_rules
Retrieve all configured alert rules. Use this to audit your entire alerting setup in one go.

### update_rule
Update an existing alert rule. This is perfect for tweaking thresholds on the fly without manual UI edits.

## Prompt Examples

**Prompt:** 
```
List all alert rules in my SigNoz instance.
```

**Response:** 
```
I've retrieved 8 alert rules from your SigNoz instance. Here is the current list:

| Rule Name | ID | Status |
| :--- | :--- | :--- |
| High CPU Usage | alert-01 | Active |
| Database Latency | alert-02 | Active |
| Service 5xx Errors | alert-03 | Active |
| 
| ... (5 more rules) |

Would you like to see the specific thresholds for any of these?
```

**Prompt:** 
```
Show me the details of my current service account.
```

**Response:** 
```
Your API key is valid. Here are your current account details:

* **Account Name:** Monitoring-Admin
* **Account ID:** sa-99283
* **Permissions:** 
    * Alerts: Read/Write
    * Dashboards: Read

Your connection to the SigNoz instance is active.
```

**Prompt:** 
```
Delete the alert rule with ID 'alert-123'.
```

**Response:** 
```
The alert rule **alert-123** has been successfully deleted from your SigNoz instance. Your active rule list has been updated.
```

## Capabilities

### Create new alert rules
Generate specific thresholds and conditions for your services using natural language.

### List all active rules
Get a full view of your monitoring environment in a single request.

### Update existing rules
Modify thresholds and conditions for alerts that are already live.

### Delete stale rules
Remove redundant or outdated alerts to keep your monitoring environment clean.

### Verify account permissions
Check your service account status and API key access instantly.

## Use Cases

### The Deployment Cleanup
An engineer just finished a rollout and needs to remove 10 old alerts. They ask the agent to delete specific rules to keep the dashboard clean.

### The Emergency Tweak
A service is flapping. The SRE asks the agent to update the threshold on a specific high-latency rule to stop the noise.

### The New Service Onboarding
A developer wants to monitor a new microservice. They tell the agent to create a rule for 5xx errors using the create_rule tool.

### The Audit Check
A platform lead needs to see what alerts are active in production. They use list_rules to get a full inventory.

## Benefits

- Stop manual UI navigation by using list_rules to see every active alert in your instance instantly.
- Speed up deployments by using create_rule to set up new monitoring thresholds as you launch services.
- Keep your monitoring environment clean by using delete_rule to remove old or redundant alerts.
- Adjust live thresholds quickly with update_rule when you need to tune your alerting during an incident.
- Confirm your setup is correct using get_service_account_me to check API permissions without hunting for settings.

## How It Works

The bottom line is you manage your entire SigNoz alerting stack through chat instead of clicking through a dashboard.

1. Connect your SigNoz Instance URL and API Key to the Connector.
2. Open your AI client and describe the alert change you need.
3. Receive a confirmation that the rule is created, updated, or removed.

## Frequently Asked Questions

**Can I use the SigNoz MCP to manage my alerts?**
Yes, this Connector lets you manage your SigNoz alert rules through natural conversation with your AI agent. You can create, update, and delete rules without leaving your current workspace.

**How does the SigNoz MCP help with infrastructure monitoring?**
It streamlines how you interact with your monitoring stack. Instead of manual UI navigation, you can use your AI agent to audit rules and adjust thresholds on the fly.

**Can I create new rules with the SigNoz MCP?**
You can. Just tell your AI agent what conditions and thresholds you need for a new alert, and the Connector will handle the creation within your SigNoz instance.

**How do I update existing thresholds using SigNoz MCP?**
You can ask your agent to update a specific rule by describing the new threshold or condition. The Connector will apply those changes to your SigNoz configuration immediately.

**Does the SigNoz MCP support auditing my monitoring stack?**
Yes, you can use it to pull a complete list of all configured alert rules. This makes it much easier to audit your environment and find stale rules that need pruning.

**Can I use the SigNoz MCP to check my API permissions?**
Yes, the Connector can verify your current service account details and API key permissions. This helps ensure your agent has the correct access to your SigNoz instance.

**Can I list all my current alert rules from SigNoz?**
Yes! Use the `list_rules` tool to fetch all alert rules configured in your SigNoz instance, including their conditions and thresholds.

**How do I verify if my API key is working correctly?**
You can use the `get_service_account_me` tool. It validates your current API key and retrieves the associated service account details.

**Is it possible to create a new alert rule via chat?**
Absolutely. Use the `create_rule` tool by providing the required JSON payload containing the alert type, condition, and thresholds.