@vigiles-hq/mcp
v0.1.7
Published
Model Context Protocol server for Vigiles incident management. Lets AI assistants query your workspace monitors, incidents, deployments, and on-call rotation.
Maintainers
Readme
@vigiles-hq/mcp
MCP server for Vigiles — connect Claude, Cursor, or any MCP client to your uptime monitoring workspace.
Installation
Add to your MCP client config (Claude Desktop, Cursor, etc.):
{
"mcpServers": {
"vigiles": {
"command": "npx",
"args": ["-y", "@vigiles-hq/mcp"],
"env": {
"VIGILES_API_KEY": "vig_live_..."
}
}
}
}Getting an API key
- Sign in to Vigiles.
- Open Settings → Workspace → API tokens.
- Create a token and copy the value (shown once). It starts with
vig_live_. - Set it as
VIGILES_API_KEYin your MCP config.
Available tools
| Tool | Description |
|------|-------------|
| list_monitors | List monitors with name, URL, type, status, and last check time. |
| get_monitor | Full detail for one monitor: interval, regions, tags, and alert channels. |
| get_monitor_checks | Recent check results with status, response times, and regions. |
| get_monitor_uptime | Uptime percentage, check counts, and downtime over a period. |
| list_incidents | List incidents with status, affected monitors, and duration. |
| get_incident | Incident detail: timeline, acknowledgement, resolution notes, postmortem. |
| list_deployments | Recent deployments with version, time, and domain group. |
| get_on_call | Current on-call rotation and upcoming shifts per schedule. |
Configuration
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| VIGILES_API_KEY | Yes | — | Workspace API token (vig_live_...). |
| VIGILES_API_URL | No | https://api.vigileshq.com | API base URL (override for staging or self-hosted). |
Security
Workspace API tokens are workspace-scoped and read-only. This package only sends requests to the Vigiles API (api.vigileshq.com by default). Your monitoring data is never sent anywhere else.
License
Business Source License 1.1 — see LICENSE.md. Converts to Apache 2.0 on 2030-06-07.
