Koskamo

Yo MCP

An MCP server that enables AI agents to send push notifications to a paired mobile device. It supports registering agents, checking registration status, canceling registrations, and sending 'Yo' notifications with optional subjects and context URLs.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Yo MCP logo, by YoCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by Yo
MCP endpoint (Streamable HTTP)
https://getyo.dev/mcp
Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

5 of 5 have a description · 5 of 5 declare behavior hints · 5 of 5 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Send push notifications to a paired phone
  • Register an AI agent for notifications
  • Check agent registration status
  • Cancel or revoke agent pairing

Source and maintenance

Community listingRegistry 1.0.1
Maintenance checked

Protocol and capabilities

Server
yo 1.1.0
MCP protocol negotiated in check
2025-11-25
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Yo lets an agent send its owner a push notification. Include a short subject explaining why you are notifying them (recommended, optional for compatibility) and a useful context_url when available. Subjects are visible on the lock screen: avoid secrets. If you have no API key, call register_agent, show the user the complete pairing URL (including the #fragment), and poll check_registration. When the key arrives, tell the user which account paired_with names; if it is not theirs, call cancel_registration (or revoke_self with the key, at any later time). Send at most 1 yo per 30 seconds.

Tools

5 advertised

register_agent
Advertised by the server during the last successful anonymous check.

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.

register_agent input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "proposed_name"
  ],
  "properties": {
    "platform": {
      "type": "string",
      "maxLength": 64,
      "description": "Agent platform (e.g. \"cursor\", \"devin\", \"claude-code\")"
    },
    "description": {
      "type": "string",
      "maxLength": 500,
      "description": "Short description of what this agent does"
    },
    "proposed_name": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Proposed display name for the agent (e.g. \"banana\", \"devin-home-repo\")"
    }
  }
}
register_agent annotations
{
  "readOnlyHint": false,
  "openWorldHint": false
}
check_registration
Advertised by the server during the last successful anonymous check.

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.

check_registration input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "pairing_code"
  ],
  "properties": {
    "claim_token": {
      "type": "string",
      "maxLength": 64,
      "description": "The claim_token returned by register_agent; required to receive the api_key"
    },
    "pairing_code": {
      "type": "string",
      "maxLength": 16,
      "minLength": 1,
      "description": "The pairing code returned by register_agent"
    }
  }
}
check_registration annotations
{
  "readOnlyHint": false,
  "openWorldHint": false
}
cancel_registration
Advertised by the server during the last successful anonymous check.

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.

cancel_registration input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "pairing_code",
    "claim_token"
  ],
  "properties": {
    "claim_token": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "The claim_token returned by register_agent (authorizes the cancellation)"
    },
    "pairing_code": {
      "type": "string",
      "maxLength": 16,
      "minLength": 1,
      "description": "The pairing code returned by register_agent"
    }
  }
}
cancel_registration annotations
{
  "readOnlyHint": false,
  "openWorldHint": false
}
revoke_self
Advertised by the server during the last successful anonymous check.

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.

revoke_self input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "confirm"
  ],
  "properties": {
    "confirm": {
      "type": "boolean",
      "const": true,
      "description": "Must be true — revocation is immediate and irreversible"
    }
  }
}
revoke_self annotations
{
  "readOnlyHint": false,
  "openWorldHint": false
}
yo
Advertised by the server during the last successful anonymous check.

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.

yo input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "subject": {
      "type": "string",
      "minLength": 1,
      "description": "Recommended: a short, specific subject explaining why you are notifying the user (1–120 characters, counted as Unicode code points), e.g. \"PR ready for review\". Plain text, one line; avoid secrets because it appears on the lock screen. Optional for compatibility with older agents."
    },
    "context_url": {
      "type": "string",
      "maxLength": 2048,
      "description": "Optional https or app deep-link URL opened when the user taps the notification"
    }
  }
}
yo annotations
{
  "readOnlyHint": false,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
681 ms
95th percentile latency
681 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 681 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http yo-mcp https://getyo.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add yo-mcp --url https://getyo.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable yo-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "yo-mcp": {
      "url": "https://getyo.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "yo-mcp": {
      "type": "streamableHttp",
      "url": "https://getyo.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start yo-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "yo-mcp": {
      "type": "http",
      "url": "https://getyo.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http yo-mcp https://getyo.dev/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://getyo.dev/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "yo-mcp": {
      "serverUrl": "https://getyo.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Yo MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.