MCP / AI IntegrationModel Context Protocol server for AI assistants and agents

Overview

WebSignal exposes an MCP (Model Context Protocol) server, allowing AI assistants, copilots, and autonomous agents to interact with your monitoring data programmatically. MCP provides a structured, tool-based interface specifically designed for LLM consumption.

With MCP, your AI assistant works on your monitoring through 28 tools over a standard JSON-RPC protocol over HTTP. 15 of them change something in your account rather than only reading it, which is why a write needs both a plan that allows it and a workspace role that allows it. Every one of them is listed under Tools below, under the service it belongs to, with the description the server itself publishes for it - which is the only description of this tool list that cannot fall behind the list.

Connection

Authentication

Most MCP tools require OAuth 2.0 Bearer tokens, identical to the REST API. The server supports:

• Authorization Code + PKCE: for interactive AI clients
• Device Code: for CLI-based agents and headless environments

Workspace scoping

Monitors, incidents, and alerts belong to a workspace, so tools that read or change them resolve against exactly one. Send the workspace id in the X-Workspace-Id header on every MCP request:

Authorization: Bearer <access_token>
X-Workspace-Id: 0YYMZFSd5AA

If you omit it, the server falls back to your only workspace when you belong to exactly one, which is what most solo accounts see; anyone who belongs to several should send the header so the agent doesn’t act on the wrong one. Fetch the ids from GET /api/v1/workspaces, and see Workspaces for the role model that governs which tools a member may use.

Quick Start

1. Initialize MCP Session

POST https://api.websignal.io/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {
    "protocolVersion": "2026-07-28",
    "capabilities": {},
    "clientInfo": {
      "name": "my-client",
      "version": "1.0.0"
    }
  }
}

2. List Available Tools

POST https://api.websignal.io/mcp
Content-Type: application/json
Mcp-Session-Id: <from initialize response>

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/list"
}

3. Call a Tool

POST https://api.websignal.io/mcp
Content-Type: application/json
Authorization: Bearer <token>
Mcp-Session-Id: <from initialize response>

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "list_monitors",
    "arguments": {}
  }
}

Tools

Capabilities