This connector has been replaced by Reflecto.
Send notifications, ask approval questions, ring, remind and deliver files to your own paired phone.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
list_devices2 fields changedOutput schema / properties / devices / items / properties / deviceIdAdded value: +{
+ "description": "Stable opaque id. Pass this as send_notification's `device` to reach exactly one device — labels are NOT unique, and a shared label delivers to every device that has it.",
+ "type": "string"
+}Output schema / properties / devices / items / requiredPrevious value: -[
- "label",
- "type",
- "reachable",
- "lastSeenAt"
-]New value: +[
+ "deviceId",
+ "label",
+ "type",
+ "reachable",
+ "lastSeenAt"
+]send_notification1 field changedInput schema / properties / device / descriptionPrevious value: -"Which devices to notify. Prefer the reliable values: 'all' (default), 'phone'/'mobile', or 'desktop'. A comma-separated list of custom device labels also works; call list_devices first to discover the exact labels (when that tool is available). An unknown label is skipped with a warning rather than failing — use the class names above unless the user named a specific device."New value: +"Which devices to notify. Prefer the reliable values: 'all' (default), 'phone'/'mobile', or 'desktop'. A comma-separated list of custom device labels also works; call list_devices first to discover the exact labels (when that tool is available). To reach EXACTLY one device, pass its `deviceId` from list_devices instead of its label — labels are not unique, and a label shared by two devices delivers to both. An unknown label is skipped with a warning rather than failing — use the class names above unless the user named a specific device."list_devices4 fields changedOutput schema / properties / devices / items / properties / lastSeenAt / descriptionPrevious value: -"Unix timestamp in seconds of last server contact"New value: +"Unix timestamp in seconds of last server contact. Coarse (hourly) for phones — prefer statusReportedAt for recency when present"Output schema / properties / devices / items / properties / onlineRemoved value: -{
- "type": "boolean"
-}Output schema / properties / devices / items / properties / reachableAdded value: +{
+ "description": "Whether the server has a delivery channel to the device right now. For a phone this means a live push registration — it can be reached, even if it is currently asleep or switched off. It does NOT mean the user is active on the device.",
+ "type": "boolean"
+}Output schema / properties / devices / items / requiredPrevious value: -[
- "label",
- "type",
- "online",
- "lastSeenAt"
-]New value: +[
+ "label",
+ "type",
+ "reachable",
+ "lastSeenAt"
+]cancel_remindercheck_replyfind_my_phoneget_shared_itemslist_devicesremind_merequest_approvalsend_filesend_notificationClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Add one secure layer between your agents and this server.
Each tool targets a distinct action: scheduling vs cancelling reminders, pushing vs ringing a phone, sending vs receiving files/shared items, and requesting vs polling approvals. The only close pair, send_notification and remind_me, is clearly separated by immediacy vs future scheduling, and the descriptions reinforce the boundary.
All tool names follow a consistent snake_case verb_noun pattern: cancel_reminder, check_reply, get_shared_items, list_devices, request_approval, send_file, send_notification. Minor possessive forms like find_my_phone and remind_me still fit the imperative verb-first style without creating confusion.
Nine tools is well within the ideal range and each one earns its place in a personal-device integration server. The surface covers notifications, reminders, approvals, shared items, file delivery, device discovery, and phone location without redundant or filler tools.
Core workflows are covered: reminders can be scheduled and cancelled, approvals can be requested and polled, notifications can be sent, and shared items can be read incrementally. Minor gaps exist, such as no way to cancel a pending approval and no update mechanism for reminders, but these are workable and the server is explicitly stateless about some of them.