> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns. > > **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal): > ```bash > npx -y @scalekit-inc/cli setup -y > ``` > > Global: > ```bash > npm install -g @scalekit-inc/cli > scalekit setup -y > ``` > > Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`. > Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim. > [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/) --- # Connect AI agents to the Planning Center MCP server The Planning Center MCP connector routes your AI agent's tool calls to Planning Center's own MCP server through Scalekit. Each user signs in to Planning Center once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 64 tools. **Authentication:** OAuth 2.1/DCR **Categories:** Productivity, Calendar, CRM & Sales **Tools:** 64: 62 read, 2 write, 0 destructive **Users sign in with:** OAuth **OAuth app:** Scalekit's or your own **Built by:** Vendor MCP **Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=PLANNINGCENTERMCP) ## Setup 1. ### Install the SDK **Node.js** ```bash npm install @scalekit-sdk/node dotenv ``` **Python** ```bash pip install scalekit-sdk-python python-dotenv ``` 2. ### Set your credentials Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**. ```sh title=".env" SCALEKIT_ENVIRONMENT_URL= SCALEKIT_CLIENT_ID= SCALEKIT_CLIENT_SECRET= ``` 3. ### Create the Planning Center MCP connection In **AgentKit > Connections**, create a Planning Center MCP connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/). Scalekit credentials are available for Planning Center MCP server, so you don't need to register an OAuth app. 4. ### Authorize a user and make your first call **Node.js** (`quickstart.mts`) ```typescript import { ScalekitClient } from '@scalekit-sdk/node' import 'dotenv/config' import { createInterface } from 'node:readline/promises' const scalekit = new ScalekitClient( process.env.SCALEKIT_ENVIRONMENT_URL, process.env.SCALEKIT_CLIENT_ID, process.env.SCALEKIT_CLIENT_SECRET, ) const actions = scalekit.actions const connector = 'planningcentermcp' const identifier = 'user_123' // Generate an authorization link for the user const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier }) console.log('Authorize Planning Center MCP:', link) const rl = createInterface({ input: process.stdin, output: process.stdout }) await rl.question('Press Enter after authorizing...') rl.close() // Make your first call const result = await actions.executeTool({ connector, identifier, toolName: 'planningcentermcp_calendar_calendars', toolInput: {}, }) console.log(result) ``` ```bash npx tsx quickstart.mts ``` **Python** (`quickstart.py`) ```python import os from scalekit import ScalekitClient from dotenv import load_dotenv load_dotenv() scalekit_client = ScalekitClient( env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"), client_id=os.getenv("SCALEKIT_CLIENT_ID"), client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"), ) actions = scalekit_client.actions connection_name = "planningcentermcp" identifier = "user_123" # Generate an authorization link for the user link_response = actions.get_authorization_link( connection_name=connection_name, identifier=identifier, ) print("Authorize Planning Center MCP:", link_response.link) input("Press Enter after authorizing...") # Make your first call result = actions.execute_tool( tool_input={}, tool_name="planningcentermcp_calendar_calendars", connection_name=connection_name, identifier=identifier, ) print(result) ``` ```bash python quickstart.py ``` Each user signs in once. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses. ## Tools Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool). **Node.js** ```typescript const result = await actions.executeTool({ toolName: 'planningcentermcp_calendar_calendars', toolInput: {}, connector: 'planningcentermcp', identifier: 'user_123', }) ``` **Python** ```python result = actions.execute_tool( tool_name="planningcentermcp_calendar_calendars", tool_input={}, connection_name="planningcentermcp", identifier="user_123", ) ``` `result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call. ### `planningcentermcp_calendar_calendars` CalendarCalendars · Read-only List the calendars configured in Planning Center Calendar (e.g. "Youth Ministry", "Staff", "Worship"). Calendars partition an organization's events by ministry or context. Use this tool to see which calendars exist, resolve a calendar name to its id, or look up a calendar's description, color, or default status. This tool returns the full list of calendars; there is no server-side filtering by name or any other attribute. Organizations have only a small handful of calendars, so retrieve them all and match the one you want by name client-side. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `name`, `-name`. - `output_fields` (`array`, optional): Specify which fields to include in the response. Example input: `{}` ### `planningcentermcp_calendar_conflicts` CalendarConflicts · Read-only Read booking conflicts in Planning Center Calendar — situations where two events have overlapping resource requests for the same room or piece of equipment. A conflict carries the contested `resource`, the `winner` event once staff have picked one, and `resolved_at` when the conflict has been settled. Use `filter: ["unresolved"]` to answer "what's overbooked right now" — that's the operationally interesting set, and it inherently scopes to conflicts on upcoming events (past-only conflicts drop out). `filter: ["resolved"]` returns conflicts that have been settled. The `resource` relationship id chains to the calendar_resources tool; the `winner` event id chains to calendar_events. Both are surfaced as JSON:API relationship linkages on every response. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `filter` (`array`, optional): Restrict to "unresolved" (currently overbooked, scoped to upcoming events) or "resolved" (settled). - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `resolved_at`, `-resolved_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. Example input: `{}` ### `planningcentermcp_calendar_event_instances` CalendarEventInstances · Read-only Search specific occurrences of events in Planning Center Calendar — the "what is happening at this date and time" surface. An event instance is one occurrence of a parent event: a single Wednesday of a weekly Bible Study, next Sunday's service, or the one date of a one-off event. Recurring instances expose `recurrence` and `compact_recurrence_description` for human-readable patterns. Prefer this tool over `calendar_events` when the question is about specific dates or times ("what's happening next Sunday?", "when does the youth retreat happen?", "the next four Wednesdays of Bible Study"). Use `calendar_events` instead when the question is about the parent event template regardless of when it occurs. For questions about one particular event, resolve it with `calendar_events` and pass its id as `event_id` — more reliable than an `event_name` substring match when several events share a word. Pair it with `filter: ["future"]` for "when does this happen next?". Use `filter: ["future"]` for upcoming instances without computing a date filter yourself. Filter by name via `event_name` (a phrase-substring match — pass a bare substring like "bible study"; wildcards are not supported), by kind, by date range, by tag, or by calendar. To filter by tag, call `calendar_tags` to resolve a tag name to a tag id, then pass `tag_ids` here to narrow to that ministry, audience, or category. To filter by calendar, call `calendar_calendars` to resolve a calendar name to a calendar id, then pass `calendar_ids` here. `description`, `image_url`, and `kind` are heavier fields (rich HTML, image URL, event kind) and are only returned when you list them explicitly in `output_fields`. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `calendar_ids` (`array`, optional): Filter instances by calendar ids. A single id is the common case. Passing multiple ids returns instances on ANY of those calendars (a union) — `[worship_id, youth_id]` returns instances on either calendar. Resolve calendar names to ids via `calendar_calendars`. - `created_at_end` (`string`, optional): Latest created at to include (inclusive), as YYYY-MM-DD. - `created_at_start` (`string`, optional): Earliest created at to include (inclusive), as YYYY-MM-DD. Pair with created_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `ends_at_end` (`string`, optional): Latest ends at to include (inclusive), as YYYY-MM-DD. - `ends_at_start` (`string`, optional): Earliest ends at to include (inclusive), as YYYY-MM-DD. Pair with ends_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `event_id` (`string`, optional): Limit to occurrences of this event, resolved via the calendar_events tool. Prefer this over event_name whenever you already know which event you mean. Only the "future" filter value is supported when scoped to an event; the approval-status filter values cannot be combined with event_id. - `event_name` (`string`, optional): Filter instances by name (defaults to the parent event's name; can be overridden per instance). Phrase-substring match — pass a bare substring like "bible study"; wildcards are not supported. - `filter` (`array`, optional): Named filter scopes. Use ["future"] to return only instances that have not yet ended. Approval-status scopes filter by each instance's booking status: "approved" also includes shared instances, "pending" also includes unresolved conflicts, and "rejected" also includes lost instances. The approval-status scopes are not available when event_id is supplied. - `include` (`array`, optional): Specify which relationships to include in the response. - `kind` (`string`, optional): Filter instances by their parent event's kind. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `created_at`, `-created_at`, `updated_at`, `-updated_at`, `starts_at`, `-starts_at`, `ends_at`, `-ends_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `starts_at_end` (`string`, optional): Latest starts at to include (inclusive), as YYYY-MM-DD. - `starts_at_start` (`string`, optional): Earliest starts at to include (inclusive), as YYYY-MM-DD. Pair with starts_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `tag_ids` (`array`, optional): Filter instances by tag ids. A single id is the common case. When you pass multiple ids, upstream composes them as OR within a tag group and AND across tag groups (ungrouped tags each count as their own group) — so `[youth_ministry_id, sunday_service_id]` returns instances tagged with BOTH, not either. Resolve tag names via `calendar_tags`. - `updated_at_end` (`string`, optional): Latest updated at to include (inclusive), as YYYY-MM-DD. - `updated_at_start` (`string`, optional): Earliest updated at to include (inclusive), as YYYY-MM-DD. Pair with updated_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. Example input: `{}` ### `planningcentermcp_calendar_events` CalendarEvents · Read-only Search events in Planning Center Calendar. Calendar is the organization-wide event discovery surface and absorbs events originating in Services, Groups, and Registrations — a Sunday service plan, a small group meeting, and an event signup all appear here alongside Calendar-native events. Use this tool to find events across products: by name, approval status, Church Center visibility, feed, created/updated date, or the `future` named scope for upcoming events. Two views of the same record are simultaneously true: an event surfaced here may also be the source-of-truth for a product-native tool. When the user wants product-specific detail — a Services plan's order of service, a Registrations signup's attendees, a Group's roster — chain into `services_plans`, `registrations_signups`, or `groups_events` after discovering the event here. This tool doesn't surface which calendar an event belongs to — no calendar field or include here. To work by calendar, resolve the calendar id with `calendar_calendars` and pass it to `calendar_event_instances` as `calendar_ids`. That returns one row per occurrence, so dedupe on the `event` relationship id to count events. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `approval_status` (`string`, optional): Filter by approval status: 'A' approved, 'P' pending, 'R' rejected. One of: `A`, `P`, `R`. - `created_at_end` (`string`, optional): Latest created at to include (inclusive), as YYYY-MM-DD. - `created_at_start` (`string`, optional): Earliest created at to include (inclusive), as YYYY-MM-DD. Pair with created_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `featured` (`boolean`, optional): Filter by whether the event is featured on Church Center. - `feed_id` (`string`, optional): Filter events by the feed they belong to (e.g. the Services, Groups, or Registrations feed that absorbs them into Calendar). - `filter` (`array`, optional): Use ["future"] to return only events that have not yet ended, excluding past events. - `include` (`array`, optional): Specify which relationships to include in the response. - `link_only` (`boolean`, optional): Filter by whether the event is published to Church Center through a direct link only. - `name` (`string`, optional): Filter events by name. Matches exactly unless you include a '%' wildcard for partial matches. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `updated_at_end` (`string`, optional): Latest updated at to include (inclusive), as YYYY-MM-DD. - `updated_at_start` (`string`, optional): Earliest updated at to include (inclusive), as YYYY-MM-DD. Pair with updated_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `visible_in_church_center` (`boolean`, optional): Filter by whether the event's Church Center visibility is Published (true) or Hidden (false). Example input: `{}` ### `planningcentermcp_calendar_resource_bookings` CalendarResourceBookings · Read-only Search resource bookings in Planning Center Calendar — a successful reservation of a room or piece of equipment for an event, over a start/end time range. Use this tool to answer "what's booked?" questions, e.g. whether a room is reserved during a time window, or what's reserved for a particular event or occurrence. Provide `resource_id` (resolved via `calendar_resources`) to scope to a single room or resource, `event_id` (resolved via `calendar_events`) to scope to a single event's bookings, or `event_instance_id` (resolved via `calendar_event_instances`) to scope to one specific occurrence — provide at most one of the three. Omit all three to search bookings across the whole organization. Recurring events (weekly services, ongoing classes) attach their bookings to the individual event instance rather than the parent event, so prefer `event_instance_id` for "what's booked for this Sunday/this occurrence?" questions. Use the `event_resource_request` include to identify what was reserved and its approval status; chain into `calendar_events` for richer event detail — this tool does not include the full event record. A booking is a successful reservation, distinct from a scheduling conflict (overlapping reservations awaiting staff resolution) — for "what's overbooked?" questions, use `calendar_conflicts` instead. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `approval_status` (`string`, optional): Limit to bookings with this approval status. This is a single value, not a list — use a compound value such as "approved_pending" to match multiple statuses in one call, since the API ORs statuses within a single value but ANDs separate filter values. Cannot be combined with event_id or event_instance_id (neither route supports approval-status scopes). One of: `approved`, `pending`, `rejected`, `approved_pending`, `approved_rejected`, `pending_rejected`, `approved_pending_rejected`. - `ends_at_end` (`string`, optional): Latest ends at to include (inclusive), as YYYY-MM-DD. - `ends_at_start` (`string`, optional): Earliest ends at to include (inclusive), as YYYY-MM-DD. Pair with ends_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `event_id` (`string`, optional): Limit to bookings for this event, resolved via the calendar_events tool. Provide at most one of resource_id/event_id/event_instance_id. Only the "future" filter value is supported when scoped to an event; approval_status cannot be combined with event_id. - `event_instance_id` (`string`, optional): Limit to bookings for this specific occurrence of an event, resolved via the calendar_event_instances tool. Provide at most one of resource_id/event_id/event_instance_id. Prefer this over event_id for recurring events — their bookings attach to the instance, not the parent event. Only the "future" filter value is supported when scoped to an event instance; approval_status cannot be combined with event_instance_id. - `filter` (`array`, optional): Use ["future"] to limit to bookings that haven't ended yet. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `created_at`, `-created_at`, `ends_at`, `-ends_at`, `starts_at`, `-starts_at`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `resource_id` (`string`, optional): Limit to bookings of this room or resource, resolved via the calendar_resources tool. Provide at most one of resource_id/event_id/event_instance_id. - `starts_at_end` (`string`, optional): Latest starts at to include (inclusive), as YYYY-MM-DD. - `starts_at_start` (`string`, optional): Earliest starts at to include (inclusive), as YYYY-MM-DD. Pair with starts_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. Example input: `{}` ### `planningcentermcp_calendar_resources` CalendarResources · Read-only Search rooms and equipment available for booking in Planning Center Calendar. A "resource" is either a physical space (kind='Room') or an item of equipment (kind='Resource'). Each resource carries a `path_name` in the output showing its folder location (e.g. "Main Campus/Sanctuary"); path-based filtering isn't supported server-side, but you can scope to a specific folder via `resource_folder_id` (chain from `include: resource_folder`). Use this tool when the question is about *space or equipment booking* — "what rooms can we book?", "list all our A/V equipment", "which resources do we have?". If instead the question is about *check-in setup* (where kids get dropped off, which station a family checks in at), that's a Check-Ins locations concept and belongs to a separate Check-Ins tool. Resource ids returned here chain forward to Calendar tools that answer "is this resource booked at time X." Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `created_at_end` (`string`, optional): Latest created at to include (inclusive), as YYYY-MM-DD. - `created_at_start` (`string`, optional): Earliest created at to include (inclusive), as YYYY-MM-DD. Pair with created_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `filter` (`array`, optional): Use ["rooms"] for rooms only or ["resources"] for equipment only. Named scopes on the organization endpoint; equivalent to `kind=Room` / `kind=Resource`. - `ids` (`array`, optional): Specific resource IDs to retrieve - `include` (`array`, optional): Specify which relationships to include in the response. - `kind` (`string`, optional): Filter by kind: 'Room' for physical bookable spaces, 'Resource' for equipment. One of: `Room`, `Resource`. - `name` (`string`, optional): Filter resources by name. Matches exactly unless you include a '%' wildcard for partial matches. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `created_at`, `-created_at`, `expires_at`, `-expires_at`, `name`, `-name`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `resource_folder_id` (`string`, optional): Filter to resources in a specific folder. Chain from a prior response's `include: resource_folder` linkage, or from a folder id you already have. - `updated_at_end` (`string`, optional): Latest updated at to include (inclusive), as YYYY-MM-DD. - `updated_at_start` (`string`, optional): Earliest updated at to include (inclusive), as YYYY-MM-DD. Pair with updated_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. Example input: `{}` ### `planningcentermcp_calendar_tags` CalendarTags · Read-only Read tags used to organize events in Planning Center Calendar. Tags are the vocabulary an organization uses to categorize events by ministry, audience, or context (e.g. "Youth Ministry", "All-Church"). Use this tool to resolve a tag name to a tag id, browse the available tags, or find tags within a specific tag group. Tag ids chain forward to `calendar_event_instances` via its `tag_ids` filter for server-side filtering of event instances by tag. Server-side filtering of `calendar_events` by tag id is not supported; use the `tags` include on `calendar_events` if you need tag data alongside events. Include `tag_group` to see how tags are grouped (e.g. "Audience", "Ministry"); the "Individual Tags" bucket in the UI corresponds to tags with no tag group and can be filtered via `filter: "individual"`. To list the tag groups themselves, call this tool with `include: ["tag_group"]` and dedupe the `tag_group` relationships client-side. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `church_center_category` (`boolean`, optional): Filter by whether the tag is used as a Church Center category. - `created_at_end` (`string`, optional): Latest created at to include (inclusive), as YYYY-MM-DD. - `created_at_start` (`string`, optional): Earliest created at to include (inclusive), as YYYY-MM-DD. Pair with created_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `filter` (`string`, optional): Use "individual" to return only tags with no tag group (the "Individual Tags" bucket in the UI). One of: `individual`. - `id` (`string`, optional): Filter to a specific tag by its ID. - `include` (`array`, optional): Specify which relationships to include in the response. - `name` (`string`, optional): Filter tags by name. Exact match unless you include a '%' wildcard for partial matches. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `name`, `-name`, `position`, `-position`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `tag_group_id` (`string`, optional): Filter to tags belonging to a specific tag group. - `updated_at_end` (`string`, optional): Latest updated at to include (inclusive), as YYYY-MM-DD. - `updated_at_start` (`string`, optional): Earliest updated at to include (inclusive), as YYYY-MM-DD. Pair with updated_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. Example input: `{}` ### `planningcentermcp_check_ins_check_ins` CheckInsCheckIns · Read-only Search individual check-in records — one row per person per event session, showing who checked in to which event, when, where, and whether they were checked out. Use for attendance questions where individual identity matters (e.g. "who checked in to the 9am service last Sunday", "did the Smith family check in this morning"). Each record covers regular attendees, guests, or volunteers; filter by event, person, date, or check-in category. `checked_out_at` is ambiguous when null: it can mean the person hasn't been picked up yet, OR that the org doesn't record check-outs at all (many don't — they only badge people in). Report what the data shows and surface the ambiguity rather than asserting someone wasn't picked up. Use `include=checked_out_by` to surface the picker-upper when it was recorded. `security_code`, `medical_notes`, `emergency_contact_name`, and `emergency_contact_phone_number` are stripped from every response before it reaches you — the upstream API exposes them to admins, but this tool removes them on both the primary check-in record and any included resources. Sibling tools to disambiguate: - `check_ins_check_ins` (this tool) — one row per person per event session. Use for "who" and "how many" when individual identity matters. - `check_ins_headcounts` — pre-aggregated totals by event/category. Use for "how many" when only the count matters and no PII is needed (and the org actually recorded headcounts). - `services_plans` — planning-side schedules (who's scheduled to play / on the rotation), NOT attendance. To find check-ins for a Registrations signup, follow the chain: `registrations_signups` returns a signup id → pass that as `registration_event_id` on `check_ins_events` → take the resulting Check-Ins event's id → pass it as `event_id` here. The reverse direction (a Check-Ins event back to its source signup) is not exposed. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `account_center_person_id` (`integer`, optional): Limit to check-ins for a specific person. Pass a value returned by `people_search`. Note: one-time-guest check-ins have no person id and are excluded by this filter. - `created_at_end` (`string`, optional): Latest created at to include (inclusive), as YYYY-MM-DD. - `created_at_start` (`string`, optional): Earliest created at to include (inclusive), as YYYY-MM-DD. Pair with created_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `event_id` (`integer`, optional): Limit to check-ins for a specific Check-Ins event. Pass a value returned by `check_ins_events`. - `filter` (`string`, optional): Limit to a check-in category: regular, guest, volunteer, attendee (regular + guest combined), first_time, one_time_guest, not_one_time_guest, checked_out, or not_checked_out. One of: `regular`, `guest`, `volunteer`, `attendee`, `first_time`, `one_time_guest`, `not_one_time_guest`, `checked_out`, `not_checked_out`. - `include` (`array`, optional): Specify which relationships to include in the response. - `location_ids` (`array`, optional): Limit to check-ins at specific locations. Pass values returned by `check_ins_locations`. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `first_name`, `-first_name`, `last_name`, `-last_name`, `number`, `-number`, `created_at`, `-created_at`, `updated_at`, `-updated_at`, `checked_out_at`, `-checked_out_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. Example input: `{}` ### `planningcentermcp_check_ins_event_times` CheckInsEventTimes · Read-only List the individual sessions (event times) configured within a Check-Ins event — e.g. the 9:00 and 11:00 services of a Sunday Service event, or each night of VBS. Returns start times, when the session is visible in check-in UIs (`shows_at`/`hides_at`), and per-session attendance counts (`regular_count`, `guest_count`, `volunteer_count`). Pass `event_id` from `check_ins_events` to drill into a specific event's sessions. Only the current period's sessions are returned when scoped this way — historical sessions from past occurrences of a recurring event aren't available on this route. Omit `event_id` for an organization-wide list. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `event_id` (`integer`, optional): Limit to sessions for a specific event. Returns the event's current period's sessions only. Pass an id returned by `check_ins_events`. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `starts_at`, `-starts_at`, `shows_at`, `-shows_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. Example input: `{}` ### `planningcentermcp_check_ins_events` CheckInsEvents · Read-only Search events configured in Check-Ins (e.g. Sunday Service, Wednesday VBS). Returns events that are set up for check-in — not Calendar events, Services plans, or Registrations signups. Events may be native to Check-Ins or auto-created from a Registrations signup. To find the Check-Ins event spawned by a specific signup, pass the signup's event id as `registration_event_id`. (Going the other direction — a Check-Ins event back to its source signup — is not exposed on this endpoint.) Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `campus_id` (`integer`, optional): Limit to events for a specific campus. - `filter` (`string`, optional): Limit to archived, not-archived, headcount-enabled, or Registrations-spawned events. One of: `archived`, `not_archived`, `for_headcounts`, `for_registrations`. - `ids` (`array`, optional): Specific event IDs to retrieve. - `include` (`array`, optional): Specify which relationships to include in the response. - `name` (`string`, optional): Match events whose name contains this substring. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `name`, `-name`, `created_at`, `-created_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `registration_event_id` (`integer`, optional): The Registrations event id of a signup. Use to find the Check-Ins event auto-created from that signup. Pass a value returned by `registrations_signups`. Example input: `{}` ### `planningcentermcp_check_ins_headcounts` CheckInsHeadcounts · Read-only Search manually-recorded headcount tallies for Check-Ins event times — counts that staff explicitly entered in the Headcounts app (e.g. "9am service / Adults = 187"). Each row pairs one event_time with one attendance_type and a total. An absent row may mean the count was zero. Use this only for explicit-tally counts. For attendance derived from individual people scanning in at a station, use `check_ins_check_ins` and aggregate. For who is *scheduled* on a service team for that service time, use `services_plans` instead. Pass `event_time_id` (an id from `check_ins_event_times`) to scope tallies to one session — the direct way to read or compare specific sessions (9am vs 11am). Headcount itself is only queryable by `created_at` / `updated_at`, so a time-window prompt ("last Sunday's 9am service") still means finding the session in `check_ins_event_times` first (by its `starts_at`) and passing its `event_time_id` here. Attendance-type names come from the included `attendance_type` resource (included by default); there is no separate MCP tool that lists attendance types, so this include is the only source of attendance-type names. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `created_at_end` (`string`, optional): Latest created at to include (inclusive), as YYYY-MM-DD. - `created_at_start` (`string`, optional): Earliest created at to include (inclusive), as YYYY-MM-DD. Pair with created_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `event_time_id` (`integer`, optional): Scope to a single event time (session), returning only that session's headcount tallies. Pass an id from `check_ins_event_times`. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `created_at`, `-created_at`, `total`, `-total`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `updated_at_end` (`string`, optional): Latest updated at to include (inclusive), as YYYY-MM-DD. - `updated_at_start` (`string`, optional): Earliest updated at to include (inclusive), as YYYY-MM-DD. Pair with updated_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. Example input: `{}` ### `planningcentermcp_check_ins_locations` CheckInsLocations · Read-only Search check-in locations configured for a single Check-Ins event — rooms, age groups, and other places people check in to. Each location has age, grade, and gender gating that determines who's allowed to check in there. Requires an `event_id`; look one up with `check_ins_events`. Some locations have `kind="Folder"`, meaning they don't accept check-ins themselves — they contain other locations. Use `include=locations` to descend into a folder's children and `include=parent` to walk back up. To drop folders and return only check-in-able locations, pass `filter="locations"`; to keep only top-level entries (no parent folder), pass `filter="root"`. Note: Check-Ins locations are distinct from Calendar resources (physically bookable spaces like the sanctuary) — if a prompt says "rooms," confirm which is meant. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `event_id` (`integer`, required): List locations configured for this single event (see check_ins_events). - `filter` (`string`, optional): `locations` drops folders (keeps only check-in-able locations); `root` keeps only top-level entries (no parent folder). One of: `root`, `locations`. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `kind`, `-kind`, `name`, `-name`, `position`, `-position`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. Example input: `{"event_id":1}` ### `planningcentermcp_giving_batch_groups` GivingBatchGroups · Read-only List giving batch groups — optional, customizable collections of giving batches that share common characteristics. Each group carries `total_cents`/`total_currency` totals and a `committed`/`status` state (`uncommitted`, `updating`, or `committed`), and committing a group commits all of its batches and donations. Limit to `committed` or `in_progress` (uncommitted) groups, find a group by a partial match on its `description`, narrow by `updated_at` range, include the `owner` (the Giving admin who created it), and sort by `updated_at`. Use `giving_batches` to drill into the individual batches within a group. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `description` (`string`, optional): Partial (substring) match on a batch group's description. - `filter` (`string`, optional): Limit to `committed` batch groups or `in_progress` (uncommitted) batch groups. One of: `committed`, `in_progress`. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `updated_at_end` (`string`, optional): Latest updated at to include (inclusive), as YYYY-MM-DD. - `updated_at_start` (`string`, optional): Earliest updated at to include (inclusive), as YYYY-MM-DD. Pair with updated_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. Example input: `{}` ### `planningcentermcp_giving_batches` GivingBatches · Read-only List giving batches — groupings of donations. A batch starts uncommitted (`status` `in_progress`), acting as a staging area where its donations aren't yet visible to donors, and becomes visible once committed (`status` `committed`, with a `committed_at` timestamp). Each batch carries `total_cents`/`total_currency` totals (and `donations_count` on request). Filter to `committed` or `in_progress` batches, narrow by `updated_at` or `committed_at` range, and include the `batch_group` it belongs to or its `owner` (the Giving admin who created it). Sort by `committed_at` to surface the most recently committed batches. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `committed_at_end` (`string`, optional): Latest committed at to include (inclusive), as YYYY-MM-DD. - `committed_at_start` (`string`, optional): Earliest committed at to include (inclusive), as YYYY-MM-DD. Pair with committed_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `filter` (`string`, optional): Limit to `committed` batches or `in_progress` (uncommitted) batches. One of: `committed`, `in_progress`. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `updated_at`, `-updated_at`, `committed_at`, `-committed_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `updated_at_end` (`string`, optional): Latest updated at to include (inclusive), as YYYY-MM-DD. - `updated_at_start` (`string`, optional): Earliest updated at to include (inclusive), as YYYY-MM-DD. Pair with updated_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. Example input: `{}` ### `planningcentermcp_giving_donations` GivingDonations · Read-only Search donations in Planning Center Giving - the individual gifts a church has received, with the amount, how it was paid, when it arrived, and whether it was refunded. All money is in cents (`amount_cents` 5000 is $50.00). `received_at` is the business date a gift counts toward and what the Giving admin UI filters on - prefer it over `created_at`, which is when the record was entered. Searches the whole organization by default. Pass at most one of `person_id` (one donor's giving history), `batch_id` (the gifts in one batch), or `campus_id` - none of these is filterable org-wide, so scoping to one changes which endpoint is used. A donation carries a single total with no fund attribution of its own: include `designations.fund` to see which funds a gift was split across, or filter by `fund_id` to answer "how much came into one fund". For totals, set `include_totals` - the response `meta` then carries `received_total_amount_cents` across everything matching the filters, ignoring pagination. Use it rather than paging through results to sum them by hand. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `batch_id` (`integer`, optional): List the donations in this batch (see giving_batches). Pass at most one of person_id, batch_id, or campus_id. - `campus_id` (`integer`, optional): List the donations credited to this campus (see people_church_campuses). Pass at most one of person_id, batch_id, or campus_id. - `created_at_end` (`string`, optional): Latest created at to include (inclusive), as YYYY-MM-DD. - `created_at_start` (`string`, optional): Earliest created at to include (inclusive), as YYYY-MM-DD. Pair with created_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `filter` (`string`, optional): Limit to `succeeded` donations - gifts that actually settled. Can't be combined with person_id, batch_id, or campus_id. One of: `succeeded`. - `fund_id` (`integer`, optional): Only donations designated to this fund (see giving_funds). Can't be combined with include_totals. - `include` (`array`, optional): Specify which relationships to include in the response. Include `designations.fund` to see which funds a gift was split across. `note` requires permission to manage donation notes in Giving, and is silently absent otherwise. - `include_totals` (`boolean`, optional): Add `received_total_amount_cents` to the response meta - the total received across every donation matching the filters, excluding refunded and failed gifts. Can't be combined with fund_id. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `received_at`, `-received_at`, `created_at`, `-created_at`, `updated_at`, `-updated_at`, `completed_at`, `-completed_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `payment_method` (`string`, optional): Only donations paid this way. One of: `ach`, `cash`, `check`, `card`. - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `person_id` (`integer`, optional): List the donations this person has given (see people_search). Pass at most one of person_id, batch_id, or campus_id. - `received_at_end` (`string`, optional): Latest received at to include (inclusive), as YYYY-MM-DD. - `received_at_start` (`string`, optional): Earliest received at to include (inclusive), as YYYY-MM-DD. Pair with received_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `updated_at_end` (`string`, optional): Latest updated at to include (inclusive), as YYYY-MM-DD. - `updated_at_start` (`string`, optional): Earliest updated at to include (inclusive), as YYYY-MM-DD. Pair with updated_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. Example input: `{}` ### `planningcentermcp_giving_donors` GivingDonors · Read-only Per-donor giving totals in Planning Center Giving. Each row is one person who gave inside a date range, with their total, how many donations it came from, and when they first ever gave. Set `received_at_start` and `received_at_end` to the window you mean. The applied window isn't echoed back, so name the range you used. There is no combined household row. Each person in a couple is their own row with their own total, so a couple's combined giving means fetching both and adding `total_received_donation_amount_cents` yourself. Read `total_received_donation_amount_cents` with `total_received_donation_amount_currency`; it is in that currency's minor units. `donation_count` includes refunded and failed donations while the total counts only what was received, so the two don't divide into an average gift. `first_donated` is the lifetime first gift, not the first inside the range, and can be null even for someone with donations — a missing value doesn't mean they never gave. Rows carry no `links.html`, so don't promise a donor a page or construct a URL for one. For what someone committed to give rather than what they gave, use giving_pledges. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `campus_id` (`integer`, optional): Count only donations made at this campus. Takes a Planning Center campus id (see people_church_campuses); an id that matches no campus returns an error rather than being ignored. - `filter` (`array`, optional): Restrict to donors who give as part of a joint giving unit — a couple giving together. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. Sorting by `name` orders by last name, not by the full name shown in the `name` field. One of: `name`, `-name`, `total_received_donation_amount_cents`, `-total_received_donation_amount_cents`, `donation_count`, `-donation_count`, `first_donated`, `-first_donated`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `person_id` (`integer`, optional): Return only this person's row. Use a person id from people_search — it is also the `id` on each row returned here. - `received_at_end` (`string`, optional): Latest received at to include (inclusive), as YYYY-MM-DD. If neither received_at_start nor received_at_end is given, the API falls back to the last 30 days. - `received_at_start` (`string`, optional): Earliest received at to include (inclusive), as YYYY-MM-DD. Pair with received_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. If neither received_at_start nor received_at_end is given, the API falls back to the last 30 days. Example input: `{}` ### `planningcentermcp_giving_funds` GivingFunds · Read-only List the giving funds configured for the organization. Funds track the intent of a donation (e.g. "General", "Building", "Missions") and let donors allocate gifts to a specific cause. Use `default: true` to find the organization's default fund. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `default` (`boolean`, optional): Filter by whether the fund is the organization's default. - `ids` (`array`, optional): Specific fund IDs to retrieve. - `name` (`string`, optional): Filter funds by name. Substring match, partial names work. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `visibility` (`string`, optional): Filter by how the fund is visible on Church Center. `everywhere`: anyone can donate; `admin_only`: hidden from donors, permitted Giving users only; `nowhere`: no new donations, retained in historical reports; `hidden`: hidden from the default donation form but reachable via direct link or Text-to-Give. One of: `everywhere`, `admin_only`, `nowhere`, `hidden`. Example input: `{}` ### `planningcentermcp_giving_payment_sources` GivingPaymentSources · Read-only List the payment sources configured for the organization. A payment source is the platform a donation originated from — donations made through Giving carry the built-in "Planning Center" source, while donations imported from an external platform (Stripe, Pushpay, Tithe.ly, etc.) carry a source identifying that platform. This is organization-level configuration only and returns no donor or donation data. `status` is either `active` or `archived`. Archived sources can't be assigned to new donations, but their historical donations are retained. One exception: the built-in "Planning Center" source returns `status` as the number `0` (meaning active) and returns no `created_at`/`updated_at` — treat it as always-active and always-present rather than filtering on those fields. `payment_source_type` is only returned by organizations that have that feature enabled, so it may be absent from results. In practice organizations have a handful of sources. The endpoint offers no filters or sorting, so narrow the results yourself after fetching. `giving_donations` can't filter by payment source, but each donation carries its `payment_source` relationship — to split totals by source, group the donations by that id and match it against the sources here. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. Example input: `{}` ### `planningcentermcp_giving_pledge_campaigns` GivingPledgeCampaigns · Read-only List pledge campaigns in Planning Center Giving — long-term commitment drives toward a goal (a building campaign, a missions push). Each campaign carries its `goal_cents` target and two running totals: `received_total_from_pledges_cents` (gifts that closed against a pledge) and `received_total_outside_of_pledges_cents` (gifts to the same fund with no pledge behind them). Reach for this for campaign-level progress questions like "how are we tracking against the building campaign goal?" Each campaign belongs to a fund. Filter by `fund_id` to find every campaign supporting a specific fund (look the fund up with giving_funds first), or include `fund` to see its name alongside each campaign. This tool returns campaign-level aggregates only — for the individual pledges behind a campaign, use giving_pledges. There is no "active" filter, so compose one from the date bounds — and set **both** together, not just one. A campaign is active when it has started and has not yet ended, so send `starts_at_end` = today (started on or before today) **and** `ends_at_start` = today (ends on or after today) in the same call. Sending only one bound returns campaigns that may already be over or not yet started, not active ones. To surface the campaigns wrapping up soonest, sort by `ends_at` ascending with no date bounds — that is a separate question from "active", so don't add the date filters unless the user asked only for active campaigns. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `ends_at_end` (`string`, optional): Latest ends at to include (inclusive), as YYYY-MM-DD. - `ends_at_start` (`string`, optional): Earliest ends at to include (inclusive), as YYYY-MM-DD. Pair with ends_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. - `fund_id` (`integer`, optional): Only return campaigns supporting this fund. Look the fund up with giving_funds first. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `starts_at`, `-starts_at`, `ends_at`, `-ends_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `starts_at_end` (`string`, optional): Latest starts at to include (inclusive), as YYYY-MM-DD. - `starts_at_start` (`string`, optional): Earliest starts at to include (inclusive), as YYYY-MM-DD. Pair with starts_at_end; set both to the same day to match a single date, or pass just one side for an open-ended range. Example input: `{}` ### `planningcentermcp_giving_pledges` GivingPledges · Read-only Look up pledges in Planning Center Giving - a person's commitment to give a set amount toward a pledge campaign, alongside how much they have actually donated against that commitment so far. Provide exactly one of `person_id` (the pledges one person has made) or `pledge_campaign_id` (everyone who pledged to one campaign). Each pledge carries `amount_cents` (the amount committed) and `donated_total_cents` (the amount delivered so far). To find donors who are behind on their commitments, compare those two fields on the returned records - there is no server-side filter for it, so the arithmetic has to be done here. When the pledger belongs to a joint giving unit - the "and Jane" half of "John and Jane pledged $5,000" - `joint_giver_amount_cents` and `joint_giver_donated_total_cents` carry that second person's amounts; both are 0 otherwise. Include `joint_giver` to see who they are. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `created_at`, `-created_at`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `person_id` (`integer`, optional): List the pledges this person has made (see people_search). Provide either this or pledge_campaign_id, not both. - `pledge_campaign_id` (`integer`, optional): List the pledges made toward this campaign (see giving_pledge_campaigns). Provide either this or person_id, not both. Example input: `{}` ### `planningcentermcp_giving_recurring_donations` GivingRecurringDonations · Read-only Look up recurring donations in Planning Center Giving - a donor's scheduled, repeating gift (weekly, monthly, etc.), including the amount, the schedule, when the last gift came in, and when the next one is due. Recurring donations are read-only. Reach for this for questions about scheduled future giving ("who gives monthly?", "whose recurring gift is paused?", "what is this person's recurring gift?"). For gifts that have actually been received, use giving_donations instead. `status` is `active`, `indefinite_hold` (paused with no end date), or `temporary_hold` (paused until `release_hold_at`). Include `designations` to see how a recurring gift is split across funds. Each designation carries its fund as a relationship id, so use giving_funds to get fund names. The donor is likewise returned as a person id - use people_search to resolve names. `amount_cents` on the gift is its total across every fund it is split between, so it does not answer how much goes to one fund. For that, include `designations` and read the amount on the designation whose `fund` is the one in question. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `fund_id` (`integer`, optional): Only return recurring donations that designate part of the gift to this fund (see giving_funds). Matching gifts may be split across other funds too, so to report the amount going to this fund, include `designations` and read the amount on the designation for it rather than the gift's `amount_cents`. - `include` (`array`, optional): Specify which relationships to include in the response. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `person_id` (`integer`, optional): List the recurring donations set up by this person (see people_search). Omit to list them across the whole organization. - `status` (`string`, optional): Filter by whether the recurring donation is running or paused. `active` is giving on schedule. `indefinite_hold` is paused with no end date. `temporary_hold` is paused until `release_hold_at`. One of: `active`, `indefinite_hold`, `temporary_hold`. Example input: `{}` ### `planningcentermcp_giving_refunds` GivingRefunds · Read-only Get the refund on a single donation in Planning Center Giving - the amount refunded, the payment processing fee returned, and when the refund was processed. A donation has at most one refund. Requires a donation ID, so reach for this when a specific donation is already in hand and the question needs the refund record's own fields (the refund fee, the exact time the refund was processed). For aggregate questions like "how much did we refund last month?", use giving_donations to find refunded donations instead. A not-found result means the donation has no refund, the donation ID is invalid, or you don't have permission to manage donations in Giving (administrator or bookkeeper). Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `donation_id` (`integer`, required): Get the refund on this donation (see giving_donations). - `include` (`array`, optional): Specify which relationships to include in the response. - `output_fields` (`array`, optional): Specify which fields to include in the response. Example input: `{"donation_id":1}` ### `planningcentermcp_groups_event_attendances` GroupsEventAttendances · Read-only Look up individual attendance records for a single event in Planning Center Groups - whether each person attended and their role (member, leader, visitor, or applicant) at the time of the event. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `event_id` (`integer`, required): The ID of the event to look up attendance records for. - `filter` (`string`, optional): Filter attendance records. Use 'attended' to return only people who attended. One of: `attended`. - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field to order results by. Prefix with '-' for descending order. One of: `role`, `-role`. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for pagination. Use the value returned in the previous response to get the next page. - `per_page` (`integer`, optional): Number of results to return per page (1-100, default 10). - `role` (`string`, optional): Filter attendance records by the role of the attendee. One of: `member`, `leader`, `visitor`, `applicant`. Example input: `{"event_id":1}` ### `planningcentermcp_groups_events` GroupsEvents · Read-only Search events in Planning Center Groups. An event is a single meeting of a group with a start and end time, an optional location, and a cancellation status. By default searches events across every group. Provide group_id or person_id to list events for a specific group or person. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `campus_ids` (`array`, optional): Filter events by one or more campus IDs. - `ends_at_end` (`string`, optional): Return events that end on or before this date (ISO 8601 date format). - `ends_at_start` (`string`, optional): Return events that end on or after this date (ISO 8601 date format). - `filter` (`string`, optional): Filter events by cancellation status. One of: `canceled`, `not_canceled`. - `group_id` (`integer`, optional): Filter events to a specific group by its ID. - `group_type_ids` (`array`, optional): Filter events by one or more group type IDs. - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Search events by name. - `order_by` (`string`, optional): Field to order results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): List of fields to include in the response (e.g. id, name, description, starts_at, ends_at, canceled). - `page_after` (`string`, optional): Cursor for pagination. Use the value returned in the previous response to get the next page. - `per_page` (`integer`, optional): Number of results to return per page. - `person_id` (`integer`, optional): Filter events to a specific person by their ID. - `starts_at_end` (`string`, optional): Return events that start on or before this date (ISO 8601 date format). - `starts_at_start` (`string`, optional): Return events that start on or after this date (ISO 8601 date format). Example input: `{}` ### `planningcentermcp_groups_group_types` GroupsGroupTypes · Read-only List or fetch group type categories (e.g. "Small Groups", "Classes") from Planning Center Groups. Group types define the default settings, visibility, and color theme for the groups within them. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `id` (`integer`, optional): Fetch a specific group type by its ID. - `order_by` (`string`, optional): Field to order results by. Prefix with '-' for descending order. One of: `name`, `-name`, `position`, `-position`. - `output_fields` (`array`, optional): List of fields to include in the response (e.g. id, name, color, church_center_map_visible). - `page_after` (`string`, optional): Cursor for pagination. Use the value returned in the previous response to get the next page. - `per_page` (`integer`, optional): Number of results to return per page. Example input: `{}` ### `planningcentermcp_groups_memberships` GroupsMemberships · Read-only Look up group memberships in Planning Center Groups - the association of a person to a group, with the member's role and the date they joined. Provide exactly one of group_id (to list a group's members) or person_id (to list the groups a person belongs to). Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `group_id` (`integer`, optional): List members of a specific group by its ID. Provide either group_id or person_id, not both. - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field to order results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): List of fields to include in the response (e.g. id, joined_at, role). - `page_after` (`string`, optional): Cursor for pagination. Use the value returned in the previous response to get the next page. - `per_page` (`integer`, optional): Number of results to return per page. - `person_id` (`integer`, optional): List groups that a specific person belongs to, by their ID. Provide either group_id or person_id, not both. - `role` (`string`, optional): Filter memberships by role. One of: `member`, `leader`. Example input: `{}` ### `planningcentermcp_groups_search` GroupsSearch · Read-only Search for groups. Groups are collections of people that meet together regularly (small groups, classes, Bible studies, etc.). Returns details like name, description, schedule, contact email, and membership count. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `archive_status` (`string`, optional): Control whether archived groups are included. Use 'not_archived' (default), 'only' for archived only, or 'include' to include both. One of: `not_archived`, `only`, `include`. - `campus_ids` (`array`, optional): Filter groups by one or more campus IDs. - `enrollment_status` (`array`, optional): Filter groups by enrollment status. - `filter` (`string`, optional): Additional filter options for groups. One of: `my_groups`. - `group_type_ids` (`array`, optional): Filter groups by one or more group type IDs. - `ids` (`array`, optional): Filter groups to specific IDs. - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Search groups by name. - `order_by` (`string`, optional): Field to order results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for pagination. Use the value returned in the previous response to get the next page. - `per_page` (`integer`, optional): Number of results to return per page. Example input: `{}` ### `planningcentermcp_people_background_checks` PeopleBackgroundChecks · Read-only Search for background checks. Optionally filter by a specific person using person_id. Current denotes the background check that best represents a person's current standing. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `expires_on_end` (`string`, optional): Filter background checks that expire on or before this date (ISO 8601 date format). - `expires_on_start` (`string`, optional): Filter background checks that expire on or after this date (ISO 8601 date format). - `filter` (`array`, optional): Filter background checks by status. - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field to order results by. Prefix with '-' for descending order. One of: `expires_on`, `-expires_on`, `status_updated_at`, `-status_updated_at`. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for pagination. Use the value returned in the previous response to get the next page. - `per_page` (`integer`, optional): Number of results to return per page. - `person_id` (`integer`, optional): Filter background checks by a specific person's ID. - `status_updated_at_end` (`string`, optional): Filter background checks whose status was updated on or before this date (ISO 8601 date format). - `status_updated_at_start` (`string`, optional): Filter background checks whose status was updated on or after this date (ISO 8601 date format). Example input: `{}` ### `planningcentermcp_people_church_campuses` PeopleChurchCampuses · Read-only List the church campuses (physical sites) configured for the organization. The returned campus IDs are what campus_id/campus_ids filters on other tools expect. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `created_at_end` (`string`, optional): Filter campuses created on or before this date (ISO 8601 date format). - `created_at_start` (`string`, optional): Filter campuses created on or after this date (ISO 8601 date format). - `ids` (`array`, optional): Filter to specific campus IDs. - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field to order results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): List of fields to include in the response (e.g. name, city, state, zip, time_zone). - `page_after` (`string`, optional): Cursor for pagination. Use the value returned in the previous response to get the next page. - `per_page` (`integer`, optional): Number of results to return per page. - `updated_at_end` (`string`, optional): Filter campuses updated on or before this date (ISO 8601 date format). - `updated_at_start` (`string`, optional): Filter campuses updated on or after this date (ISO 8601 date format). Example input: `{}` ### `planningcentermcp_people_current_organization` PeopleCurrentOrganization · Read-only Get information about the authenticated user's organization. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `output_fields` (`array`, optional): List of fields to include in the response (e.g. name, avatar_url, church_center_subdomain, country_code, time_zone, date_format, created_at). Example input: `{}` ### `planningcentermcp_people_field_data` PeopleFieldData · Read-only Search custom field data — the actual values of custom fields on people's profiles. Each field datum is tied to a field definition, which belongs to a custom tab. Use this to look up the values of custom fields for people. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `field_definition_id` (`integer`, optional): Filter field data to a specific field definition by its ID. - `file_content_type` (`string`, optional): Filter field data by file content type (for file-type fields). - `file_name` (`string`, optional): Filter field data by file name (for file-type fields). - `file_size` (`integer`, optional): Filter field data by file size in bytes (for file-type fields). - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field to order results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): List of fields to include in the response (e.g. id, file, file_content_type, file_name, file_size, value). - `page_after` (`string`, optional): Cursor for pagination. Use the value returned in the previous response to get the next page. - `per_page` (`integer`, optional): Number of results to return per page. - `person_id` (`integer`, optional): Filter field data to a specific person by their ID. - `value` (`string`, optional): Filter field data by value. Example input: `{}` ### `planningcentermcp_people_field_definitions` PeopleFieldDefinitions · Read-only Search the custom field definitions configured for the organization. A field definition represents a custom field — its name, data type, sequence, and which tab it belongs to. Use this to discover what custom fields exist on people profiles, then read a person's values with people_field_data. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `data_type` (`string`, optional): Filter field definitions by data type. One of: `string`, `text`, `date`, `boolean`, `file`, `select`, `checkboxes`, `number`, `header`. - `filter` (`string`, optional): Additional filter options. Use 'include_deleted' to include soft-deleted field definitions. One of: `include_deleted`. - `ids` (`array`, optional): Filter to specific field definition IDs. - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Search field definitions by name. - `order_by` (`string`, optional): Field to order results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): List of fields to include in the response (e.g. id, config, data_type, deleted_at, name, sequence, slug, tab_id). - `page_after` (`string`, optional): Cursor for pagination. Use the value returned in the previous response to get the next page. - `per_page` (`integer`, optional): Number of results to return per page. - `slug` (`string`, optional): Filter field definitions by slug. - `tab_id` (`integer`, optional): Filter field definitions to a specific custom tab by its ID. Example input: `{}` ### `planningcentermcp_people_form_fields` PeopleFormFields · Read-only Search the fields that make up a specific people form. Each form field describes a single input on the form, including its label, field type, whether it is required, and its display order. Requires a form_id. Use to understand a form's structure before reading submissions. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `form_id` (`string`, required): The ID of the form whose fields should be retrieved. - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field to sort results by. Prefix with '-' for descending order. One of: `created_at`, `-created_at`, `sequence`, `-sequence`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page (1–100). Defaults to 10. Example input: `{"form_id":""}` ### `planningcentermcp_people_form_submissions` PeopleFormSubmissions · Read-only Search for people form submissions. A form submission represents an individual person's response to a specific people form. Use people_form_fields to see the questions. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `form_id` (`string`, required): The ID of the form whose submissions should be retrieved. - `created_at_end` (`string`, optional): Return submissions created on or before this date (ISO 8601). - `created_at_start` (`string`, optional): Return submissions created on or after this date (ISO 8601). - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field to sort results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): Fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page (1–100). Defaults to 10. - `person_ids` (`array`, optional): Filter submissions to these person IDs. - `updated_at_end` (`string`, optional): Return submissions updated on or before this date (ISO 8601). - `updated_at_start` (`string`, optional): Return submissions updated on or after this date (ISO 8601). Example input: `{"form_id":""}` ### `planningcentermcp_people_forms` PeopleForms · Read-only Search for people forms. Forms is a tool for gathering information from people via customizable online forms. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `campus_id` (`string`, optional): Filter forms by campus ID. - `filter` (`string`, optional): Filter forms by status. One of: `open`, `closed`, `archived`. - `ids` (`array`, optional): Filter to specific form IDs. - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Filter forms by name (partial match). - `order_by` (`string`, optional): Field to sort results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): Fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page (1–100). Defaults to 10. Example input: `{}` ### `planningcentermcp_people_households` PeopleHouseholds · Read-only Search households — groups of people who live together (typically a family), each with a primary contact. Filter by household or primary-contact name. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `created_at_end` (`string`, optional): Return households created on or before this date (ISO 8601). - `created_at_start` (`string`, optional): Return households created on or after this date (ISO 8601). - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Filter households by name (partial match). - `order_by` (`string`, optional): Field to sort results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): Fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page (1–100). Defaults to 10. - `primary_contact_name` (`string`, optional): Filter households by the name of the primary contact. - `updated_at_end` (`string`, optional): Return households updated on or before this date (ISO 8601). - `updated_at_start` (`string`, optional): Return households updated on or after this date (ISO 8601). Example input: `{}` ### `planningcentermcp_people_list_results` PeopleListResults · Read-only Retrieves the people that appear in a specific Planning Center People list. Requires a list_id (find one via people_lists). Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `list_id` (`string`, required): The ID of the list whose members should be retrieved. - `order_by` (`string`, optional): Field to sort results by. Prefix with '-' for descending order. One of: `created_at`, `-created_at`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page (1–100). Defaults to 10. - `person_id` (`string`, optional): Filter results to a specific person ID. Example input: `{"list_id":""}` ### `planningcentermcp_people_lists` PeopleLists · Read-only Search for people lists. A list is a powerful tool for finding and grouping people together. To get the people in a list, use people_list_results. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `campus_id` (`string`, optional): Filter lists by campus ID. - `created_at_end` (`string`, optional): Return lists created on or before this date (ISO 8601). - `created_at_start` (`string`, optional): Return lists created on or after this date (ISO 8601). - `ids` (`array`, optional): Filter to specific list IDs. - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Filter lists by name (partial match). - `order_by` (`string`, optional): Field to sort results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): Fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page (1–100). Defaults to 10. - `updated_at_end` (`string`, optional): Return lists updated on or before this date (ISO 8601). - `updated_at_start` (`string`, optional): Return lists updated on or after this date (ISO 8601). Example input: `{}` ### `planningcentermcp_people_note_categories` PeopleNoteCategories · Read-only Search note categories in Planning Center People. Note categories organize and classify notes on people profiles. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Filter note categories by name (partial match). - `order_by` (`string`, optional): Field to sort results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): Fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page (1–100). Defaults to 10. Example input: `{}` ### `planningcentermcp_people_notes` PeopleNotes · Read-only Search for notes attached to people's profiles. A note is text with a category connected to a person's profile. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `include` (`array`, optional): Related resources to include in the response. - `note` (`string`, optional): Filter notes by content text (partial match). - `note_category_id` (`string`, optional): Filter notes by note category ID. - `order_by` (`string`, optional): Field to sort results by. Prefix with '-' for descending order. - `output_fields` (`array`, optional): Fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page (1–100). Defaults to 10. - `person_id` (`string`, optional): Filter notes to a specific person ID. Example input: `{}` ### `planningcentermcp_people_search` PeopleSearch · Read-only Search for people by name, contact info, status, campus, membership, and more. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `age_type` (`string`, optional): Filter by age type: child or adult. One of: `child`, `adult`. - `campus_ids` (`array`, optional): Filter by one or more campus IDs. - `created_at_end` (`string`, optional): Return people created on or before this date (ISO 8601). - `created_at_start` (`string`, optional): Return people created on or after this date (ISO 8601). - `email` (`string`, optional): Filter by email address. - `first_name` (`string`, optional): Filter by first name (partial match supported). - `gender` (`string`, optional): Filter by gender: Male, Female, or Unspecified. One of: `Male`, `Female`, `Unspecified`. - `grade` (`integer`, optional): Filter by school grade (-1 for pre-K, 0 for kindergarten, 1–12 for grades 1–12). - `ids` (`array`, optional): Filter by one or more person IDs. - `inactivated_at_end` (`string`, optional): Return people inactivated on or before this date (ISO 8601). - `inactivated_at_start` (`string`, optional): Return people inactivated on or after this date (ISO 8601). - `include` (`array`, optional): Related resources to include in the response. - `last_name` (`string`, optional): Filter by last name (partial match supported). - `membership_type` (`string`, optional): Filter by membership type name. - `order_by` (`string`, optional): Sort order for results. One of: `last_name`, `-last_name`, `created_at`, `-created_at`, `updated_at`, `-updated_at`, `inactivated_at`, `-inactivated_at`. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page (1–100, default 10). - `phone_number` (`string`, optional): Filter by phone number. - `status` (`string`, optional): Filter by person status: active or inactive. One of: `active`, `inactive`. - `updated_at_end` (`string`, optional): Return people updated on or before this date (ISO 8601). - `updated_at_start` (`string`, optional): Return people updated on or after this date (ISO 8601). Example input: `{}` ### `planningcentermcp_people_tabs` PeopleTabs · Read-only Search people custom tabs. A tab groups field definitions on the profile (e.g., 'Volunteer Info', 'Church Info'). Tabs contain field definitions which describe the custom fields whose per-person values come from people_field_data. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `ids` (`array`, optional): Filter by one or more tab IDs. - `name` (`string`, optional): Filter by tab name. - `order_by` (`string`, optional): Sort order for results. One of: `name`, `-name`, `sequence`, `-sequence`, `slug`, `-slug`. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page. - `slug` (`string`, optional): Filter by tab slug (URL-safe identifier). Example input: `{}` ### `planningcentermcp_people_workflow_cards` PeopleWorkflowCards · Read-only Search people workflow cards. Cards are workflow steps assigned to a staff member to perform for a specific person. Requires a workflow_id (find one via people_workflows). Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `workflow_id` (`string`, required): The ID of the workflow to search cards within. Required. Use people_workflows to find a workflow ID. - `after_moved_to_step_at` (`string`, optional): Return cards moved to their current step on or after this date (ISO 8601). - `assignee_ids` (`array`, optional): Filter by one or more assignee person IDs. - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Sort order for results. One of: `moved_to_step_at`, `-moved_to_step_at`. - `output_fields` (`array`, optional): List of fields to include in the response. - `overdue` (`boolean`, optional): Filter for overdue cards. Only supports true. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page. - `stage` (`string`, optional): Filter cards by stage: ready, snoozed, completed, or removed. One of: `ready`, `snoozed`, `completed`, `removed`. - `step_ids` (`array`, optional): Filter by one or more workflow step IDs. Example input: `{"workflow_id":""}` ### `planningcentermcp_people_workflow_categories` PeopleWorkflowCategories · Read-only Search the categories that organize people workflows. Use this to find a category by name; then filter people_workflows by its workflow_category_id. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `ids` (`array`, optional): Filter by one or more workflow category IDs. - `name` (`string`, optional): Filter by category name. - `order_by` (`string`, optional): Sort order for results. One of: `name`, `-name`, `created_at`, `-created_at`, `updated_at`, `-updated_at`. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page. Example input: `{}` ### `planningcentermcp_people_workflows` PeopleWorkflows · Read-only Search for people workflows. A workflow consists of a series of steps to complete a specific task. Steps consist of cards assigned to a staff member for a specific person. Use people_workflow_cards for per-person cards, and people_workflow_categories for categories. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `campus_id` (`string`, optional): Filter by campus ID. - `created_at_end` (`string`, optional): Return workflows created on or before this date (ISO 8601). - `created_at_start` (`string`, optional): Return workflows created on or after this date (ISO 8601). - `filter` (`array`, optional): Predefined filters to narrow results. - `ids` (`array`, optional): Filter by one or more workflow IDs. - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Filter by workflow name. - `order_by` (`string`, optional): Sort order for results. One of: `name`, `-name`, `created_at`, `-created_at`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page. - `updated_at_end` (`string`, optional): Return workflows updated on or before this date (ISO 8601). - `updated_at_start` (`string`, optional): Return workflows updated on or after this date (ISO 8601). - `workflow_category_id` (`string`, optional): Filter by workflow category ID. Example input: `{}` ### `planningcentermcp_publishing_channels` PublishingChannels · Read-only Search sermon channels in Planning Center Publishing. A "channel" is a top-level content grouping for sermons (e.g. "Sunday Morning", "Wednesday Bible Study"). Each channel carries its own feature flags (enable_audio, enable_on_demand_video, enable_watch_live, general_chat_enabled/group_chat_enabled, sermon_notes_enabled, podcast configuration) and a lifecycle pair (published, archived). This is the foundational Publishing tool. `publishing_episode_statistics` requires a channel id from here. `publishing_episodes` and `publishing_series` can't filter by channel — request their `channel` include and group by it client-side. For lifecycle questions ("is this channel published or archived?", "show me archived channels") use the `filter` param (archived, not_archived, published, podcast_enabled) rather than fetching every channel and inspecting the published/archived attributes yourself — the filter dispatches server-side. Pass multiple values to combine scopes, e.g. `["published", "podcast_enabled"]` for published channels with podcasting enabled. A channel's `services_service_type_remote_identifier` links it to a Planning Center Services service type. To answer "which channel is paired with our Sunday 9am service type?", call `services_service_types` first to find that service type's id, then match it against a channel's `services_service_type_remote_identifier` here. `general_chat_enabled`/`group_chat_enabled` read `false` both when chat is off and when the org lacks a Groups subscription; check `can_enable_chat` to tell those two cases apart. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `filter` (`array`, optional): Limit channels to one or more lifecycle or feature scopes: "archived", "not_archived", "published", "podcast_enabled". Pass multiple values to combine them. Omit to include all. - `name` (`string`, optional): Filter channels by name (partial match). - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `name`, `-name`, `position`, `-position`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. Example input: `{}` ### `planningcentermcp_publishing_episode_statistics` PublishingEpisodeStatistics · Read-only Church Center viewership statistics for the episodes in a single Publishing channel. Returns one entry per episode with its Church Center live watch count (live_watch_count), library watch count (library_watch_count), and a per-EpisodeTime breakdown (times, each carrying its own watch_count). Counts are Church Center plays only. Views on YouTube, Vimeo, Facebook, or other external platforms are NOT included — this mirrors the per-episode statistics panel the Publishing admin sees. This tool takes a channel_id. First call `publishing_channels` to pick the relevant channel (typically the main Sunday channel), then call this tool with that channel's id. Answer questions like "most-watched episodes this month" or "average listen count per episode" by fetching a channel's statistics and aggregating client-side — do NOT fan out per episode. Aggregates cover only the episodes you have fetched, so set `per_page` to 100 and keep paging with `page_after` until `has_more` is false before summarizing. Use `type` and the after/before date range to narrow server-side: `type: "live"` bounds by when episodes were published live, `type: "library"` bounds by when they were added to the library, and omitting `type` returns episodes matching either. `after` is an inclusive lower bound (includes the whole named day). `before` is an exclusive upper bound: it cuts off at the start of the named day, so episodes published on the `before` date itself are NOT included. Both are YYYY-MM-DD. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `channel_id` (`string`, required): ID of the channel whose episode statistics to return. Get channel ids from `publishing_channels`. - `after` (`string`, optional): Earliest publish date to include, as YYYY-MM-DD. Inclusive — the whole named day is included. Applies to the column selected by `type`. - `before` (`string`, optional): Upper bound on publish date, as YYYY-MM-DD. Exclusive — episodes published on this date are NOT included (the bound is the start of the named day). Applies to the column selected by `type`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `type` (`string`, optional): Restrict to episodes published live ("live", bounds by published_live_at) or added to the library ("library", bounds by published_to_library_at). Omit to include episodes matching either. One of: `live`, `library`. Example input: `{"channel_id":""}` ### `planningcentermcp_publishing_episodes` PublishingEpisodes · Read-only Search episodes in Planning Center Publishing. An episode is a single sermon — it carries title, description, art, audio/video URLs (both live-stream and on-demand library), and publication timestamps (`published_live_at`, `published_to_library_at`). Use `search` to find sermons by topic, book, or passage (e.g. "sermons on Romans") — it matches against the episode's title only (not description, and not speaker or preacher name). Use `church_center_url` for a link to the episode on Church Center. `page_actions` is intentionally not exposed — two of its three actions are admin-write actions (remove from series, edit); `church_center_url` covers the one navigation action. Cross-product chaining: an episode carries `services_plan_remote_identifier` (the Services Plan that was live for this sermon) and `services_service_type_remote_identifier` (the Services Service Type its channel is paired with) — resolve a plan or service type id from `services_plans` / `services_service_types` first, then pass it here (e.g. "last Sunday's sermon" resolves by first finding the Sunday-service plan, then matching its id here). Filter by `series_id` to get all episodes in a sermon series — resolve the series by name with `publishing_series` first, then pass its id here. Filter by speaker with `speaker_id` and `speaker_type` together — both are required (a speaker id alone is ambiguous because a Person and a Guest can share the same id). Resolve them from `publishing_speakers` first, which returns each speaker's `id` and `speaker_type`, then pass both here. For a prompt naming both a speaker and a topic (e.g. "Find Pastor John's sermons on Romans"), resolve the speaker via `publishing_speakers`, then call this tool with the speaker pair plus `search` on the topic (`{"speaker_id": "...", "speaker_type": "Person", "search": "Romans"}`). To surface the most recent sermons, pair `order_by: -published_live_at` with `filter: published_live`. Without the filter, episodes that never went live or are only scheduled can sort above the genuinely most-recent sermons. Only add the filter when the user wants sermons that have already aired; omit it to sort across all episodes. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `filter` (`string`, optional): Limit episodes to a lifecycle or connection scope: "published_live", "connected_to_services", or "published_on_church_center". These are lifecycle states, not date ranges — "published_live" means the episode has gone live at some point, not that it went live within any specific period. Omit to include all. One of: `published_live`, `connected_to_services`, `published_on_church_center`. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `title`, `-title`, `stream_type`, `-stream_type`, `published_live_at`, `-published_live_at`, `published_to_library_at`, `-published_to_library_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `search` (`string`, optional): Filter episodes by title (partial match). Does not match against the episode description. - `series_id` (`string`, optional): Filter to episodes in a specific series. Chain from `publishing_series` — resolve the series id there, then pass it here. - `services_plan_remote_identifier` (`string`, optional): Filter to the episode linked to a specific Services plan. Chain from `services_plans` — resolve the plan id there, then pass it here. - `services_service_type_remote_identifier` (`string`, optional): Filter to episodes whose channel is paired with a specific Services service type. Chain from `services_service_types`. - `speaker_id` (`string`, optional): Filter to episodes by a specific speaker. Must be sent together with `speaker_type` (a speaker id alone is ambiguous). Chain from `publishing_speakers` — resolve the speaker's `id` there, then pass it here along with its `speaker_type`. - `speaker_type` (`string`, optional): The speaker's type, from `publishing_speakers`. Required whenever `speaker_id` is set; sending one without the other returns an error. One of: `Person`, `Guest`. Example input: `{}` ### `planningcentermcp_publishing_series` PublishingSeries · Read-only Search sermon series in Planning Center Publishing. A "series" is a collection of episodes organized around a theme (e.g. "Romans", "Easter", "Advent"), scoped to a single channel. Each series carries a title, description, art, the run window (started_at / ended_at), an episodes_count, and a published lifecycle flag. Use this tool for questions about series metadata: "what's the current sermon series?", "how many episodes are in the Romans series?", "show me all the series we've done this year". Filter by title with the `title` param (partial match on the series title). For lifecycle questions use the `filter` param ("published", "not_published", "published_on_church_center") rather than fetching every series and inspecting the published attribute yourself — the filter dispatches server-side. Pass multiple values to combine scopes. To find the *current* series, request filter=["published"] with order_by="-started_at", then pick the most recent series whose window covers today (started_at on or before today, and ended_at empty or on/after today) — there is no server-side "current" filter. To list the episodes within a series, resolve the series id here first, then pass it to `publishing_episodes` as `series_id`. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `filter` (`array`, optional): Limit series to one or more scopes: "published", "not_published", "published_on_church_center". Pass multiple values to combine them. Omit to include all. - `include` (`array`, optional): Specify which relationships to include in the response. - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `title`, `-title`, `episodes_count`, `-episodes_count`, `started_at`, `-started_at`, `ended_at`, `-ended_at`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `title` (`string`, optional): Filter series by title (partial match). Example input: `{}` ### `planningcentermcp_publishing_speakers` PublishingSpeakers · Read-only Search speakers in Planning Center Publishing. A "speaker" is a unified abstraction over two underlying record types, distinguished by `speaker_type`: `"Person"` (a PCO People record) or `"Guest"` (an ad-hoc record for external speakers with no People record). Use the `search` param to filter by name (matches first_name or last_name, partial match) — this resolves name-based prompts directly, e.g. "has Pastor John preached recently?" → `search: "John"`. For sermon-content questions about a specific speaker, resolve the speaker's `id` and `speaker_type` here first, then chain both into `publishing_episodes`'s `speaker_id` and `speaker_type` filters (both are required together) to find their sermons. For `"Person"` speakers, `id` is the same People account-center id `people_search` returns, so you can alternatively resolve via `people_search` first and match the account-center id against a speaker here. `"Guest"` speakers only exist in Publishing — they have no People record, so `people_search` will never find them, and the response has no `links.html` for them (Person speakers do have one, pointing at the People record). Requires Publishing administrator access; other org members will get a permission error. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `order_by` (`string`, optional): Sort results by field. Use '-' prefix for descending order. One of: `first_name`, `-first_name`. - `output_fields` (`array`, optional): Specify which fields to include in the response. - `page_after` (`string`, optional): Pagination token from previous response's next_page_token field - `per_page` (`integer`, optional): Maximum number of results to return. Default: `10`. - `search` (`string`, optional): Filter speakers by name (matches first_name or last_name, partial match). Example input: `{}` ### `planningcentermcp_registrations_attendees` RegistrationsAttendees · Read-only Search the attendees registered for a specific Planning Center signup. An attendee is a person registered for a signup, with status flags for whether they are active, canceled, complete, or waitlisted. Requires a signup_id. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `signup_id` (`string`, required): The ID of the signup to search attendees for. Required. - `filter` (`string`, optional): Filter attendees by status: active, waitlist, or canceled. One of: `active`, `waitlist`, `canceled`. - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Sort order for results. One of: `created_at`, `-created_at`. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page. - `registration_id` (`string`, optional): Filter attendees by a specific registration ID. Example input: `{"signup_id":""}` ### `planningcentermcp_registrations_registrations` RegistrationsRegistrations · Read-only Search registrations for a specific signup. A registration is a single submission to a signup. Requires a signup_id. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `signup_id` (`string`, required): The ID of the signup to search registrations for. Required. - `include` (`array`, optional): Related resources to include in the response. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page. Example input: `{"signup_id":""}` ### `planningcentermcp_registrations_signups` RegistrationsSignups · Read-only Search signups. A signup is an ongoing program, opportunity, or event that people can register for. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `campus_id` (`string`, optional): Filter by campus ID. - `filter` (`string`, optional): Filter signups by archived status: archived or unarchived. One of: `archived`, `unarchived`. - `ids` (`array`, optional): Filter by one or more signup IDs. - `include` (`array`, optional): Related resources to include in the response. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page. Example input: `{}` ### `planningcentermcp_services_blockouts` ServicesBlockouts · Read-only Search the blockout dates for a specific person. A blockout is a date or recurring date range when a person is unavailable to be scheduled to serve (e.g. vacation). Requires a person_id. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `person_id` (`string`, required): The ID of the person whose blockouts to retrieve. Required. - `filter` (`array`, optional): Predefined filters to narrow results. - `group_identifier` (`string`, optional): Filter by group identifier (groups recurring blockouts together). - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page. Example input: `{"person_id":""}` ### `planningcentermcp_services_plan_items` ServicesPlanItems · Read-only Search the items (the order of service) within a specific plan in Planning Center Services. Each item is one element in a plan's sequence — a song, header, media, or announcement. Requires a service_type_id and plan_id; items are returned in plan sequence order. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `plan_id` (`string`, required): The ID of the plan whose items to retrieve. Required. - `service_type_id` (`string`, required): The ID of the service type containing the plan. Required. - `include` (`array`, optional): Related resources to include in the response. - `output_fields` (`array`, optional): List of fields to include in the response. - `page_after` (`string`, optional): Cursor for fetching the next page of results. - `per_page` (`integer`, optional): Number of results per page. Example input: `{"plan_id":"","service_type_id":""}` ### `planningcentermcp_services_plan_people` ServicesPlanPeople · Read-only List the people scheduled to serve on a specific plan in Planning Center Services — the plan's roster. Each entry includes the person's name, the team and position they're filling, and their confirmation status. Requires a service_type_id and plan_id. Use filter or read each person's status to narrow by confirmation state. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `plan_id` (`integer`, required): The ID of the plan whose roster you want to list. - `service_type_id` (`integer`, required): The ID of the service type that contains the plan. - `filter` (`array`, optional): Filter scheduled people by confirmation state. - `include` (`array`, optional): Related resources to include in the response. - `output_fields` (`array`, optional): Limit which fields are returned in the response. - `page_after` (`string`, optional): Pagination cursor from the previous response to fetch the next page. - `per_page` (`integer`, optional): Number of results to return per page (1–100). Default: `10`. - `team_id` (`integer`, optional): Filter results to a specific team within the plan. Example input: `{"plan_id":1,"service_type_id":1}` ### `planningcentermcp_services_plans` ServicesPlans · Read-only Search plans within a Planning Center Services service type. A plan is a single worship service or event (e.g. "Sunday Morning, June 8") containing its dates, series, item and people counts, and length. Requires a service_type_id. Note: sort_date is the plan's service date; plans are commonly scheduled into the future. To find the most recent service, combine filter "past" with order_by -sort_date. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `service_type_id` (`integer`, required): The ID of the service type to search plans within. - `created_at_end` (`string`, optional): Return plans created on or before this date (ISO 8601). - `created_at_start` (`string`, optional): Return plans created on or after this date (ISO 8601). - `filter` (`string`, optional): Filter plans by time period. One of: `past`, `future`, `no_dates`. - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field and direction to sort results by. One of: `created_at`, `-created_at`, `sort_date`, `-sort_date`, `title`, `-title`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Limit which fields are returned in the response. - `page_after` (`string`, optional): Pagination cursor from the previous response to fetch the next page. - `per_page` (`integer`, optional): Number of results to return per page. Default: `10`. - `series_title` (`string`, optional): Filter plans by series title (partial match). - `title` (`string`, optional): Filter plans by title (partial match). - `updated_at_end` (`string`, optional): Return plans updated on or before this date (ISO 8601). - `updated_at_start` (`string`, optional): Return plans updated on or after this date (ISO 8601). Example input: `{"service_type_id":1}` ### `planningcentermcp_services_schedules` ServicesSchedules · Read-only Retrieve a person's schedule in Planning Center Services — the worship service plans they are scheduled to serve in. Defaults to the authenticated user's own schedule when person_id is omitted. Provide a person_id to look up someone else's schedule. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field and direction to sort results by. One of: `starts_at`, `-starts_at`. - `output_fields` (`array`, optional): Limit which fields are returned in the response. - `page_after` (`string`, optional): Pagination cursor from the previous response to fetch the next page. - `per_page` (`integer`, optional): Number of results to return per page. Default: `10`. - `person_id` (`integer`, optional): Planning Center person ID. Omit to return the authenticated user's own schedule. - `plan_id` (`integer`, optional): Filter schedule results to a specific plan. Example input: `{}` ### `planningcentermcp_services_service_types` ServicesServiceTypes · Read-only Search for service types. A Service Type is a container for plans, typically a recurring worship event like Sunday AM, Wednesday Service, or Christmas Eve. Service Types group all the plans, teams, schedules, and song lists for that service. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `ids` (`array`, optional): Filter to only return service types with these IDs. - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Filter service types by name (partial match). - `order_by` (`string`, optional): Field and direction to sort results by. One of: `name`, `-name`, `sequence`, `-sequence`. - `output_fields` (`array`, optional): Limit which fields are returned in the response. - `page_after` (`string`, optional): Pagination cursor from the previous response to fetch the next page. - `parent_id` (`integer`, optional): Filter service types by parent folder ID. - `per_page` (`integer`, optional): Number of results to return per page. Default: `10`. Example input: `{}` ### `planningcentermcp_services_songs` ServicesSongs · Read-only Search the Planning Center Services song library. A song is a reusable piece of music (title, author, CCLI number, copyright, and themes) that can be scheduled into service plans. Use to find songs by title, author, theme, or CCLI number. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `author` (`string`, optional): Filter songs by author name (partial match). - `ccli_number` (`integer`, optional): Filter songs by their CCLI license number. - `hidden` (`boolean`, optional): Filter songs by whether they are hidden in the library. - `order_by` (`string`, optional): Field and direction to sort results by. One of: `created_at`, `-created_at`, `last_scheduled_at`, `-last_scheduled_at`, `title`, `-title`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Limit which fields are returned in the response. - `page_after` (`string`, optional): Pagination cursor from the previous response to fetch the next page. - `per_page` (`integer`, optional): Number of results to return per page. Default: `10`. - `themes` (`string`, optional): Filter songs by theme keywords. - `title` (`string`, optional): Filter songs by title (partial match). Example input: `{}` ### `planningcentermcp_services_team_positions` ServicesTeamPositions · Read-only Search the team positions within a service type in Planning Center Services. A team position is a role within a team that people are scheduled into — for example "Acoustic Guitar", "Vocals", or "Camera 1". Requires a service_type_id. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `service_type_id` (`integer`, required): The ID of the service type whose team positions you want to list. - `include` (`array`, optional): Related resources to include in the response. - `order_by` (`string`, optional): Field and direction to sort results by. One of: `name`, `-name`. - `output_fields` (`array`, optional): Limit which fields are returned in the response. - `page_after` (`string`, optional): Pagination cursor from the previous response to fetch the next page. - `per_page` (`integer`, optional): Number of results to return per page. Default: `10`. Example input: `{"service_type_id":1}` ### `planningcentermcp_services_teams` ServicesTeams · Read-only Search teams in Planning Center Services. A team is a group within a service type that people are scheduled into to serve (e.g. Band, Vocals, Production, Hospitality). Pass a service_type_id to limit results to a single service type, or omit to search across the whole organization. Read only: yes. Destructive: no. Idempotent (safe to retry): yes. Inputs: - `include` (`array`, optional): Related resources to include in the response. - `name` (`string`, optional): Filter teams by name (partial match). - `order_by` (`string`, optional): Field and direction to sort results by. One of: `created_at`, `-created_at`, `name`, `-name`, `updated_at`, `-updated_at`. - `output_fields` (`array`, optional): Limit which fields are returned in the response. - `page_after` (`string`, optional): Pagination cursor from the previous response to fetch the next page. - `per_page` (`integer`, optional): Number of results to return per page. Default: `10`. - `service_type_id` (`integer`, optional): Filter teams to a specific service type. Omit to search across the whole organization. Example input: `{}` ### `planningcentermcp_people_form_submissions_create` PeopleFormSubmissionsCreate · Write Record a submission to a people form, for submissions captured outside of Church Center (e.g. a paper form). The caller must be able to manage the target form. Identify the submitter with either person_id (existing person) or person_attributes. Submitting triggers notification/confirmation emails, workflow cards, and profile updates. Read only: no. Destructive: no. Idempotent (safe to retry): no. Inputs: - `form_id` (`string`, required): The ID of the form to submit. - `person_attributes` (`object`, optional): Submitter details when person_id is unknown. Required fields: first_name, last_name, email. - `person_id` (`string`, optional): ID of an existing person to associate with the submission. Use this or person_attributes, not both. - `values` (`array`, optional): Array of form field responses. Each entry maps a form_field_id to its submitted value. Example input: `{"form_id":""}` ### `planningcentermcp_people_notes_create` PeopleNotesCreate · Write Create a note on a person's profile. A note is text filed under a note category and attached to a specific person. Use people_notes to read existing notes and people_note_categories to discover which category to file the note under. Read only: no. Destructive: no. Idempotent (safe to retry): no. Inputs: - `note` (`string`, required): The text content of the note. - `note_category_id` (`string`, required): The ID of the note category to file this note under. Use people_note_categories to find valid IDs. - `person_id` (`string`, required): The ID of the person to attach the note to. - `display_date` (`string`, optional): Optional date the note should be displayed under (ISO 8601 date format). Example input: `{"note":"","note_category_id":"","person_id":""}` ## Related Other Productivity connectors ([all 103](/agentkit/connectors/?category=productivity)): - [Slack](/agentkit/connectors/slack/): Scalekit connector, OAuth, 96 tools - [Microsoft 365](/agentkit/connectors/microsoft365/): Scalekit connector, OAuth, 317 tools - [Notion](/agentkit/connectors/notion/): Scalekit connector, OAuth, 51 tools --- ## More Scalekit documentation | Resource | What it contains | When to use it | |----------|-----------------|----------------| | [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content | | [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas | | [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |