Skip to main content
Glama
gege-mn

Ray: Your Notification Infra

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RAY_API_KEYYesRay API key (`ck_live_...`). Whitespace, quotes and a `Bearer ` prefix are stripped.
RAY_MCP_URLNoHosted endpoint to bridge to. Only change it for staging or local development.https://ray-api.gege.mn/mcp

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
setup_helpA

Ray's tools could not be loaded. Ray rejected the API key (HTTP 401). Check that RAY_API_KEY holds a current key: keys are shown only once, and revoked keys stop working immediately. Create a new key at https://ray.gege.mn under "API keys", update the MCP server's env, and restart your MCP client. Server said: unauthorized: invalid Authorization header: expected Bearer <Ray API key>. Call this tool to see how to fix it and to retry the connection.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion with other tools. The single tool's purpose is clearly diagnostic.

Naming Consistency5/5

The lone tool name 'setup_help' follows a clear snake_case verb_noun pattern. Since there is only one tool, naming consistency is trivially maintained.

Tool Count1/5

A notification infrastructure server with just one help/diagnostic tool is extremely under-scoped. This single tool does not constitute a functional server.

Completeness1/5

The tool surface provides no actual notification capabilities—no send, list, create, or manage operations. The server is effectively non-functional, failing its stated purpose entirely.