Integration

Push by Techulus integration

Push by Techulus delivers custom push notifications to the iOS and Android devices signed in to a Push account. Send a notification with a title and body (plus optional sound, channel, link, image and an iOS time-sensitive flag) to every device of the account or team that owns the API key, either waiting for the per-device delivery results or asynchronously (recommended by Push for teams and more than 10 devices), or to one device group by its ID. The webhook variants that carry the API key in the URL path and the beta team-management routes are not exposed. Authentication is the account or team API key from the Push console integrations page (or the mobile app's Account tab), sent in the x-api-key header; the key decides which devices receive the notification.

Connect Push by Techulus How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Push by Techulus.Built from the 3 Push by Techulus tools below, on the connection you add once.

What you can do with Push by Techulus

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

send_group_notificationSend group notificationPOSTSends a push notification to the devices of one device group in the account, and returns the per-device delivery results. Only the account API key works here: team API keys are refused for this endpoint.
send_notificationSend notificationPOSTSends a push notification to every device of the account (account API key) or of every team member (team API key) and waits for per-device delivery results. Push recommends send_notification_async for teams and for more than 10 devices.
send_notification_asyncSend notification asyncPOSTSame notification as send_notification, delivered asynchronously: the answer is an acknowledgement (success and message) instead of per-device delivery results. Recommended by Push for teams and for more than 10 devices.

Use Push by Techulus from Claude Code, Cursor or Codex

Connect Push by Techulus in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Push by Techulus operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Push by Techulus

Create your workspace
Sign up free. Nothing to install.
Connect Push by Techulus once
Add your Push by Techulus connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.