MCP Server Overview
Architecture and authentication for the Pushary MCP server
New to Pushary agent notifications? Start with the Getting Started guide — it covers signup, connecting your agent, and sending your first notification in under 5 minutes.
Architecture
Pushary exposes a hosted Model Context Protocol (MCP) server that lets AI agents send push notifications, manage subscribers, run campaigns, control automation flows, and ask users yes/no questions via push.
Any MCP-compatible client can connect — including Cursor, Claude Code, Windsurf, Lovable, and any tool that supports Streamable HTTP or stdio via mcp-remote.
AI Agent → MCP (Streamable HTTP) → pushary.com/api/mcp → Pushary APIThe 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.
Connection methods
Streamable HTTP (recommended)
Most modern MCP clients support HTTP transport. Add this to your MCP configuration:
{
"pushary": {
"url": "https://pushary.com/api/mcp/mcp",
"headers": {
"Authorization": "Bearer pk_xxx.secret_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.secret_xxx"
]
}
}Agent skill
Install the Pushary skill to teach your agent when and how to use notifications:
npx skills add pushary/pushary-skillThis works with Cursor, Claude Code, Codex, Windsurf, and 38 more agents. The skill includes the MCP tool documentation and best practices for notification etiquette and human-in-the-loop flows.
Authentication
The MCP server authenticates using a site API key passed as a Bearer token in the Authorization header. Keys are site-scoped — each key is tied to a specific site.
The key format is pk_xxx.secret_xxx and is only shown once at creation time. Store it securely.
If the API key is missing or invalid, the server returns HTTP 401 and all tool calls will fail with an authentication error.
Rate limits
MCP tool calls are subject to the same rate limits as the REST API. Limits are per-workspace and vary by plan tier.
Tool categories
The Pushary MCP server exposes 19 tools across six categories:
| Category | Tools | Description |
|---|---|---|
| Notifications | send_notification | Send push notifications to subscribers |
| Human-in-the-Loop | ask_user_yes_no, wait_for_answer, cancel_question | Ask yes/no questions, wait for answers |
| Subscribers | list_subscribers, get_subscriber, count_subscribers | View and manage notification subscribers |
| Campaigns | list_campaigns, create_campaign, get_campaign, send_campaign, pause_campaign, get_campaign_stats | Create and manage notification campaigns |
| Templates | list_templates, create_template | Reusable notification templates |
| Flows | list_flows, create_flow, activate_flow, pause_flow | Automation flows (welcome series, re-engagement) |
Section guide
| Page | What it covers |
|---|---|
| Getting Started | Sign up, connect your agent, send your first notification |
| Receiving Notifications | Subscribe on iPhone, Android, and desktop |
| Human-in-the-Loop | Yes/no questions with retry logic and best practices |
| Available Tools | Full parameter reference for all 19 tools |
| Use Cases & Prompts | Copy-paste prompts and server-side utility code |