Quismon MCP Server

The Quismon MCP (Model Context Protocol) server enables AI agents like Claude to interact with your Quismon monitoring platform programmatically. This allows AI assistants to create checks, view incidents, trigger immediate checks, and manage alert rules through natural language conversations.

What is MCP?

The Model Context Protocol (MCP) is a standardized way for AI models to interact with external tools and resources. It provides:

• Resources: Read-only data that AI can query (like checking the status of your monitors)
• Tools: Actions the AI can perform (like creating new checks)

---

Configuration

Set the environment variable API_URL to point to the Quismon API:

export API_URL=https://api.quismon.com
export MCP_PORT=8081

Authentication

All requests require your Quismon API key. Get your API key from: https://app.quismon.com/settings/api-keys

Include it in requests using either:

• Authorization: Bearer YOUR_API_KEY header
• X-API-Key: YOUR_API_KEY header

Using with Claude Desktop

Add this to your Claude Desktop config:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "quismon": {
      "url": "https://mcp.quismon.com",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}

Replace YOUR_API_KEY_HERE with your actual API key from the Quismon dashboard.

---

Available Resources

Resources are read-only data that AI agents can query to understand the state of your monitoring.

quismon://checks

Lists all monitoring checks in your account.

Example Response:

[
  {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "name": "API Health Check",
    "type": "https",
    "config": {"url": "https://api.example.com/health"},
    "interval_seconds": 60,
    "regions": ["fr-par-1", "na-east-ewr"],
    "enabled": true,
    "health_status": "healthy"
  }
]

quismon://incidents

Lists all active (unresolved) incidents.

Example Response:

[
  {
    "id": "660e8400-e29b-41d4-a716-446655440001",
    "check_id": "550e8400-e29b-41d4-a716-446655440000",
    "severity": "critical",
    "started_at": "2026-02-18T10:30:00Z",
    "resolved_at": null,
    "acknowledged_at": null,
    "details": {"error": "Connection timeout"}
  }
]

quismon://alerts

Lists all alert rules.

Example Response:

[
  {
    "id": "770e8400-e29b-41d4-a716-446655440002",
    "check_id": "550e8400-e29b-41d4-a716-446655440000",
    "name": "API Down Alert",
    "condition": {"failure_threshold": 3},
    "enabled": true
  }
]

quismon://checks/{check_id}

Get details for a specific check by ID.

Available Tools

Tools allow AI agents to perform actions on your Quismon account.

create_check

Create a new monitoring check.

Parameters:

Name	Type	Required	Description
name	string	Yes	Name of the check
type	string	Yes	Check type: http, https, ping, tcp, dns, ssl, smtp-imap, throughput, http3
url	string	No	URL to check (for HTTP/HTTPS checks)
interval_seconds	integer	No	Check interval (default: 60)
regions	array	No	List of regions (default: ["fr-par-1"])
enabled	boolean	No	Enable the check (default: true)

Example:

{
  "name": "My API Check",
  "type": "https",
  "url": "https://api.example.com/health",
  "interval_seconds": 120,
  "regions": ["fr-par-1", "na-east-ewr"]
}

trigger_check

Trigger immediate execution of a check (bypassing the schedule).

Parameters:

Name	Type	Required	Description
check_id	string	Yes	ID of the check to trigger

Example:

{
  "check_id": "550e8400-e29b-41d4-a716-446655440000"
}

acknowledge_incident

Acknowledge an incident to indicate someone is working on it.

Parameters:

Name	Type	Required	Description
incident_id	string	Yes	ID of the incident to acknowledge

Example:

{
  "incident_id": "660e8400-e29b-41d4-a716-446655440001"
}

create_alert_rule

Create an alert rule for a check.

Parameters:

Name	Type	Required	Description
check_id	string	Yes	ID of the check
name	string	Yes	Name of the alert rule
failure_threshold	integer	No	Failures before alert (default: 3)
notification_channels	array	No	Notification channel IDs

Example:

{
  "check_id": "550e8400-e29b-41d4-a716-446655440000",
  "name": "Critical Alert",
  "failure_threshold": 2
}

---

Example Conversations

Checking Monitor Status

You: "What's the status of my monitoring checks?"

Claude: Queries quismon://checks resource

You have 5 active checks:

• API Health Check (https): healthy, checking every 60s from 2 regions
• Database Ping (ping): healthy, checking every 30s
• Website SSL (ssl): healthy, certificate expires in 45 days
• DNS Resolution (dns): healthy
• SMTP Server (tcp): unhealthy - last check failed

Creating a New Check

You: "Create a new HTTPS check for https://shop.example.com checking every 5 minutes"

Claude: Uses create_check tool

Created check "shop.example.com" with ID abc123.... It will check https://shop.example.com every 300 seconds from the default region. Would you like me to add more regions or set up alerting?

Investigating an Incident

You: "Are there any active incidents?"

Claude: Queries quismon://incidents resource

Yes, there's 1 active incident:

• SMTP Server check has been failing since 10:30 AM
• Severity: critical
• Error: Connection timeout

Would you like me to acknowledge this incident or trigger an immediate recheck?

---

API Reference

All endpoints require authentication via API key.

List Resources

GET /mcp/resources
Authorization: Bearer YOUR_API_KEY

Returns a list of available MCP resources.

Get Resource

GET /mcp/resources/{uri}
Authorization: Bearer YOUR_API_KEY

Returns the contents of a specific resource.

List Tools

GET /mcp/tools
Authorization: Bearer YOUR_API_KEY

Returns a list of available MCP tools with their input schemas.

Execute Tool

POST /mcp/tools/{tool_name}
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{...input parameters...}

Executes a tool and returns the result.

---

Security Considerations

• Keep your API key secure - it provides full access to your Quismon account
• The MCP server requires authentication for all operations
• Consider using API keys with limited scopes when available

Building

cd quismon-mcp
go build -o quismon-mcp cmd/mcp/main.go

Running

export API_URL=https://api.quismon.com
export MCP_PORT=8081
./quismon-mcp

The server exposes these endpoints:

• GET /health - Health check endpoint (no auth required)
• GET /mcp/resources - List available resources (auth required)
• GET /mcp/resources/{uri} - Get a specific resource (auth required)
• GET /mcp/tools - List available tools (auth required)
• POST /mcp/tools/{name} - Execute a tool (auth required)