Web Push MCP server for AI clients

The Streamable HTTP MCP endpoint exposes seven typed tools backed by the same campaign validation as the dashboard. It uses an account token, returns structured data, and never gives an AI client browser permission or a way around delivery limits.

Connect an MCP-compatible client

Create a bearer token in the dashboard, then configure the client with the exact HTTPS endpoint. Keep the token in a secret store or environment variable rather than a prompt, chat, URL, or repository.

MCP client configuration{ "mcpServers": { "pushnotifications": { "url": "https://pushnotifications.org/mcp", "headers": { "Authorization": "Bearer YOUR_PN_TOKEN" } } } }

Seven typed campaign tools

List websites

Returns only registered websites owned by the authenticated account.

Delivery overview

Returns plan usage, campaign counts, and the next scheduled message.

List campaigns

Filters account campaigns by website, status, and a bounded result limit.

Get campaign

Loads one account-owned campaign with its current state and schedule.

Create campaign

Creates a validated draft or schedule with a verified-site destination.

Schedule campaign

Queues an editable campaign for a future time, subscriber goal, or both.

Return to draft

Cancels a scheduled send by returning the campaign to a reviewable draft.

Use a review-first workflow

  1. Ask the client to list websites and choose the intended site ID.
  2. Create a draft first and inspect its copy, destination, audience, and rich fields.
  3. Ask for the campaign again before making a schedule decision.
  4. Schedule only after a person confirms the website, message, destination, and time.

MCP does not expand account authority

The server cannot grant visitor permission, read confidential subscriber endpoints, change a visitor's opt-out choice, bypass the rolling contact protection, exceed an account allowance, or edit another account's data. The token holder can act only within the token owner's account, so revoke a token immediately if it may have been exposed.

For direct server integrations, read the REST API guide. For terminal use, download the no-dependency CLI.