Streamable HTTP · Remote MCP MCP Server v1.61.0

Integración MCP

Conecta cualquier agente de IA compatible con MCP a tus monitores de PulseGuard: lee estadísticas de uptime, inspecciona incidentes y gestiona monitores mediante lenguaje natural.

Requisitos Previos

  • Una cuenta de PulseGuard con al menos un monitor configurado.
  • A PulseGuard API token — generate one under Profile → API Keys. Use a Read-only token for telemetry queries, or a Full Access token to create, update, pause, configure, and delete monitors on paid plans.
  • Node.js 18+ — required if you use the mcp-remote bridge for Claude Desktop. Download from nodejs.org. Verify with node -v. Not needed if you use the Connectors UI or Cursor/Windsurf.
  • Un cliente compatible con MCP. Clientes compatibles:
Cliente Versión mínima Notas
Claude Desktop 0.7.0+ UI de Conectores (OAuth) o mcp-remote (token Bearer)
Cursor 0.43.0+ Configuración → MCP → Agregar servidor
Windsurf 1.0.0+ Configuración → Cascade → MCP
Antigravity any Edit ~/.gemini/antigravity/mcp_config.json
Any SSE client MCP spec 2024-11-05+ Pass Authorization: Bearer header

Tipos de Token

PulseGuard uses Passport API tokens and OAuth access tokens. Two permission levels are available:

Tipo de Token Listar / Leer monitores Leer estadísticas e incidentes Crear monitores Pausar / Reanudar Delete via AI
Solo lectura
Acceso Completo

Full Access tokens carry the mcp:full ability. Read-only tokens carry the read ability. Full Access write actions require an eligible paid plan; monitor deletion also requires the exact monitor ID.

Instalación

El endpoint del servidor MCP es:

https://pulseguard.saniolabs.com/mcp

No se necesita archivo de configuración ni clave API: Claude Desktop gestiona el flujo OAuth automáticamente.

  1. 1 Open Claude Desktop → Settings → Integrations.
  2. 2 Click Add Integration and paste the MCP server URL:
https://pulseguard.saniolabs.com/mcp
  1. 3 Claude opens a browser window — log in to PulseGuard and click Authorize.
  2. 4 The integration appears in Claude Desktop. Ask "List my PulseGuard monitors" to verify.
OAuth starts from safe monitor access. Write actions require Full Access and an eligible paid plan; monitor deletion also requires the exact monitor ID. You can revoke access at any time from your Profile.

Uses the mcp-remote bridge to connect Claude Desktop via a Bearer token. Requires Node.js 18+.

Ruta del archivo de configuración

macOS ~/Library/Application Support/Claude/claude_desktop_config.json
Windows %APPDATA%\Claude\claude_desktop_config.json
Linux ~/.config/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "pulseguard": {
      "command": "npx",
      "args": [
        "mcp-remote@latest",
        "https://pulseguard.saniolabs.com/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_TOKEN"
      ]
    }
  }
}
Replace YOUR_API_TOKEN with a token from Profile → API Keys. Fully quit Claude Desktop (Cmd+Q / Alt+F4), then reopen.

Verify: ask Claude "List my PulseGuard monitors" — it should call list-monitors-tool and return your monitors.

Open or create ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):

Ruta del archivo de configuración

macOS / Linux ~/.cursor/mcp.json
Windows %USERPROFILE%\.cursor\mcp.json
Per-project .cursor/mcp.json
{
  "mcpServers": {
    "pulseguard": {
      "url": "https://pulseguard.saniolabs.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Verify: open Cursor Chat and type "List my PulseGuard monitors" — Cursor should invoke list-monitors-tool.

Open or create ~/.codeium/windsurf/mcp_config.json:

Ruta del archivo de configuración

macOS / Linux ~/.codeium/windsurf/mcp_config.json
Windows %USERPROFILE%\.codeium\windsurf\mcp_config.json
UI path Settings → Cascade → Add MCP Server
{
  "mcpServers": {
    "pulseguard": {
      "serverUrl": "https://pulseguard.saniolabs.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
Reload the Windsurf window after saving (Cmd/Ctrl+Shift+P → Reload Window).

Verify: in Cascade ask "List my PulseGuard monitors".

Open or create ~/.gemini/antigravity/mcp_config.json and add the pulseguard entry:

Ruta del archivo de configuración

macOS / Linux ~/.gemini/antigravity/mcp_config.json
Windows %USERPROFILE%\.gemini\antigravity\mcp_config.json
"pulseguard": {
  "serverUrl": "https://pulseguard.saniolabs.com/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_API_TOKEN"
  }
}
Replace YOUR_API_TOKEN with a token from Profile → API Keys.

Verify: ask Antigravity "List my PulseGuard monitors" — it should call list-monitors-tool and return your monitors.

Any MCP client that supports Streamable HTTP transport works. The server accepts JSON-RPC 2.0 POST requests with a single Authorization header.

# curl — verify the Streamable HTTP endpoint
curl -s -X POST \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl-test","version":"1.0"}}}' \
  https://pulseguard.saniolabs.com/mcp

A successful response returns a JSON-RPC result with serverInfo and capabilities. From there the MCP handshake is complete and tools are available.

Herramientas Disponibles

PulseGuard exposes read tools for monitor health, incidents, SSL, PageSpeed, status pages, charts, and notification channels. Paid plans can also create, edit, pause, resume, configure, and delete monitors safely.

list-monitors-tool

Token de lectura

Returns all monitors configured in the authenticated user's account.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}

No se requiere entrada.

Ejemplo de respuesta

[
  {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "name": "Production API",
    "url": "https://api.example.com",
    "status": "up",
    "type": "http",
    "check_interval": 300,
    "paused_at": null
  }
]

get-uptime-stats-tool

Token de lectura

Returns uptime percentage and average response time for a given time period. Use period to choose between "24h" or "30d" (default).

Esquema de entrada

{
  "type": "object",
  "required": ["monitor_id"],
  "properties": {
    "monitor_id": {
      "type": "string",
      "description": "UUID of the monitor"
    },
    "period": {
      "type": "string",
      "description": "\"24h\" or \"30d\" (default: \"30d\")"
    }
  }
}

Ejemplo de respuesta

{
  "monitor_name": "Production API",
  "status": "up",
  "period": "last 30 days",
  "uptime_percentage": "99.85%",
  "average_response_time_ms": 142,
  "total_pings_analyzed": 129600, // 30d × 24h × 60min × 3 pings/min
  "total_incidents": 3
}

get-monitor-incidents-tool

Token de lectura

Returns the 10 most recent incidents for a monitor, ordered by started_at descending.

Esquema de entrada

{
  "type": "object",
  "required": ["monitor_id"],
  "properties": {
    "monitor_id": {
      "type": "string",
      "description": "UUID of the monitor"
    }
  }
}

Ejemplo de respuesta

[
  {
    "id": 12,
    "monitor_id": "a1b2c3d4-...",
    "started_at": "2026-03-28T14:22:00.000000Z",
    "resolved_at": "2026-03-28T14:35:00.000000Z",
    "duration": 780,
    "root_cause": "Connection timeout"
  }
]

create-monitor-tool

Token de acceso completo

Creates a new HTTP or keyword monitor. Returns the created monitor object. Fails if the account's monitor limit is reached.

Esquema de entrada

{
  "type": "object",
  "required": ["name", "url"],
  "properties": {
    "name": {
      "type": "string",
      "description": "Display name, e.g. My API"
    },
    "url": {
      "type": "string",
      "description": "Full URL, e.g. https://api.example.com"
    },
    "type": {
      "type": "string",
      "enum": ["http", "keyword"],
      "description": "Default: http"
    },
    "check_interval": {
      "type": "integer",
      "description": "Seconds between checks. Default: 300"
    },
    "timeout": {
      "type": "integer",
      "description": "Seconds before marking down. Default: 10"
    },
    "monitor_ssl": {
      "type": "boolean",
      "description": "Monitor SSL cert. Default: false"
    },
    "notify_uptime": {
      "type": "boolean",
      "description": "Email alerts. Default: true"
    },
    "monitor_domain": {
      "type": "boolean",
      "description": "Monitor domain expiry. Default: false"
    }
  }
}

Ejemplo de respuesta

Monitor created successfully.

{
  "id": "f7e6d5c4-b3a2-1098-fedc-ba9876543210",
  "name": "Staging API",
  "url": "https://staging.example.com",
  "type": "http",
  "status": "pending",
  "check_interval": 300,
  "timeout": 10,
  "monitor_ssl": false,
  "notify_uptime": true,
  "monitor_domain": false
}

toggle-monitor-pause-tool

Token de acceso completo

Pauses or resumes a monitor. Pass pause: true to stop checks, pause: false to resume. Paused monitors show status "paused"; resumed monitors revert to "pending" until the next check.

Esquema de entrada

{
  "type": "object",
  "required": ["monitor_id", "pause"],
  "properties": {
    "monitor_id": {
      "type": "string",
      "description": "UUID of the monitor to modify"
    },
    "pause": {
      "type": "boolean",
      "description": "true to pause, false to resume"
    }
  }
}

Ejemplo de respuesta (pausar)

Monitor paused successfully.

Ejemplo de respuesta (reanudar)

Monitor unpaused successfully.

list-all-incidents-tool

Token de lectura

Returns recent incidents across all of the user's monitors in a single call. Incidents are sorted by started_at descending and include monitor_name for context.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Max incidents per monitor (1–50). Default: 10"
    }
  }
}

All parameters optional. Omit limit to use the default of 10.

Ejemplo de respuesta

[
  {
    "monitor_name": "Production API",
    "monitor_id": "a1b2c3d4-...",
    "incident_id": 42,
    "started_at": "2026-03-28T14:22:00.000000Z",
    "resolved_at": "2026-03-28T14:35:00.000000Z",
    "duration": "13m 0s",
    "root_cause": "Connection timeout"
  },
  {
    "monitor_name": "Staging API",
    "monitor_id": "b2c3d4e5-...",
    "incident_id": 38,
    "started_at": "2026-03-27T09:10:00.000000Z",
    "resolved_at": "2026-03-27T09:11:30.000000Z",
    "duration": "1m 30s",
    "root_cause": "Gateway Timeout"
  }
]

Ejemplos de Prompts

Cópialos directamente en tu agente de IA. El agente llamará a las herramientas apropiadas automáticamente.

1. Listar todos los monitores Leer token

List all my PulseGuard monitors and show me their current status and check intervals.

2. Estadísticas de uptime Leer token

What is the uptime percentage and average response time for my Production API monitor? Give me the monitor ID too.

3. Diagnóstico de incidentes Leer token

Fetch the last 10 incidents for monitor ID a1b2c3d4-e5f6-7890-abcd-ef1234567890 and tell me if there is a recurring failure pattern based on root_cause and timing.

4. Comparación entre monitores Leer token

List all my monitors, then fetch uptime stats for each one and rank them by average response time from fastest to slowest.

5. Creación masiva Acceso Completo token

Create three HTTP monitors: "API Gateway" at https://api.example.com, "Auth Service" at https://auth.example.com, and "Dashboard" at https://app.example.com. Set check_interval to 60 for all three and enable SSL monitoring.

Solución de Problemas

401 Error de autenticación: "No autenticado" o HTTP 401

The Authorization header is missing or malformed.

  • Confirm the token value starts with no extra whitespace.
  • The header must be exactly Authorization: Bearer <token>.
  • Regenerate the token in Profile → API Keys if unsure.
403 Error "no tiene permisos de escritura completos"

You are using a Read-only token and calling a write tool (create-monitor-tool or toggle-monitor-pause-tool).

Generate a Full Access token in Profile → API Keys and update your client config.

404 Herramienta no encontrada / el agente no conoce herramientas de PulseGuard

The client has not completed the MCP initialize handshake, or has a stale tool cache.

  • Claude Desktop / Windsurf: fully quit and relaunch the app.
  • Cursor: open the MCP settings panel and click Reconnect.
  • Verify the config file has no JSON syntax errors (trailing commas are not allowed).
[ ] Lista de monitores vacía o "Monitor no encontrado"

The tool only returns monitors owned by the token's user.

  • Log into PulseGuard and confirm monitors exist on the dashboard.
  • If passing a monitor_id, copy it directly from the URL or list-monitors-tool output — IDs are UUIDs.
  • No ping data for stats: the monitor must have at least one completed check cycle.
ERR Conexión rechazada / servidor sin respuesta

Check the URL in your config:

https://pulseguard.saniolabs.com/mcp
  • No trailing slash.
  • No /api/ prefix — the endpoint is at /mcp directly.
  • Run the curl command from the Generic HTTP tab above to confirm connectivity from your machine.

Registro de Cambios

v1.9.0

2026-04-02

Unified Navigation & New Tools

  • Unified marketing navigation across all pages (x-marketing-nav)
  • Added list-all-incidents-tool for bulk incident reporting
  • Monitor deletion is now available only with Full Access, an eligible paid plan, and the exact monitor ID
  • App logo now links to homepage; simplified auth-aware CTAs
  • Removed forced dashboard redirect for logged-in users
v1.0.0

2026-03-30

Initial release

  • SSE-based Remote MCP server at /api/mcp/sse
  • 5 monitors & stats tools

MCP server version: 1.61.0 · Protocol: MCP 2024-11-05 · Transport: SSE