Yo

io.github.alfongj-comPublished by GitHub account alfongj-comv1.0.1Updated Nov 2, 2026

Let agents send content-free push notifications to a paired phone via MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Hosted MCP server that lets an agent pair with a user's phone and send content-free "Yo" push notifications to it.

What you can do
  • Register the agent and pair it with a phone via a pairing URL and code the user approves in the Yo app
  • Poll a pairing code to collect the API key once and see which account the agent is paired with
  • Cancel a pending or approved pairing, or permanently revoke the agent's own key
  • Send a Yo push notification to the paired owner, optionally with a short subject and a context link
When to use it
Useful when an agent should ping a person's phone at a meaningful moment — a task finished, something needs attention — without carrying message content. It fits setups where the sender identity and timing are the whole signal.
Requirements
A remote Streamable HTTP endpoint at getyo.dev; nothing to install locally. The user needs the Yo app to approve the pairing. After pairing, calls must send the agent API key as an Authorization Bearer token.
Before you install
The API key is returned only once during pairing and must be stored securely; it grants the ability to send notifications and revoke the agent. Pairing must be approved by the right account — check the reported paired account and revoke if it is wrong. Subjects appear on the lock screen, so no secrets should be put in them. Notifications go to a third-party hosted, closed-source service.

Installation

In SourceWeft

  1. Open Yo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.alfongj-com%2Fyo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "yo": {
      "type": "http",
      "url": "https://getyo.dev/mcp"
    }
  }
}

README

Yo — Agent Plugin

Let your agent Yo you: one MCP tool call sends a content-free push notification to your phone. The sender identity plus the moment of the ping is the message.

This package is the public integration for the hosted Yo service (Agent Plugins 1.0.0 format):

  • plugin.json — plugin manifest
  • mcp.json — portable Agent Plugins Streamable HTTP config for the hosted Yo MCP server
  • skills/yo/SKILL.md — teaches your agent when and how to yo, and how to register
  • .codex-plugin/plugin.json + .mcp.json — Codex-specific layout; .mcp.json uses the client http transport
  • .claude-plugin/plugin.json + marketplace.json — Claude Code marketplace layout
  • glama.json — Glama directory ownership claim
  • server.json — official MCP Registry metadata for the hosted server. Its version is the registry record version, intentionally decoupled from the plugin manifests' 1.0.0; because the registry rejects duplicate versions and our token can publish but not edit io.github.alfongj-com/*, metadata corrections require a version bump (currently 1.0.1).

The Yo service itself is hosted and closed-source. This repo contains no server code and no secrets.

Install instructions for all platforms: https://getyo.dev/agents

This repository is mirrored automatically from a private monorepo; PRs here are not reviewed — use the contact on the install page.

License

MIT (plugin package only).

Source: README.md at commit 2ab2b3f

Tools

5

register_agent

Register this agent with Yo (unauthenticated). Returns a pairing URL and code to show the user, who approves the connection in the Yo app. Then poll check_registration to obtain the API key.

Parametersplatformdescriptionproposed_namerequired

check_registration

Check the status of a pairing code from register_agent. On the first poll after the user approves, the response includes the api_key exactly once — store it immediately in your secret mechanism — plus paired_with, the account the agent is now connected to, which you MUST show the user.

Parametersclaim_tokenpairing_coderequired

cancel_registration

Abort a pairing you started with register_agent. Works while pending and after approval: an already-approved connection is revoked (the API key stops working) so a pairing approved by the wrong account can be undone. Available until the pairing expires, and for 15 minutes after you pick up the API key; later than that, use revoke_self. Then call register_agent again.

Parametersclaim_tokenrequiredpairing_coderequired

revoke_self

Permanently revoke THIS agent using its API key as the Bearer token. Use when you discover (at any time) that paired_with is not your owner’s account and cancel_registration no longer works. The key stops working immediately; call register_agent to start over.

Parametersconfirmrequired

yo

Send a Yo push notification to your owner. Recommended: include a short subject explaining what the notification is about, and a context_url when there is a useful link to open. The subject appears on the lock screen and in the app; avoid secrets. Requires an agent API key as the Bearer token.

Parameterssubjectcontext_url

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts