---
title: Pushello developer platform
description: Pushello REST API, SDK, webhooks, and OAuth-protected MCP integration.
canonical: https://www.pushello.com/developers/
last-updated: 2026-09-05
---

# Pushello developer platform

Integrate cross-platform push delivery through the REST API, browser and native SDKs, signed webhooks, or the OAuth-protected MCP server published for Claude and ChatGPT.

## Developer resources

- [Developer guide](https://www.pushello.com/developers/)
- [REST API reference](https://www.pushello.com/api/)
- [OpenAPI specification](https://www.pushello.com/openapi.json)
- [Authentication](https://www.pushello.com/auth.md)
- [MCP server card](https://www.pushello.com/.well-known/mcp/server-card.json)
- [Pricing](https://www.pushello.com/en/pricing/)

## MCP tools

- `list_projects` — List tenant-owned projects using a safe metadata projection.
- `get_project` — Fetch safe metadata for a tenant-owned project.
- `get_credentials_status` — Check provider setup as booleans without returning credentials.
- `list_devices` — List bounded, privacy-filtered device registration metadata.
- `list_notifications` — List safe delivery counts and platform/timestamp metadata.
- `list_webhook_subscriptions` — List webhook status without secrets or credential-bearing paths.
- `list_api_keys` — List key metadata and scopes without returning key secrets.
- `list_team_members` — List organization operators and pending invitations safely.
- `send_push` — Send an approval-gated push to interests or users, never both.

## Privacy boundary

Pushello never exposes provider credentials, VAPID private keys, device identifiers or tokens, user identifiers, interests, attestation, notification targets, or platform payloads through its MCP tools. Read tools return explicit safe projections. The `send_push` write tool requires `pushello:write`, resolves tenant ownership, and keeps publish credentials server-side.