Ray notifications
Server Details
Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- gege-mn/ray-mcp
- GitHub Stars
- 0
- Server Listing
- Ray: Your Notification Infra
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 21 tools
Each tool targets a distinct resource or lifecycle stage, and potentially close pairs like send_notification vs test_send_template and get_send_status vs list_feed_notifications are explicitly differentiated in their descriptions. There are no ambiguous duplicate operations.
Almost every tool follows a snake_case verb_noun convention such as list_templates, update_webhook, and get_send_status. whoami is the only clear deviation, which is minor and conventional.
21 tools is heavy relative to the ideal 3-15 range, but the surface spans several real subdomains: templates, webhooks, sending, feeds, stats, usage, docs, and identity. Each tool maps to a distinct operation, so the count is slightly over but reasonable for the scope.
The set covers the core notification workflow end to end: channel discovery, template creation/editing/publishing/archiving, sending, test sends, delivery status, in-app feeds, click stats, webhook lifecycle, usage, and identity. Minor gaps remain around campaign management, direct send-history listing, and hard template deletion, though archive/unarchive and read_docs provide workarounds.
Available Tools
21 toolsarchive_templateArchive templateADestructiveIdempotentInspect
Archive a template (POST /templates/{id}/archive; write scope). Sends that reference it fail until it is restored with unarchive_template; its name stays reserved meanwhile. Confirm with the user first if it may be in production use.
Inputs: templateId (required).
create_templateCreate templateAInspect
Create a template (POST /templates; write scope). channelKind is permanent and must match the channels you'll send through (list_channels templateKind). It is saved as an unpublished draft unless publish: true; sending by templateId needs a published version (publish_template). Names are unique per workspace including archived templates: a collision returns 409, so unarchive_template the old one instead. Returns { id, requiredParams }. Designed (drag-and-drop) email templates can only be made in the dashboard.
Inputs: name (required), content (required), logTitle (required), channelKind (required), +4 more.
create_webhookCreate webhookAInspect
Create an outbound webhook that Ray POSTs signed event payloads to (POST /tenant-webhooks; write scope; Pro plan or higher, otherwise 403). The URL must be public HTTPS. The response contains the signing secret exactly once: show it to the user to store (e.g. as an env var), since it can't be read again, only rotated with update_webhook. Read the webhooks docs page for the signature scheme.
Inputs: url (required), name (required), events (required).
delete_webhookDelete webhookADestructiveIdempotentInspect
Delete (archive) a webhook so it receives no more events (DELETE /tenant-webhooks/{id}; write scope). It cannot be restored through the API; confirm with the user first.
Inputs: webhookId (required).
get_click_statsGet click statsARead-onlyIdempotentInspect
Email link click counts grouped by destination URL (GET /clicks) for a sendId, a campaignId, or both (at least one is required). Only links from email sends made with trackClicks: true are counted.
Inputs: sendId, campaignId.
get_send_statusGet send statusARead-onlyIdempotentInspect
Delivery status of a send (GET /sends/{id}): aggregate counts per status over the whole send (pending, claimed, delivered, failed_retryable, failed_terminal, suppressed) plus one page of per-recipient delivery rows including provider errors. Right after sending, rows are usually pending; check again after a few seconds. Feed-only sends have no rows. For more rows, pass the returned nextCursor as cursor.
Inputs: sendId (required), limit, cursor.
get_templateGet templateARead-onlyIdempotentInspect
Get one template with its published version and its current draft (GET /templates/{id}): content, logTitle/logDescription, requiredParams a send must supply, and paramOverrides. Read this before update_template_draft, which needs the full body.
Inputs: templateId (required).
get_usageGet plan and usageARead-onlyIdempotentInspect
The workspace's plan, subscription status and this calendar month's usage against the monthly quota (GET /billing/subscription). used/remaining are null on unmetered plans. On a hard-capped plan, sends beyond the quota fail with HTTP 402 quota_exceeded.
Inputs: no named parameters.
get_webhookGet webhookARead-onlyIdempotentInspect
Get one outbound webhook (GET /tenant-webhooks/{id}) including its delivery health (consecutiveFailures, lastDeliveryAt, lastFailureAt, lastError).
Inputs: webhookId (required).
list_channelsList channelsARead-onlyIdempotentInspect
List the delivery channels configured in this workspace (GET /channels). Call this FIRST before sending: each entry's id is the channelConfigId for send_notification and test_send_template, kind is the channel type (ses_email, smtp_email, fcm_push, slack_webhook, discord_webhook, telegram_bot, twilio_sms, sendsms_mn, generic_webhook), templateKind is the template channelKind it accepts, and recipientSchema is the exact JSON Schema of the recipient it expects. Channels and their provider credentials are set up in the Ray dashboard, not through this API; if the list is empty, ask the user to add one there.
Inputs: no named parameters.
list_feed_notificationsList feed notificationsARead-onlyIdempotentInspect
Read one end user's in-app notification feed (GET /notifications): the entries created by sends with feed or showInFeed. This is what an in-app inbox would show, not delivery status (use get_send_status for that). Paginate by passing nextCursor back as cursor.
Inputs: externalUserId (required), after, limit, before, +3 more.
list_templatesList templatesARead-onlyIdempotentInspect
List message templates (GET /templates): id, name, folder, channelKind, and publishedVersionId (null = never published, so it cannot be sent by templateId yet). Archived templates are hidden unless includeArchived is true. Use get_template for content and required params.
Inputs: folder, includeArchived.
list_webhooksList webhooksARead-onlyIdempotentInspect
List the workspace's outbound event webhooks (GET /tenant-webhooks): url, subscribed events, enabled flag and delivery health (consecutiveFailures, lastError). Signing secrets are never returned.
Inputs: includeArchived.
publish_templatePublish templateAInspect
Publish a template's current draft as its new live version (POST /templates/{id}/publish; write scope). Sends by templateId use it immediately. Fails if there is no draft or the template is archived.
Inputs: templateId (required).
read_docsRead Ray docsARead-onlyIdempotentInspect
Read Ray's documentation as markdown. With no slug it returns the index (llms.txt) listing every page; then pass a page slug, i.e. the path after /docs/ without .md, such as sending, templates, idempotency, errors, rate-limits, webhooks, status-and-feeds or channels/telegram. Use it for anything the tool descriptions don't cover.
Inputs: slug.
send_notificationSend notificationAInspect
Send a notification (POST /send; needs a write-scoped key). Returns { sendId } with HTTP 202: delivery is asynchronous, so check the outcome with get_send_status. Use exactly one mode:
Single:
channelConfigId+recipient.Fan-out:
channelConfigId+targets(1-1000{ recipient, externalUserId? }), one channel, one sendId.Multi-channel:
deliveries(1-10, each with its ownchannelConfigId,recipientandtemplateIdorcontent) for ONE person over several channels; addfeed+externalUserIdfor a single in-app feed entry.Feed-only:
feed(withtitle) +externalUserIdand no channel: an in-app notification only. In modes 1-2 give exactly one oftemplateId(a published template, plusparams) or inlinecontent; in mode 3 that choice is made per delivery. Get channel ids and each recipient shape from list_channels first. PassidempotencyKeywhenever a retry must not deliver twice.
Inputs: feed, params, content, targets, +13 more.
test_send_templateTest-send templateAInspect
Send a real test of a template's PUBLISHED version to one recipient (POST /templates/{id}/test-send; write scope). It goes through the provider for real, so use a recipient the user controls. Test sends don't count toward the monthly quota (a small daily allowance applies instead) and never appear in feeds. Returns { sendId } for get_send_status.
Inputs: recipient (required), templateId (required), channelConfigId (required), params.
unarchive_templateUnarchive templateAIdempotentInspect
Restore an archived template (POST /templates/{id}/unarchive; write scope). This is how to reclaim a name held by an archived template instead of creating a new one.
Inputs: templateId (required).
update_template_draftUpdate template draftAInspect
Replace a template's draft (PATCH /templates/{id}; write scope). This is a full replacement, not a partial patch: pass content, logTitle, logDescription and paramOverrides as they should end up (get_template first). name, folder and channelKind are required for validation but not changed (channelKind must equal the original). Live sends keep using the published version until you publish, either with publish: true here or publish_template. Fails on archived templates.
Inputs: name (required), content (required), logTitle (required), templateId (required), +5 more.
update_webhookUpdate webhookAInspect
Change a webhook (PATCH /tenant-webhooks/{id}; write scope). Only the fields you pass change; pass at least one. rotateSecret: true issues a new signing secret, returned once in the response, and the old secret stops verifying immediately, so the receiving service must be updated at the same time.
Inputs: webhookId (required), url, name, events, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Send notifications, manage templates, and configure integrations with Courier.
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Send, search, and manage notifications, accounts, and push preferences
Send WhatsApp messages and templates, manage chats, contacts, broadcasts and AI agents.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables sending rich notifications to Discord and/or Slack webhooks with automatic service detection, retry logic, and support for embeds, blocks, and attachments. Provides secure webhook management with comprehensive input validation and rate limiting.3TypeScriptMIT
- AlicenseNot gradedqualityCmaintenanceUnified notification MCP server with 36 tools to send messages across 23 channels — Email, SMS, Slack, Telegram, Discord, Teams, WhatsApp, Firebase Push, and more.9MIT
- AlicenseAqualityBmaintenanceEnables agents and applications to send notifications through configurable channels such as Telegram or a JSONL file, with queued delivery, status tracking, idempotency, and event-based routing.2MIT
- FlicenseNot gradedqualityCmaintenanceEnables agents to send structured notifications to recipients via configurable channels (initial SMTP provider) without exposing delivery addresses or credentials, with tools for listing recipients, listing channels, and sending notifications.-
Glama MCP Gateway
Add one secure layer between your agents and this server.