Get started

Heartbeat for AI agents

Heartbeat provides plug-and-play tools for building and managing online communities, covering members, channels, and events, used by creators and businesses running paid or free community spaces. 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.

Connect HeartbeatSee the 7 actions ↓
ProductivityAPI keyMCP + RESTheartbeat.chat
AUDIT LOG · HEARTBEATPOLICY: acme-support
09:41:07 · claude · u_8f2read
heartbeat.list_users
List Users✓ allowed · 212ms
09:41:08 · claude · u_8f2read
heartbeat.get_events
Get Events✓ allowed · 164ms
09:41:09 · claude · u_8f2write
heartbeat.reactivate_user
Reactivate User✓ approved · approved by user
EVERY HEARTBEAT CALL, ON THE RECORD
01 · USE CASES

What agents do in Heartbeat.

01

List community members

List members of a community to check who has joined ahead of an event.

02

Check upcoming events

Pull upcoming community events to remind members of what's on the calendar.

03

Reactivate a member with approval

Reactivate a previously deactivated member only after a community admin confirms the request.

02 · ACTIONS

7 Heartbeat actions, graded by risk.

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

read

6

Look things up. Allowed by default.

  • heartbeat.get_events
    Get Events
  • heartbeat.list_users
    List Users
  • heartbeat.list_groups
    List Groups
  • heartbeat.list_channels
    List channels
  • heartbeat.retrieve_user
    Retrieve User
  • heartbeat.retrieve_group
    Retrieve Group

write

1

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

  • heartbeat.reactivate_user
    Reactivate User

destructive

0

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

  • No destructive actions.
03 · HOW IT WORKS

Heartbeat in three steps.

  1. 01Your users connect HeartbeatThey add their Heartbeat api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “reactivate User” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Heartbeat 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('heartbeat', {
  read: 'allow',
  write: 'ask',        // reactivate_user
  destructive: 'deny',  
})

# 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 Heartbeat connects.

Users add their Heartbeat 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 Heartbeat 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 Heartbeat from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More productivity apps.

Notion57 actionsAirtable27 actionsConfluence70 actionsClickUp164 actionsAmazing Marvin10 actionsRentman130 actionsHub Planner122 actionsCoda110 actions
ALL PRODUCTIVITY APPS →
07 · FAQ

Heartbeat and Arc0, answered.

Q01

Can I use Heartbeat with Claude, ChatGPT or Cursor?

Yes. Connect Heartbeat 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 Heartbeat actions you allow.

Q02

How do users connect Heartbeat?

Users add their Heartbeat 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 Heartbeat actions can my agent take?

7 in total: 6 read, 1 write and 0 destructive, such as “reactivate User”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Heartbeat?

Yes. Allow read actions and deny writes in the Heartbeat policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Heartbeat too?

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

Get started

Plug Heartbeat into your agent.

Your users connect Heartbeat once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.

Connect HeartbeatBrowse all apps →

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