# ChurchSuite MCP server > Read ChurchSuite contacts, children, small groups, rotas, events and attendance; add contact notes. A hosted remote MCP server by usefulapi.io, an independent service (not affiliated with ChurchSuite). - Server URL: https://churchsuite.usefulapi.io/mcp - Transport: Streamable HTTP, OAuth sign-in - Status: live - Page: https://usefulapi.io/churchsuite/ ## Connect - Claude (claude.ai, Desktop): Customize → Connectors → Add custom connector, name ChurchSuite, URL https://churchsuite.usefulapi.io/mcp. Prefilled dialog: https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=ChurchSuite&connectorUrl=https%3A%2F%2Fchurchsuite.usefulapi.io%2Fmcp - Claude Code: `claude mcp add --transport http churchsuite https://churchsuite.usefulapi.io/mcp`, then run `/mcp` to log in. As a plugin: `claude plugin marketplace add https://usefulapi.io/claude/marketplace.json`, then `claude plugin install churchsuite@usefulapi`. - Codex: `codex mcp add churchsuite --url https://churchsuite.usefulapi.io/mcp`, then `codex mcp login churchsuite`. - ChatGPT: Plugins → Add custom MCP server, authentication OAuth. - Cursor, VS Code and other MCP clients: add the URL as a remote MCP server. Add only the URL. Do not add an `Authorization` header or an API key to the client config. The server signs you in with OAuth: the login page asks for your **Client ID** and **Client secret**. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401. ## Before you connect A ChurchSuite administrator enables **API access** on a user profile (Account Settings → **Users**; a dedicated user for this integration is best). That API user then generates a **client secret** and copies its client ID. The user's ChurchSuite permissions decide which modules this server can see, so grant only what you need. API access may depend on your ChurchSuite plan. Your credentials are used only to call the ChurchSuite API on your behalf; your account is identified by your church's ChurchSuite account id. ## Example requests - Which small groups meet on Wednesdays, and where and when? - Who serves in our welcome team ministry? - How many people attended our services over the last month? - Add a note to Jane Smith's record: visited her at home today. ## Pricing - Free: $0, 50 tool calls / month - Pro: $9/mo · $90/yr per church account, 10,000 tool calls / month - Pro+: $39/mo · $390/yr per church account, 100,000 tool calls / month Each paid plan covers this ChurchSuite server only. ## Tools (33) ### Read only (28) - `churchsuite_get_account`: Get church account. The church's ChurchSuite account summary: name, unique id, subdomain, time zone, currency, language and first day of week (no billing or data-protection contact details). A good first call. - `churchsuite_list_sites`: List sites. List the church's sites (campuses/congregations: id, name, initials, address). Site ids filter contacts, children, groups, events and plans. - `churchsuite_list_contacts`: List address book contacts. Search or list adult contacts in the Address Book (name, contact details, address, sites, status, tags via tag\_ids). Personal data: ask only for what you need. - `churchsuite_get_contact`: Get a contact. Get one Address Book contact by id: names, sex, date of birth, marital status and spouse id, address, phones, email, job, custom fields, communication preferences, sites, status. - `churchsuite_list_contact_notes`: List contact notes. List the pastoral/admin notes on a contact (content, pinned, visibility, who wrote it and when), pinned first. - `churchsuite_list_contact_tags`: List address book tags. List Address Book tags (id, name, category, whether it is a smart tag). Use a tag id as tag\_ids in list\_contacts to list the people with that tag. - `churchsuite_list_children`: List children. Search or list children in the Children module (name, date of birth, school year, contact details, sites, status, consent flags). Medical and additional-needs fields are left out unless include\_medical is true. - `churchsuite_get_child`: Get a child. Get one child by id (names, date of birth, school, contact details, custom fields, consents, sites, status). Medical and additional-needs fields only with include\_medical: true. - `churchsuite_list_children_groups`: List children's groups. List the Children module's groups (classes/age groups: id, name, entry age, check-in capacity and ratio, status). - `churchsuite_list_small_groups`: List small groups. List small groups (home groups/life groups: name, day, time, frequency, location, description, dates, sign-up options). - `churchsuite_get_small_group`: Get a small group. Get one small group by id (schedule, location, description, custom fields, sign-up options, sites). - `churchsuite_list_small_group_members`: List small group members. List small group memberships (group id, person = contact or child id, status, role ids, joined date). Filter by group to get a group's members, or by contact/child to get a person's groups; look people up with get\_contact / get\_child. - `churchsuite_list_events`: List calendar events. List calendar events (name, start/end, status, category, location, description, sign-up options, sites). Use starts\_after/starts\_before (YYYY-MM-DD) for a date window. - `churchsuite_get_event`: Get a calendar event. Get one calendar event by id (times, status, category, location, description, visibility, sign-up options). - `churchsuite_list_event_categories`: List event categories. List calendar categories (id, name, colour, status). Use the ids as category\_ids in list\_events. - `churchsuite_list_ministries`: List rota ministries. List the Rotas module's ministries (worship team, welcome team…: id, name, description, days, rota and rotation type, status, sites). - `churchsuite_list_ministry_teams`: List ministry teams. List the teams inside rota ministries (id, ministry id, name, order). - `churchsuite_list_ministry_members`: List ministry members. List who serves in rota ministries (ministry id, team id, person = contact or child id, role ids). Look people up with get\_contact / get\_child. - `churchsuite_list_unavailability`: List rota unavailability. List the dates people said they are unavailable to serve (person, description, start/end). Filter by person, ministry or a date window. - `churchsuite_list_rotas`: List rotas. List rotas: one rota per ministry and time period (id, name, ministry id, start/end dates, times, accept/decline on or off, draft or published). Default view: active rotas. - `churchsuite_list_rota_dates`: List rota dates. List rota dates (serving dates: id, rota id, serving\_at date-time, notes, service notes). serving\_after and serving\_before EXCLUDE the date given: for one day D pass the day before and the day after, or use churchsuite\_list\_servings\_on\_date. - `churchsuite_list_rota_servings`: List rota servings. List rota servings: who is down to serve on which rota date (person = contact or child with first/last name, date id, rota id, status accepted/declined/pending or null when accept/decline is off, clashes with other servings or unavailability). ChurchSuite does not return the role of a serving. - `churchsuite_list_servings_on_date`: Who serves on a date. Who serves on one day, across ministries: each rota date on that day with its ministry and rota names, time, notes and the people serving (name, contact/child id, accepted/declined/pending, clashes). Dates with nobody assigned are listed in dates\_without\_servings. ChurchSuite's API has no role per serving and no unfilled-slot data; the roles people can serve are in churchsuite\_list\_ministry\_members. Reads several API pages in one call. - `churchsuite_list_service_plans`: List service plans. List service plans from the Planning module (name, date, time, status, linked event, sites). - `churchsuite_list_plan_items`: List service plan items. List the running order of one or more service plans (items: type, name, song arrangement, duration, start time, notes, people). - `churchsuite_list_giving_funds`: List giving funds. List the church's giving funds (id, name, description, Gift Aid / tax-deductible flags, whether shown in Donate, status). Funds only: no donors, donations or amounts. - `churchsuite_list_gatherings`: List attendance gatherings. List the Attendance module's gatherings (services/meetings whose attendance is counted: id, name, sites, status). - `churchsuite_list_attendance_records`: List attendance records. List attendance records (headcounts per gathering and date: total number, total people, notes), sorted by date. Filter by gathering, weekday or a date window (YYYY-MM-DD). ### Changes data (1) - `churchsuite_add_contact_note`: Add a note to a contact. WRITE: add a new note to a contact's record in ChurchSuite (it is visible to other ChurchSuite users who can see the contact, unless private\_to\_me is true). Only adds a note: never edits or deletes anything, sends nothing to the contact. ### Your usefulapi plan (4) - `churchsuite_usage_status`: Usage status (free-tier meter). Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. - `churchsuite_request_feature`: Request a missing feature. Tell usefulapi that the user needs something the ChurchSuite tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. - `churchsuite_upgrade`: Upgrade to Pro or Pro+. Get a paid plan for ChurchSuite (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus\_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place: call without confirm first, as the reply states the exact charge for this account (the price difference for the rest of the period, or in a free Pro trial the full Pro+ price, as the trial ends); then call with confirm: true. Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter. - `churchsuite_cancel_subscription`: Cancel the Pro subscription. Cancel the caller's ChurchSuite Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run churchsuite\_upgrade later to undo the cancel before the period ends. Does not count against the meter. ## FAQ ### What can I do with ChurchSuite in Claude or ChatGPT? Find small groups, their times and members. See who serves in a rota ministry. Report attendance over a period. Look up upcoming events and service plans. Find a contact and read or add a note. See [what you can do](https://usefulapi.io/churchsuite/#uses) for the details. ### Is this an official ChurchSuite product? No. usefulapi is an independent service. It is not affiliated with or endorsed by ChurchSuite. The server calls the ChurchSuite API with your own ChurchSuite access, so it sees only the data that your account can see. ### Can I connect ChurchSuite to Claude or ChatGPT? Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See [the setup steps](https://usefulapi.io/churchsuite/#connect). ### What do I need to connect? The login page asks for your **Client ID** and **Client secret**. See [Before you connect](https://usefulapi.io/churchsuite/#setup) for where to find them. ### Do I put my ChurchSuite key or an Authorization header in the client config? No. Add only the URL. Do not add an `Authorization` header or an API key to the client config. The server signs you in with OAuth: the login page asks for your **Client ID** and **Client secret**. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401. ### How do you keep my ChurchSuite credentials? The login stores them encrypted in the authorization grant of your connection. The server uses them to call the ChurchSuite API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in ChurchSuite. ### Can the AI change my ChurchSuite data? Yes, if you approve it. 1 of the 29 ChurchSuite tools can create or change data. The other 28 are marked read-only. Most MCP clients ask you to approve a tool call before it runs. ### What does it cost? The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this ChurchSuite server only. Cancel any time: your paid plan then runs to the end of the paid period. Run `churchsuite_usage_status` to see how many calls you used. ### How do I subscribe or cancel? Ask the AI to run `churchsuite_upgrade` and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run `churchsuite_cancel_subscription`. Your paid plan continues to the end of the paid period. ### What if a ChurchSuite tool that I need is missing? Tell the AI what you wanted to do. It can send the request with `churchsuite_request_feature`. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day. ### Which AI clients can I use? Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others. ## Links - [ChurchSuite MCP server page](https://usefulapi.io/churchsuite/) - [All servers](https://usefulapi.io/llms.txt) - [Terms of Service](https://usefulapi.io/terms/) - [Privacy Policy](https://usefulapi.io/privacy/) - Support: support@usefulapi.io