Get started

Chmeetings for AI agents

ChMeetings manages church operations, from event planning and member records to donations and volunteer coordination, for faith-based organizations and congregations. 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 ChmeetingsSee the 28 actions ↓
SchedulingAPI keyMCP + RESTchmeetings.com
AUDIT LOG · CHMEETINGSPOLICY: acme-support
09:41:07 · claude · u_8f2read
chmeetings.list_meeting_attendees
List Meeting Attendees✓ allowed · 212ms
09:41:09 · claude · u_8f2write
chmeetings.create_meeting
ChMeetings: Create Meeting✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
chmeetings.delete_meeting_attendee
Delete Meeting Attendee✕ blocked · policy: deny
EVERY CHMEETINGS CALL, ON THE RECORD
01 · USE CASES

What agents do in Chmeetings.

01

Create a new meeting

Create a new meeting or event and set its date, time, and organization.

02

Look up a member's profile

Look up a person's profile before updating their contact or membership details.

03

Confirm before deleting a person

Confirm before deleting a person's record, since their attendance and giving history goes with it.

02 · ACTIONS

28 Chmeetings actions, graded by risk.

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

read

1

Look things up. Allowed by default.

  • chmeetings.list_meeting_attendees
    List Meeting Attendees

write

22

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

  • chmeetings.create_meeting
    ChMeetings: Create Meeting
  • chmeetings.create_reminder
    ChMeetings: Create Reminder
  • chmeetings.create_organization
    ChMeetings: Create Organization
  • chmeetings.update_attendee_role
    Update attendee role
  • chmeetings.person_get
    ChMeetings: Get Person
  • chmeetings.people_list
    ChMeetings: List People
  • chmeetings.attendee_get
    Get Attendee Details
  • chmeetings.meetings_get
    ChMeetings: Get Meeting
  • chmeetings.reminder_get
    ChMeetings: Get Reminder
  • chmeetings.settings_get
    ChMeetings: Get Settings
  • chmeetings.people_update
    ChMeetings: Update Person
  • chmeetings.person_create
    ChMeetings: Create Person
  • chmeetings.reminders_list
    ChMeetings: List Reminders
  • chmeetings.attendee_create
    Invite Meeting Attendee
  • chmeetings.meetings_update
    ChMeetings: Update Meeting
  • chmeetings.reminder_update
    ChMeetings: Update Reminder
+ 6 MORE

destructive

5

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

  • chmeetings.delete_meeting_attendee
    Delete Meeting Attendee
  • chmeetings.people_delete
    ChMeetings: Delete Person
  • chmeetings.meetings_delete
    ChMeetings: Delete Meeting
  • chmeetings.reminder_delete
    ChMeetings: Delete Reminder
  • chmeetings.organizations_delete
    ChMeetings: Delete Organization
03 · HOW IT WORKS

Chmeetings in three steps.

  1. 01Your users connect ChmeetingsThey add their Chmeetings api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “chMeetings: Create Meeting” can wait for the user, and “delete Meeting Attendee” can be denied outright.
  3. 03Any agent can actYour agent calls Chmeetings 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('chmeetings', {
  read: 'allow',
  write: 'ask',        // create_meeting
  destructive: 'deny',  // delete_meeting_attendee
})

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

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

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

More scheduling apps.

Google Calendar50 actionsCalendly57 actionsApaleo29 actionsCal175 actionsBookingmood142 actionsEventbrite95 actionsEtermin78 actionsTicket Tailor77 actions
ALL SCHEDULING APPS →
07 · FAQ

Chmeetings and Arc0, answered.

Q01

Can I use Chmeetings with Claude, ChatGPT or Cursor?

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

Q02

How do users connect Chmeetings?

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

28 in total: 1 read, 22 write and 5 destructive, such as “chMeetings: Create Meeting”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Chmeetings?

Yes. Actions like “delete Meeting Attendee” 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 Chmeetings too?

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

Get started

Plug Chmeetings into your agent.

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

Connect ChmeetingsBrowse all apps →

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