MCP Server
Connect AI agents to Pushary using the Model Context Protocol
Overview
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 human-in-the-loop push notifications.
Any MCP-compatible client can connect - including Claude Desktop, Cursor, Windsurf, OpenClaw, and any tool that supports Streamable HTTP or stdio via mcp-remote.
How It Works
Your AI agent connects to Pushary's MCP endpoint using your API key. The agent can then discover and call Pushary tools just like any other MCP tool. Every tool call is authenticated and rate-limited the same way as the REST API.
AI Agent → MCP (Streamable HTTP) → pushary.com/api/mcp → Pushary APIQuick Start
1. Get Your API Key
- Go to Dashboard → Sites
- Click Settings on the site you want to connect
- Open the Integration tab
- Click Create API Key and copy the key shown - it is only displayed once
2. Connect Your Client
Cursor, Claude Desktop, Windsurf (Streamable HTTP):
{
"pushary": {
"url": "https://pushary.com/api/mcp/mcp",
"headers": {
"Authorization": "Bearer pk_xxx.secret_xxx",
"Accept": "application/json, text/event-stream"
}
}
}stdio-only clients (via mcp-remote bridge):
{
"pushary": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://pushary.com/api/mcp/mcp",
"--header",
"Authorization:Bearer pk_xxx.secret_xxx"
]
}
}3. Start Using Tools
Once connected, your AI agent can discover all Pushary tools automatically. Try asking your agent:
- "Send a push notification to all active subscribers about our new feature"
- "How many active subscribers do we have?"
- "Create a campaign for our weekend sale"
- "What are the stats for our last campaign?"
- "Before deploying, ask me for confirmation via push notification"
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 and is only shown once at creation time. Store it securely; you cannot retrieve it again.
API access requires a Starter plan or higher.
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.