MCP server
PushFleet runs a remote MCP server at https://mcp.pushfleet.com, over streamable HTTP. Any MCP client that supports remote servers can connect: coding agents, IDEs and your own scripts.
Sign-in
Section titled “Sign-in”The first time a client connects, PushFleet asks you to sign in with OAuth. On the consent screen you pick the project, the environment and the scopes the agent gets. PushFleet then creates a restricted key for that agent, so it shows up in the dashboard with its name and you can revoke it in one click.
For headless setups such as CI, skip OAuth and send a restricted key yourself as Authorization: Bearer pf_rk_….
Logged and limited
Section titled “Logged and limited”Every tool call is logged with the key that made it. A tool the key has no scope for fails with missing_scope, and create_key can never grant more than the agent’s own scopes.
upload_credential
Section titled “upload_credential”Verify and store an Apple .p8 key or a Firebase service account. Needs credentials:write.
create_key
Section titled “create_key”Create an API key with the permissions you allow. Needs keys:write.
Send a notification to a user or a device. Needs messages:write.
send_test
Section titled “send_test”Send a test notification to your own device. Needs messages:write.
list_devices
Section titled “list_devices”List a user’s registered devices. Needs devices:read.
get_message
Section titled “get_message”Look up a message’s delivery status. Needs messages:read.