Your church ministry plans, in conversation.

Before connecting

Sign in to Hapibit Church Planner with a verified Hapibit account and join or create a church. Sample church accounts cannot connect. Your existing church role and department determine what the assistant can access.

For a client that supports remote MCP and OAuth, add this server URL in its connection settings:

Review the requesting app and return address, sign in on Hapibit, and approve the displayed permissions. A request to change plans requires your explicit approval for write access. Your Hapibit password is not shared with the AI client.

Public directory availability depends on each platform’s review. This page does not mean the integration has been approved or listed in Claude or ChatGPT.

What you can ask

• “Which church and department am I connected to?”
• “Find my department’s upcoming ministry plans.”
• “Summarize the schedule and preparation for this ministry.”
• “Create a draft plan for our outreach day.”
• “Update this ministry’s location after I review the change.”
• “Copy this ministry to next year as a new draft.”

Creating, updating and copying require write access, the applicable church permissions, and acceptance of the planner’s community rules. Existing data is read before changes; an outdated version must be refreshed before saving.

Information and permissions

The connection may return your church, role, department, ministry schedules and descriptions, prayer requests, and other ministry details permitted by your role. Budget details, evaluations and internal preparation are restricted by role and department.

It does not provide congregant records, weekly journals, department annual budgets, account deletion, ministry deletion, member management, purchases or payments. Connecting does not allow access to another church.

The assistant receives the records needed for its requests. Review the connected provider’s data handling settings and your church’s sharing rules before connecting. See our privacy policy for storage, sharing and deletion details.

Disconnect or reconnect

Connections last up to 30 days. Open connection settings to revoke a connection immediately, or reconnect from your AI client when authorization expires. Revocation prevents future requests; it cannot retrieve data already received by the other service.

Clients that support a manually configured Bearer credential can continue to use a personal connection key. Store that key only in the client’s secure authentication settings. A GPT configured with your personal key is for your private use.

If access is denied, check your church membership, role, the approved permissions and connection expiry. Contact Hapibit support without sending passwords or access tokens.