Push by Techulus for AI agents

Push by Techulus sends transactional push notifications across platforms through code and no-code integrations. Developers use it to deliver real-time alerts without building notification infrastructure. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

CommunicationAPI keyMCP + RESTpush.techulus.com
AUDIT LOG · PUSH BY TECHULUSPOLICY: acme-support
09:41:09 · claude · u_8f2write
push_by_techulus.send_notification_sync
Send Notification Sync✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
push_by_techulus.delete_team_member_or_invite
Delete Team Member or Invite✕ blocked · policy: deny
EVERY PUSH BY TECHULUS CALL, ON THE RECORD
01 · USE CASES

What agents do in Push by Techulus.

01

Send a notification synchronously

Send a real-time notification to a user and confirm delivery in the same request.

02

Send to a device group

Push a notification to a whole device group at once for a broad announcement.

03

Remove a team member with approval

Remove a team member's access only after an admin confirms the change.

02 · ACTIONS

6 Push by Techulus actions, graded by risk.

Every Push by Techulus action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

0

Look things up. Allowed by default.

  • No read actions.

write

5

Create and change things. Allow, or ask the user first.

  • push_by_techulus.send_notification_sync
    Send Notification Sync
  • push_by_techulus.send_notification_async
    Send Push Notification Async
  • push_by_techulus.send_notification_to_group
    Send Notification to Device Group
  • push_by_techulus.send_notification_webhook_post
    Send Notification via Webhook POST
  • push_by_techulus.invite_user_to_team
    Invite User to Team

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • push_by_techulus.delete_team_member_or_invite
    Delete Team Member or Invite
03 · HOW IT WORKS

Push by Techulus in three steps.

  1. 01Your users connect Push by TechulusThey add their Push by Techulus api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “send Notification Sync” can wait for the user, and “delete Team Member or Invite” can be denied outright.
  3. 03Any agent can actYour agent calls Push by Techulus through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('push_by_techulus', {
  read: 'allow',
  write: 'ask',        // send_notification_sync
  destructive: 'deny',  // delete_team_member_or_invite
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Push by Techulus connects.

Users add their Push by Techulus api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Push by Techulus connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Push by Techulus from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Push by Techulus and Arc0, answered.

Q01

Can I use Push by Techulus with Claude, ChatGPT or Cursor?

Yes. Connect Push by Techulus to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Push by Techulus actions you allow.

Q02

How do users connect Push by Techulus?

Users add their Push by Techulus api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Push by Techulus actions can my agent take?

6 in total: 0 read, 5 write and 1 destructive, such as “send Notification Sync”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Push by Techulus?

Yes. Actions like “delete Team Member or Invite” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Push by Techulus too?

Yes. The same Push by Techulus connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Push by Techulus into your agent.

Your users connect Push by Techulus once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan