pco-services-mcp
Related Servers
Alternatives to pco-services-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to interact with Planning Center Online accounts across modules like People, Services, Giving, and Calendar. It provides tools for searching people, managing service plans, tracking donations, and monitoring events through the PCO API.29-
- AlicenseNot gradedqualityDmaintenanceProvides read-only access to the Planning Center People API, enabling natural language queries for people, households, background checks, and lists.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access Planning Center Online data including worship plans, song library, teams, and volunteer information through natural language queries and direct tools.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables authenticated subscribers to inspect weekly menus, recipe ingredients, deliveries, order history, and plan quota, and to preview or replace and save weekly main-meal selections with read-back verification. It also preserves add-ons and surfaces deadlines, permissions, and revision conflicts.MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates the Planning Center Online API with an MCP server to enable natural language interaction with church management data. It allows users to query service information, manage workflows, and retrieve data through conversational prompts.11MIT
- AlicenseAqualityDmaintenanceProvides read-only access to Nolio training data including planned workouts, completed sessions, metrics, records, and notes.84MIT
TDQS
Scored across 11 tools
Most tools target clearly distinct resources: attachments (list/download), blockouts (list/add/remove/skip), schedule views, and service order. The one soft overlap is team_contacts vs contact_info, which both return emails/phones, but the descriptions separate them by lookup path (per-plan vs name-search across upcoming plans). An agent can tell them apart, though it may hesitate.
About half the tools use a clean verb_noun pattern (list_attachments, add_blockout, remove_blockout, skip_blockout_date), but the rest are bare noun phrases (my_schedule, plan_team, team_contacts, contact_info, service_order). Mixed conventions, yet still readable and non-conflicting.
11 tools is squarely in the well-scoped range, and each one maps to a concrete task (check schedule, manage blockouts, fetch attachments, view team/contact info). Nothing feels redundant or vestigial.
The blockout lifecycle is well covered (list, add, remove, skip a single date) and the schedule/plan/attachment surfaces are present. Minor gaps: no edit/update for an existing blockout and no standalone way to enumerate plans or service types (they are surfaced indirectly via my_schedule IDs).