MCP 服务器
通过 Model Context Protocol，从 Claude 及其他 AI 智能体操控 PushWard。托管的 MCP 服务器让智能体能够通过您的集成密钥创建 Live Activities、发送通知并管理小组件。
PushWard runs a remote Model Context Protocol (MCP) server, so AI agents like Claude can drive your account in natural language — create and update Live Activities, send notifications, manage Home Screen widgets, send email, and run health checks. It's a hosted server with nothing to install: your client connects over OAuth and you authorize it once with your integration key.
The MCP server is the same PushWard REST API behind a tool interface for AI agents. It uses your hlk_ integration key, so an agent can only do what that key's scopes and capabilities allow.
Connect from Claude Code
Add the server with one command. OAuth runs interactively the first time the agent uses a tool.
claude mcp add --transport http pushward https://mcp.pushward.app/mcpConnect from other clients
Any MCP client that supports remote servers over OAuth — Claude Desktop, the Claude apps, and others — can connect by adding a remote (custom) connector pointed at the endpoint below:
https://mcp.pushward.app/mcpThe client discovers the OAuth endpoints automatically and walks you through authorization on first connect.
Authorize
The first time you connect, a browser opens a PushWard consent screen. Paste your hlk_ integration key once and approve access. The server validates the key, stores it encrypted, and issues short-lived tokens for the session — your raw key is never shared with the MCP client.
Get your integration key from the iOS app's settings screen. See Authentication for how keys, scopes, and capability flags work.
Create a dedicated integration key for the MCP server instead of reusing your default key. Scope it to just the capabilities the agent needs (notifications, widgets, email) so you can revoke it independently.
What you can do
The remote server exposes tools covering the full API surface:
- Live Activities — create, update, end, get, list, and delete activities, plus bulk-end by filter.
- Notifications — send inbox notifications with optional push delivery.
- Widgets — full CRUD for Home Screen widgets.
- Email — send transactional email to verified recipients.
- Health — liveness and readiness checks for the API.
- Test workflows — composite helpers that run a full lifecycle (for example, create an activity, push a few updates, then end it) in one call.
- Reference — built-in tools that return the PushWard docs bundle and integration best practices, so the agent grounds its calls in the real API.
Relay webhook-simulation tools (Grafana, Sonarr, ArgoCD, and the rest) are only available in the local build of the MCP server, not the hosted endpoint. For production webhooks use the Relay integration directly.
Endpoint
| Property | Value |
|---|---|
| Endpoint | https://mcp.pushward.app/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1, authorized with an hlk_ integration key |
Next steps
- API Reference — every endpoint the MCP tools map to
- Authentication — integration keys, scopes, and capability flags
- Getting Started — create your first Live Activity