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.
- OAuth or API key
- Free 14-day trial
- No credit card
Which calendar conflicts are still open for this weekend's events?
Working in Planning Center with Elaichi
-
List all Planning Center API connected applications
-
Get single Planning Center API connected application by ID
-
List all Planning Center API mau
How to connect Planning Center to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Planning Center MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Planning Center MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Planning Center through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Planning Center is logged.
-
Pastoral care
Pull up a person before a visit
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.
-
Events
Find every open calendar conflict
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.
-
Facilities
See what a room is booked for
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.
-
Office
Check the attachments on an event
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.
-
Volunteers
Answer the questions on an event form
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.
-
Admin
Review which apps can reach your account
Ask which connected applications and personal access tokens exist on your Planning Center organization, and revoke a token that is no longer needed.
Try asking
- “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.”
What connecting Planning Center gets you
6 screens from Elaichi, each doing one job for your Planning Center account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about people and events in plain words.
Answers come from live Planning Center people, calendars and conflicts, not from a stale export.
Copy the endpoint
AI apps
One endpoint reaches Planning Center from every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Tool catalog
776 Planning Center tools, no custom code.
People, calendars, events, conflicts, attachments and connected applications, all ready to use.
Toolboxes
Every team gets its own Planning Center toolbox.
Pastoral care sees people, facilities sees calendars and resources, each scoped to their work.
Shared connections
Teammates use Planning Center without seeing a credential.
One person connects, shares with teams, and everyone still signs in as themselves.
Audit log
Know who looked up which person and when.
Every Planning Center call is logged with who, what, type and resource, append-only.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Planning Center digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch people
Planning Center
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Planning Center
Queued
Workflows
A schedule drafts the weekly calendar digest.
Events and conflicts are fetched, grouped, drafted, approved by a person, then posted to Planning Center.
Planning Center health
Refreshed 4 minutes ago · every 15 minutes · from the people collection
People
1,284 ↓ 12%
Calendars
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
People created
Last 14 days
By team
Share of activity
Pastoral care 34%
Events 27%
Facilities 21%
Office 18%
Collections and dashboards
Planning Center health, computed without a model.
Four metrics, 14 days of records created, and a breakdown by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Planning Center tools for your AI agents
776 tools are ready to call through Elaichi's MCP endpoint the moment you connect Planning Center, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 228 of 776 Planning Center tools here. Connect Planning Center and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
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 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.
Put Planning Center in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot