The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Ray notifications listing page.
MCP server for Ray, the notification delivery API. It lets Claude, Cursor, VS Code, Windsurf, Codex, Zed and any other MCP client send notifications and manage templates, delivery webhooks and usage in your Ray workspace.
Ray here is the multi-tenant notification API from gege.mn (email via Amazon SES or SMTP, Firebase push, Slack, Discord, Telegram, SMS via Twilio or sendsms.mn, generic webhooks and an in-app feed). It is not the Ray distributed computing framework.
Ray runs an MCP server for you. There are two ways to connect, with the same tools:
| Hosted (recommended) | Local (this package) | |
|---|---|---|
| What runs | Nothing on your machine | npx -y @gege-mn/ray-mcp, a stdio process |
| Endpoint | https://ray-api.gege.mn/mcp (Streamable HTTP) | Bridges to the hosted endpoint |
| Auth | Authorization: Bearer <key> header | RAY_API_KEY environment variable |
| Use it when | Your client supports remote servers with custom headers | Your client only runs stdio servers (e.g. Claude Desktop config file), or you prefer env vars over headers |
This package is a thin bridge: it connects to the hosted endpoint with your key and mirrors its tool list, descriptions and instructions, so new tools appear without upgrading the package. All validation, scopes, rate limits and quota are enforced by Ray's API.
ck_live_ and is shown only once.
read scope: status, templates, usage, docs.write scope: also needed to send, create or change templates, and manage webhooks.The examples below use ck_live_... as a placeholder. Keep real keys out of version control.
Hosted:
Local:
Add --scope user to make it available in every project. Check the connection with claude mcp get ray.
Edit claude_desktop_config.json (Settings → Developer → Edit Config; macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json), then fully restart Claude Desktop:
.cursor/mcp.json in a project, or ~/.cursor/mcp.json for all projects.
Hosted:
Local:
Cursor can read the key from your environment instead: "Authorization": "Bearer ${env:RAY_API_KEY}".
VS Code's mcp.json (.vscode/mcp.json in a workspace, or MCP: Open User Configuration) uses a top-level servers key and can prompt for the key so it isn't stored in the file:
Local variant: replace the server entry with { "type": "stdio", "command": "npx", "args": ["-y", "@gege-mn/ray-mcp"], "env": { "RAY_API_KEY": "${input:ray-api-key}" } }.
~/.codeium/windsurf/mcp_config.json (Windsurf calls the URL field serverUrl and supports ${env:VAR}):
Local: use the same command / args / env entry as in the Cursor example.
~/.codex/config.toml, local:
Hosted, reading the key from your shell environment:
Or from the CLI: codex mcp add ray --env RAY_API_KEY=ck_live_... -- npx -y @gege-mn/ray-mcp.
In Zed's settings.json:
Local: "ray": { "command": "npx", "args": ["-y", "@gege-mn/ray-mcp"], "env": { "RAY_API_KEY": "ck_live_..." } }.
Any client that runs stdio servers:
Any client that supports Streamable HTTP: URL https://ray-api.gege.mn/mcp, header Authorization: Bearer ck_live_....
| Variable | Required | Default | Description |
|---|---|---|---|
RAY_API_KEY | yes | Ray API key (ck_live_...). Whitespace, quotes and a Bearer prefix are stripped. | |
RAY_MCP_URL | no | https://ray-api.gege.mn/mcp | Hosted endpoint to bridge to. Only change it for staging or local development. |
CLI flags: --help, --version. Requires Node.js 18 or newer.
The tool list comes from the hosted server, so it can grow over time; your client shows the authoritative descriptions and input schemas. Current tools:
| Tool | What it does |
|---|---|
whoami | Shows the workspace, key id and scopes of the API key in use. |
get_usage | Plan, subscription status and this month's usage against the quota. |
list_channels | Configured channels with their ids and the recipient shape each accepts. Call first. |
send_notification | Sends a notification (single, fan-out, multi-channel or feed-only). Needs write. |
get_send_status | Delivery status of a send, with per-recipient rows. |
list_templates | Lists message templates. |
get_template | One template with its published version and draft. |
create_template | Creates a template, optionally publishing it. Needs write. |
update_template_draft | Replaces a template's draft. Needs write. |
publish_template | Publishes a template's draft as the live version. Needs write. |
archive_template | Archives a template. Needs write. |
unarchive_template | Restores an archived template. Needs write. |
test_send_template | Sends a real test of a published template to one recipient. Needs write. |
list_feed_notifications | Reads one end user's in-app notification feed. |
get_click_stats | Email link click counts for a send or campaign. |
list_webhooks | Lists outbound event webhooks and their delivery health. |
get_webhook | One outbound webhook. |
create_webhook | Creates an outbound webhook; returns its signing secret once. Needs write. |
update_webhook | Changes a webhook or rotates its secret. Needs write. |
delete_webhook | Deletes a webhook. Needs write. |
read_docs | Reads Ray's documentation as markdown. |
Read-only tools are annotated readOnlyHint; archive and delete tools are annotated destructiveHint, so clients can ask before running them.
firstName param, then test-send it to me."snd_... get delivered? Show me any failures."https://example.com/hooks/ray for failed deliveries."The local package always starts, even when something is wrong, and explains the problem through MCP instead of crashing. Diagnostics go to stderr (your client's MCP log); stdout carries only MCP messages.
setup_help tool is listed. The server can't load Ray's tools. Its description says why. Without RAY_API_KEY every tool call returns setup steps. If the endpoint was unreachable, call setup_help after fixing the cause: it retries, and on success the client is told the tool list changed. If your client doesn't refresh, reload the server.write scope.get_usage.RAY_MCP_URL.npx not found or old Node. Install Node.js 18+ and make sure npx is on the PATH your client uses. On macOS GUI apps may not see shell PATH changes; use an absolute path to npx if needed.RAY_API_KEY=ck_live_... npx -y @gege-mn/ray-mcp should log connected to https://ray-api.gege.mn/mcp on stderr, then wait for input (Ctrl+C to exit). Or inspect it with npx @modelcontextprotocol/inspector npx -y @gege-mn/ray-mcp..md to any docs URL for raw markdown). The MCP setup guide is Using Ray with AI coding agents.@gege-mn/ray (gege-mn/ray-node).npx skills add gege-mn/ray-skills).Releasing: bump the version in package.json, server.json (both version fields) and src/version.ts, update CHANGELOG.md, then publish a GitHub release tagged vX.Y.Z. The publish workflow ships to npm and the MCP Registry. To publish by hand instead: pnpm publish --access public, then run the MCP Registry workflow (a personal mcp-publisher login github can't publish under the gege-mn namespace).
MIT © gege.mn