# Planning Center MCP connector

The Planning Center connector brings people records, calendars, events, resource bookings, conflicts and attachments into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with each person signed in under their own Planning Center access.

Source: https://elaichi.ai/connectors/planningcenter/

## Facts

| | |
| --- | --- |
| Application | Planning Center |
| Category | CRM |
| AI tools | 776 |
| Authentication | OAuth or API key |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Planning Center is connected

- Which calendar conflicts are still open for this weekend's events?
- Find the person record for Maria Alvarez in People.
- List the attachments on the fall retreat event.

## Connect Planning Center in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Planning Center.
2. Optionally set Share with, then press Connect.
3. Supply your own Planning Center app, then approve. Planning Center needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Planning Center tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Planning Center MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Planning Center MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Planning Center MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Planning Center MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Planning Center MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Planning Center to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Planning Center tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Planning Center through Elaichi

### Pull up a person before a visit

Pastoral care. Ask for someone's Planning Center profile on the way to a hospital visit or a coffee, and get the record as it stands today rather than a printout from last month.

### Find every open calendar conflict

Events. Before the weekend, ask which Planning Center events still have an unresolved conflict over a room or a resource, and get the list with the events involved.

### See what a room is booked for

Facilities. Ask which events are using the fellowship hall or the sound system this week, read straight from the Planning Center calendar and its resource bookings.

### Check the attachments on an event

Office. Ask what files are attached to the fall retreat event in Planning Center, such as a floor plan or a vendor contract, without opening the calendar and clicking through.

### Answer the questions on an event form

Volunteers. When someone asks what a registrant answered on a Planning Center calendar event form, pull the answers up in one ask instead of exporting them.

### Review which apps can reach your account

Admin. Ask which connected applications and personal access tokens exist on your Planning Center organization, and revoke a token that is no longer needed.

## Elaichi vs Zapier MCP vs Composio for Planning Center

All three can connect Planning Center to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Planning Center tools | Allow or restrict single Planning Center tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Planning Center call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Planning Center to Claude?

First, connect Planning Center in Elaichi. Planning Center asks you to register an OAuth application inside its own developer settings, so somebody brings that client ID and secret once, or pastes a Planning Center API key instead if that is easier. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in with your own Planning Center login and you are done.

### Does Planning Center work with ChatGPT and Cursor as well as Claude?

Yes. Once Planning Center is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Planning Center once and every client uses it.

### What can an AI agent actually do with my Planning Center data?

An agent can look up a person in Planning Center, read calendars and events, see which rooms and resources an event uses, list open conflicts, pull attachments and form answers, and review the applications and tokens connected to your organization. In practice, you ask things like which events this Saturday still have a room conflict. Short, specific asks work better than long paragraphs.

### Does connecting Planning Center give the AI access to everyone's records?

No. Each person signs in to Planning Center as themselves, so the agent only sees the people, calendars and events that person could already open in Planning Center. Elaichi can narrow that access further for a role or an individual, and it never widens it.

### Can my team share one Planning Center connection?

Yes. One person connects Planning Center in Elaichi and shares it with a team, and nobody else ever handles the client ID, secret or API key. Each teammate still signs in as themselves, so the audit log names the actual person behind every Planning Center lookup.

### Can I stop an agent from deleting or changing things in Planning Center?

Yes. Restrictions in Elaichi work per action, set on a role or on one person, so you can allow reading Planning Center people and calendars while restricting anything that revokes a token or changes a record. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Planning Center connection when someone leaves?

Offboarding that person in Elaichi ends their access to Planning Center through every client at once. A shared Planning Center connection keeps working for everyone else on the team. If you ever want it gone entirely, disconnecting Planning Center once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Planning Center MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Planning Center is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Planning Center?

Yes. Both let Claude, ChatGPT or Cursor use Planning Center. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Planning Center call.

### How is Elaichi different from Composio for Planning Center?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Planning Center: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 776 Planning Center tools

Every tool below is callable through https://api.elaichi.ai/mcp once Planning Center is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Planning Center API connected applications** (List). Planning Center API: list ConnectedApplication records. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center API connected application by ID** (Get). Planning Center API: get one ConnectedApplication by id. Required: id.
- **List all Planning Center API mau** (List). Planning Center API: list OauthApplicationMau records. Monthly Active Users for an Oauth Application. A "Monthly Active User" is any person who has been issued an Oauth token during that month. Historical data will be kept for 24 months. _Note:_ There is no historical data before mid-February 2019. Required: oauth_application_id. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center API mau by ID** (Get). Planning Center API: get one OauthApplicationMau by id. Monthly Active Users for an Oauth Application. A "Monthly Active User" is any person who has been issued an Oauth token during that month. Historical data will be kept for 24 months. _Note:_ There is no historical data before mid-February 2019. Required: id, oauth_application_id.
- **List all Planning Center API oauth applications** (List). Planning Center API: list OauthApplication records. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center API oauth application by ID** (Get). Planning Center API: get one OauthApplication by id. Required: id.
- **List all Planning Center API organization** (List). Planning Center API: get the organization (API's root record).
- **List all Planning Center API people** (List). Planning Center API: list ConnectedApplicationPerson records. Required: connected_application_id. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center API person by ID** (Get). Planning Center API: get one ConnectedApplicationPerson by id. Required: id, connected_application_id.
- **List all Planning Center API person** (List). Planning Center API: get the Person of a PersonalAccessToken (one record, via /api/v2/personal_access_tokens/{personal_access_token_id}/person). Required: personal_access_token_id.
- **List all Planning Center API personal access tokens** (List). Planning Center API: list PersonalAccessToken records. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center API personal access token by ID** (Get). Planning Center API: get one PersonalAccessToken by id. Required: id.
- **Create a Planning Center API personal access tokens revoke** (Create). Planning Center API: revoke action on a PersonalAccessToken. Revokes a personal access token Takes no payload, and is available to both organization administrators and the owner of the personal access token. Required: personal_access_token_id.
- **List all Planning Center calendar answers** (List). Planning Center Calendar: list EventResourceAnswer records. An answer to a question in a room or resource request. Required: event_resource_request_id. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar answer by ID** (Get). Planning Center Calendar: get one EventResourceAnswer by id. An answer to a question in a room or resource request. Required: id, event_resource_request_id.
- **List all Planning Center calendar attachments** (List). Planning Center Calendar: list Attachment records. A file or external link attached to an event. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar attachment by ID** (Get). Planning Center Calendar: get one Attachment by id. A file or external link attached to an event. Required: id.
- **List all Planning Center calendar calendars** (List). Planning Center Calendar: list Calendar records. Calendars associated with an Organization. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar calendar by ID** (Get). Planning Center Calendar: get one Calendar by id. Calendars associated with an Organization. Required: id.
- **List all Planning Center calendar conflicts** (List). Planning Center Calendar: list Conflict records. A conflict between two events caused by overlapping event resource requests. If the conflict has been resolved, resolved_at will be present. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar conflict by ID** (Get). Planning Center Calendar: get one Conflict by id. A conflict between two events caused by overlapping event resource requests. If the conflict has been resolved, resolved_at will be present. Required: id.
- **List all Planning Center calendar containing resource** (List). Planning Center Calendar: get the ContainingResource of a RoomSetup (one record, via /calendar/v2/room_setups/{room_setup_id}/containing_resource). The containing record for a RoomSetup. Can be a Resource or an Organization. Required: room_setup_id.
- **List all Planning Center calendar event connections** (List). Planning Center Calendar: list EventConnection records. A connection between a Calendar event and a record in another product. Required: event_id. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar event connection by ID** (Get). Planning Center Calendar: get one EventConnection by id. A connection between a Calendar event and a record in another product. Required: id, event_id.
- **Create a Planning Center calendar event connection** (Create). Planning Center Calendar: create a EventConnection. Body: JSON:API data.type "EventConnection" and data.attributes (assignable: connected_to_id, connected_to_name, connected_to_type, product_name, promoted). Required: data, event_id.
- **Update a Planning Center calendar event connection by ID** (Update). Planning Center Calendar: update a EventConnection. Body: JSON:API data.type "EventConnection" and the data.attributes to change (assignable: connected_to_id, connected_to_name, connected_to_type, product_name, promoted). Required: id, data, event_id.
- **Delete a Planning Center calendar event connection by ID** (Delete). Planning Center Calendar: delete a EventConnection. Required: id, event_id.
- **List all Planning Center calendar event instances** (List). Planning Center Calendar: list EventInstance records. A specific occurrence of an event. If the event is recurring, recurrence will be set and recurrence_description will provide an overview of the recurrence pattern. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar event instance by ID** (Get). Planning Center Calendar: get one EventInstance by id. A specific occurrence of an event. If the event is recurring, recurrence will be set and recurrence_description will provide an overview of the recurrence pattern. Required: id.
- **List all Planning Center calendar event resource requests** (List). Planning Center Calendar: list EventResourceRequest records. A room or resource request for a specific event. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar event resource request by ID** (Get). Planning Center Calendar: get one EventResourceRequest by id. A room or resource request for a specific event. Required: id.
- **List all Planning Center calendar event times** (List). Planning Center Calendar: list EventTime records. Start and end times for each event instance. In the Calendar UI, these are represented under the "Schedule" section and may include "Setup" and "Teardown" times for the instance. Required: event_instance_id. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **List all Planning Center calendar events** (List). Planning Center Calendar: list Event records. An event. May contain information such as who owns the event, visibility on Church Center and a public-facing summary. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar event by ID** (Get). Planning Center Calendar: get one Event by id. An event. May contain information such as who owns the event, visibility on Church Center and a public-facing summary. Required: id.
- **List all Planning Center calendar feeds** (List). Planning Center Calendar: list Feed records. A feed belonging to an organization. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar feed by ID** (Get). Planning Center Calendar: get one Feed by id. A feed belonging to an organization. Required: id.
- **List all Planning Center calendar job statuses** (List). Planning Center Calendar: list JobStatus records. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar job status by ID** (Get). Planning Center Calendar: get one JobStatus by id. Required: id.
- **List all Planning Center calendar organization** (List). Planning Center Calendar: get the organization (Calendar's root record).
- **List all Planning Center calendar people** (List). Planning Center Calendar: list Person records. The people in your organization with access to Calendar. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar person by ID** (Get). Planning Center Calendar: get one Person by id. The people in your organization with access to Calendar. Required: id.
- **List all Planning Center calendar report templates** (List). Planning Center Calendar: list ReportTemplate records. A template for generating a report. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar report template by ID** (Get). Planning Center Calendar: get one ReportTemplate by id. A template for generating a report. Required: id.
- **Create a Planning Center calendar report template** (Create). Planning Center Calendar: create a ReportTemplate. Body: JSON:API data.type "ReportTemplate" and data.attributes (assignable: body, description, title). Required: data.
- **Update a Planning Center calendar report template by ID** (Update). Planning Center Calendar: update a ReportTemplate. Body: JSON:API data.type "ReportTemplate" and the data.attributes to change (assignable: body, description, title). Required: id, data.
- **Delete a Planning Center calendar report template by ID** (Delete). Planning Center Calendar: delete a ReportTemplate. Required: id.
- **List all Planning Center calendar required approvals** (List). Planning Center Calendar: list RequiredApproval records. Represents the relationship between a Resource and a Resource Approval Group. Required: resource_approval_group_id. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar required approval by ID** (Get). Planning Center Calendar: get one RequiredApproval by id. Represents the relationship between a Resource and a Resource Approval Group. Required: id, resource_approval_group_id.
- **List all Planning Center calendar resource approval groups** (List). Planning Center Calendar: list ResourceApprovalGroup records. A group of people that can be attached to a room or resource in order to require their approval for booking. The connector pages through all results (offset; limit sets the page size, 1 to 100, Planning Center's default 25).
- **Get single Planning Center calendar resource approval group by ID** (Get). Planning Center Calendar: get one ResourceApprovalGroup by id. A group of people that can be attached to a room or resource in order to require their approval for booking. Required: id.
- ...and 726 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
