Ray MCP server
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.
Agenten stärken
Die eigene URL des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
https://ray-api.gege.mn/mcpDie Claude-Schaltfläche oben öffnet Claude mit ausgefülltem Namen und ausgefüllter URL. Sie bestätigen dort noch.
claude mcp add --transport http io.github.gege-mn-ray-mcp https://ray-api.gege.mn/mcpRun in a terminal.
{ "mcpServers": { "io.github.gege-mn-ray-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://ray-api.gege.mn/mcp" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
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.
Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.
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:
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:
claude mcp add --transport http ray https://ray-api.gege.mn/mcp --header "Authorization: Bearer $RAY_API_KEY"
Local:
claude mcp add ray --env RAY_API_KEY=ck_live_... -- npx -y @gege-mn/ray-mcp
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:
{
"mcpServers": {
"ray": {
"command": "npx",
"args": ["-y", "@gege-mn/ray-mcp"],
"env": { "RAY_API_KEY": "ck_live_..." }
}
}
}
.cursor/mcp.json in a project, or ~/.cursor/mcp.json for all projects.
Hosted:
{
"mcpServers": {
"ray": {
"url": "https://ray-api.gege.mn/mcp",
"headers": { "Authorization": "Bearer ck_live_..." }
}
}
}
Local:
{
"mcpServers": {
"ray": {
"command": "npx",
"args": ["-y", "@gege-mn/ray-mcp"],
"env": { "RAY_API_KEY": "ck_live_..." }
}
}
}
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:
{
"inputs": [
{ "id": "ray-api-key", "type": "promptString", "description": "Ray API key (ck_live_...)", "password": true }
],
"servers": {
"ray": {
"type": "http",
"url": "https://ray-api.gege.mn/mcp",
"headers": { "Authorization": "Bearer ${input:ray-api-key}" }
}
}
}
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}):
{
"mcpServers": {
"ray": {
"serverUrl": "https://ray-api.gege.mn/mcp",
"headers": { "Authorization": "Bearer ${env:RAY_API_KEY}" }
}
}
}
Local: use the same command / args / env entry as in the Cursor example.
~/.codex/config.toml, local:
[mcp_servers.ray]
command = "npx"
args = ["-y", "@gege-mn/ray-mcp"]
env = { RAY_API_KEY = "ck_live_..." }
Hosted, reading the key from your shell environment:
[mcp_servers.ray]
url = "https://ray-api.gege.mn/mcp"
bearer_token_env_var = "RAY_API_KEY"
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:
{
"context_servers": {
"ray": {
"url": "https://ray-api.gege.mn/mcp",
"headers": { "Authorization": "Bearer ck_live_..." }
}
}
}
Local: "ray": { "command": "npx", "args": ["-y", "@gege-mn/ray-mcp"], "env": { "RAY_API_KEY": "ck_live_..." } }.
Any client that runs stdio servers:
{
"mcpServers": {
"ray": {
"command": "npx",
"args": ["-y", "@gege-mn/ray-mcp"],
"env": { "RAY_API_KEY": "ck_live_..." }
}
}
}
Any client that supports Streamable HTTP: URL https://ray-api.gege.mn/mcp, header Authorization: Bearer ck_live_....
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:
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).pnpm install
pnpm typecheck
pnpm test # vitest: bridge end to end against an in-process fake Ray endpoint
pnpm build # tsup -> dist/index.js
pnpm smoke # the built binary over real stdio
RAY_MCP_URL=http://localhost:8787/mcp RAY_API_KEY=ck_live_... node dist/index.js
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
Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.
{ "mcpServers": { "io.github.gege-mn-ray-mcp": { "url": "https://ray-api.gege.mn/mcp", "headers": {} } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: RAY_API_KEY, RAY_MCP_URL.
Ray Notifications wird über HTTP erreicht.
Zuletzt geprüft: 2026-11-09. Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.