Who is serving on Sunday, and which first-time guests still need a follow-up?
Planning Center connects Memtro to your church. It reads people with status and membership and their workflow cards, lists, workflows with card counts, service types and plans with who is scheduled to serve, calendar event instances, groups and Check-Ins headcounts. When asked, and once an administrator has granted the action by name, it can add a person or a note, change a name or membership, add an email, put someone on a workflow, move or assign a card and add a group member. Assignees and note subscribers may be told. Birthdates, addresses and phone numbers are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Planning Center tool, reads what it needs, and answers with the source cited.
These tools change something in Planning Center. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Planning Center, choosing the same kinds; the tab shows Planning Center's own steps. Each event can start a job, with the event as its input. Planning Center signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Planning Center is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Planning Center + MemtroWho is serving on Sunday morning this week?
Which positions still need people for next Sunday?
How many first-time guest cards are overdue?
What was our headcount over the last month?
Put Maya Okafor on the first-time guests workflow
Tom Reilly, worship leader at a church in the Northwind network, asked who was serving on Sunday and what was still needed. Memtro listed the team by position with who had confirmed, and named two positions still open on the plan.
Priya Sharma, welcome coordinator at Acme Community Church, asked Memtro to put a visitor on the first-time guests workflow and give the card to Dan Fletcher. Memtro added the card and assigned it to Dan, whom Planning Center may notify.
The teams that lean on Planning Center most, a question each of them asks, and what they connect beside it.
A record in Planning Center is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Capsule CRM
Copper
Freshsales
Dialpad
folk
Insightly
Nutshell
Vitally
Nimble
OnePageCRM
Salesflare
CloudTalk
Hunter
Lusha
Ontraport
Reply
Streak
EspoCRM
Planhat
Bloomerang
Givebutter
Raisely
People Data Labs
ChurchSuite
Affinity
Kommo
Pipeline CRM
KeapIn Planning Center, go to api.planningcenteronline.com → Personal Access Tokens → New Personal Access Token.
Copy the Application ID and the Secret when the token is made. The token acts as the user who made it, so use a dedicated user with view rights, and edit rights only where Memtro should act.
In Memtro, open Connections → Planning Center and paste them into Application ID and Secret.
Ask your first question: who is serving on Sunday morning this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Planning Center tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a person's profile (people subscribed to the note category may be told); add a person to Planning Center People; change a person's name, nickname or membership; add an email address to a person; put a person on a workflow (the assignee may be told); move a workflow card forward or back, skip a step, remove, restore or unsnooze it; assign a workflow card to someone (they may be told); add a note to a workflow card; add a person to a group as a member. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Application ID and Secret. In Planning Center, go to api.planningcenteronline.com → Personal Access Tokens → New Personal Access Token.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Planning Center, choosing the same kinds; the tab shows Planning Center's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time