Attendance for the trustees
Sarah Chen, church administrator at Acme Community Church, asked how attendance had gone over the last month for the trustees' meeting. Memtro listed the headcount for each gathering by date and gave the total.
What is on in the church calendar, and how many came last Sunday?
ChurchSuite connects Memtro to your church's address book, calendar and planning. It reads contacts with name, email, status and sites, tags, sites, calendar events in a date window, small groups, service plans and attendance totals per gathering. When asked, and once an administrator has granted the action by name, it can add a note to a contact, event, group or plan, add a contact, tag a contact, and sign a contact up to an event without a confirmation email. Phone numbers, addresses, dates of birth and collection amounts are never returned, and small group members are not listed.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right ChurchSuite tool, reads what it needs, and answers with the source cited.
These tools change something in ChurchSuite. 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.
Once ChurchSuite 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.
What is in the church calendar this week?
How many people came to our gatherings last month?
Which small groups meet on a Wednesday?
Is the Easter Sunday service plan published yet?
Sign Tom Reilly up to the newcomers lunch
Sarah Chen, church administrator at Acme Community Church, asked how attendance had gone over the last month for the trustees' meeting. Memtro listed the headcount for each gathering by date and gave the total.
Maya Okafor, pastoral assistant at Northwind Church, asked Memtro to sign a newcomer up to the welcome lunch and tag him as a newcomer. Memtro signed the contact up in ChurchSuite and added the tag. No confirmation email was sent.
The teams that lean on ChurchSuite most, a question each of them asks, and what they connect beside it.
A record in ChurchSuite 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.
In ChurchSuite, an administrator turns on API access for a dedicated user profile with only the modules Memtro should see. That user's identifier, shown on their profile, is the client ID.
Signed in as that user, open My profile → API Secrets → Add secret and copy the secret when it is created.
In Memtro, open Connections → ChurchSuite and paste them into Client ID and Client secret.
Ask your first question: what is in the church calendar this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The ChurchSuite tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to an address book contact; add a note to a calendar event; add a note to a small group; add a note to a service plan; add a contact to the address book; tag an address book contact; sign a contact up to a calendar event (no confirmation email is sent). 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.
Client ID and Client secret. In ChurchSuite, an administrator turns on API access for a dedicated user profile with only the modules Memtro should see. That user's identifier, shown on their profile, is the client ID.
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