MCP Server for AI Assistants
Let Claude, Cursor, VS Code and other AI assistants check and manage your monitors.
Overview
Notifier runs a hosted Model Context Protocol server at https://notifier.so/mcp. Add it to your AI assistant with an API key and you can ask things like:
- "Is anything down right now?"
- "Add a monitor for https://example.com that checks every minute."
- "Pause the API monitor while I deploy, then turn it back on."
- "How many outages did the shop have this month, and why?"
1. Create an API Key
In the monitoring dashboard, go to Integrations → API keys → Create API key. Name it after the assistant, such as "Claude". Tick Read-only if the assistant should only look, not change anything. Copy the key (it starts with ntf_).
2. Add It to Your Assistant
Claude Code
claude mcp add --transport http notifier https://notifier.so/mcp \
--header "Authorization: Bearer ntf_your_key_here"
Cursor
Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"notifier": {
"url": "https://notifier.so/mcp",
"headers": { "Authorization": "Bearer ntf_your_key_here" }
}
}
}
VS Code (GitHub Copilot)
Add this to .vscode/mcp.json. VS Code asks for the key once and stores it securely:
{
"inputs": [
{ "type": "promptString", "id": "notifier-key", "description": "Notifier API key", "password": true }
],
"servers": {
"notifier": {
"type": "http",
"url": "https://notifier.so/mcp",
"headers": { "Authorization": "Bearer ${input:notifier-key}" }
}
}
}
Claude Desktop
Claude Desktop connects to remote servers with API keys through the small mcp-remote helper (needs Node.js). In Settings → Developer → Edit Config, add:
{
"mcpServers": {
"notifier": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://notifier.so/mcp", "--header", "Authorization:${NOTIFIER_AUTH}"],
"env": { "NOTIFIER_AUTH": "Bearer ntf_your_key_here" }
}
}
}
Restart Claude Desktop and Notifier's tools appear in the tools menu.
Other Clients
Any client that supports remote MCP servers over Streamable HTTP works. Use the URL https://notifier.so/mcp and send the header Authorization: Bearer ntf_... (or X-API-Key: ntf_...).
Tools
| Tool | What it does |
|---|---|
get_status_summary | How many monitors are up, down or paused, and details of anything down right now |
list_monitors | List monitors, filtered by status or search |
get_monitor | One monitor with uptime for 24h, 7d, 30d and 90d |
create_monitor | Add an HTTP, keyword, ping, port or DNS monitor |
update_monitor | Change name, URL, interval, alert channels or keyword |
pause_monitor / resume_monitor | Stop and restart checks, for example around a deploy |
delete_monitor | Delete a monitor and its history (marked destructive, so assistants ask first) |
get_response_times | Response times and min/avg/max for 1h to 365d |
list_incidents / get_incident | Outages with duration and why the check failed |
get_account | Plan, monitor limit and usage, fastest check interval |
Limits and Safety
- The assistant can do exactly what the key can do, on the team the key was created in. Use a read-only key if it should only look.
- Your plan's limits apply: monitor count, fastest check interval and alert channels.
- Rate limits are shared with the REST API: 30 requests a minute on Free, 300 on paid plans.
- Revoke the key under Integrations and the assistant loses access immediately.
Questions? Email support@notifier.so or use the chat on any page.