How It Works

Architecture

Pushary runs a hosted Model Context Protocol (MCP) server. Your AI agent connects to it over HTTP, gets access to notification and question tools, and can reach you on any device you've subscribed on.

AI Agent → MCP (Streamable HTTP) → pushary.com/api/mcp → Web Push → Your Phone

The MCP server is a thin layer over the Pushary REST API. Every tool call maps to an API endpoint. Authentication, rate limits, and plan limits are shared between MCP and REST.

Any MCP-compatible client works: Claude Code, Codex, Cursor, Windsurf, Hermes, Lovable, and any tool that supports Streamable HTTP or stdio via mcp-remote.

Connection methods

Streamable HTTP (recommended)

Most modern MCP clients support HTTP transport:

{
  "pushary": {
    "url": "https://pushary.com/api/mcp/mcp",
    "headers": {
      "Authorization": "Bearer pk_xxx.sk_xxx"
    }
  }
}

stdio via mcp-remote

For clients that only support stdio transport, use the mcp-remote bridge:

{
  "pushary": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://pushary.com/api/mcp/mcp",
      "--header",
      "Authorization:Bearer pk_xxx.sk_xxx"
    ]
  }
}

Agent skill

Install the Pushary skill to teach your agent when and how to use notifications:

npx skills add pushary/pushary-skill

Works with Claude Code, Codex, Cursor, Windsurf, and 38+ other agents. The skill includes tool documentation and best practices for notification etiquette.

Authentication

The MCP server authenticates via a site API key passed as a Bearer token. Keys are site-scoped. Each key is tied to a specific workspace.

The key format is pk_xxx.sk_xxx and is shown once at creation time. Store it securely.

If the key is missing or invalid, the server returns HTTP 401 and all tool calls fail.

Authentication details

Rate limits

MCP tool calls share rate limits with the REST API. Limits are per-workspace and vary by plan.

Pricing and limits

Tool categories

The MCP server exposes 19 tools across six categories:

Full tools reference