API Documentation

REST API for notifications via Telegram and Max. Subscribers, OTP, broadcasts, forms, helpdesk.

MCP server for AI agents

The Zapnoty MCP server connects the notification service to AI agents (Claude, Cursor, ChatGPT) via the Model Context Protocol. The agent gets a set of ~60 tools and can create and configure a project, send messages, manage broadcasts and helpdesk — on behalf of the user.

Connecting

Server endpoint — https://mcp.zapnoty.com/mcp (JSON-RPC over HTTP).

Claude Desktop / Claude Code:

claude mcp add zapnoty https://mcp.zapnoty.com/mcp

Cursor / Continue / Goose — in the MCP servers config:

{
"mcpServers": {
"zapnoty": { "url": "https://mcp.zapnoty.com/mcp" }
}
}

How the agent works with a project

  1. zapnoty_create_virtual_project — creates a project, returns a temporary zn_virt_… key and accept_url.
  2. The user opens accept_url and clicks Accept — the key becomes a permanent zn_live_… key.
  3. zapnoty_check_status — the agent waits for the active status.
  4. Before Accept (zn_virt_) only configuration is available; sending messages and runtime — after Accept with zn_live_.

All tools except project creation and status check take an api_key parameter (zn_virt_… or zn_live_…).

tools/call → zapnoty_create_template
{
"api_key": "zn_virt_...",
"key": "welcome",
"text": "Hello, {{name}}!"
}

Available tools

MCP covers the entire /v1 API available by API key — ~60 tools grouped by resource:

  • Setup — templates, permissions, tags (full CRUD), webhook (single & multi-endpoint), auto-messages.
  • Scheduler — delayed messages, drip chains, recurring broadcasts.
  • Forms — CRUD for forms and delivery routes, reading submissions.
  • Helpdesk config — module settings, SLA, ticket types, canned responses, routing rules.
  • Runtime (after Accept) — sending messages, batch, broadcasts, OTP, events, auth sessions, helpdesk tickets.
  • Reading — subscribers, subscriber permissions, audit log, setup summary.

The tool set mirrors the REST API — see the «Management» section (API vs dashboard boundary). What is dashboard-only (team management, custom bot connection, API key regeneration) is not yet configurable via MCP.

Security

  • The agent cannot send messages until the user confirms the project with the Accept button.
  • The temporary zn_virt_ key has a 24-hour TTL and grants no runtime operations.
  • The permanent zn_live_ key is visible to the user in the dashboard and can be revoked.

Related sections

Webhooks — incoming events
Incoming events: subscription, delivery, broadcast, tickets, forms. HMAC-signed.
Virtual Projects — AI-driven setup
AI creates and configures a project for the user via MCP. The user only Accepts.
Custom Bots — your own bot (white-label)
Connect your own Telegram/Max bot: your name, welcome, commands and branding.