Planning Center Online MCP Server
Related Servers
Alternatives to Planning Center Online MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access Planning Center Online data including worship plans, song library, teams, and volunteer information through natural language queries and direct tools.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
- AlicenseNot gradedqualityDmaintenanceProvides read-only access to the Planning Center People API, enabling natural language queries for people, households, background checks, and lists.MIT
- FlicenseNot gradedqualityCmaintenanceConnects AI assistants to the Ploomes CRM, exposing 153 tools for CRUD operations on entities, pipeline and field configuration, CPQ proposal models, automations, and webhooks.-
- AlicenseAqualityDmaintenanceConnects AI agents to the Ploomes CRM REST API, exposing 56 tools for managing contacts, deals, tasks, pipelines, interactions, quotes, orders, products, fields, users, and account information.5614 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables control and automation of Holyrics presentation software through natural language commands for managing lyrics, media, schedules, and events. It provides specialized tools to search content and orchestrate church presentation workflows via the Holyrics API.-
TDQS
Scored across 29 tools
Each tool has a clearly distinct purpose targeting specific resources and actions within the Planning Center ecosystem. For example, pco_get_person retrieves a single person, pco_list_people searches and lists people, and pco_create_person creates a new person, with no overlap in functionality. The tools are well-organized by domain (People, Groups, Giving, Services, Calendar, Check-Ins), making it easy for an agent to distinguish between them.
All tool names follow a consistent 'pco_verb_noun' pattern with snake_case throughout. Verbs like 'create', 'get', 'list', and 'update' are used predictably across resources (e.g., pco_create_person, pco_get_person, pco_list_people, pco_update_person). This uniformity enhances readability and reduces cognitive load for agents when selecting tools.
With 29 tools, the count is borderline high for a single server, though it covers multiple Planning Center modules (People, Groups, Giving, Services, Calendar, Check-Ins). While each tool serves a specific purpose, the sheer number might overwhelm agents or lead to inefficiencies in tool selection. A more modular approach with fewer tools per domain could improve manageability.
The tool set provides comprehensive coverage for read and list operations across all major Planning Center domains, with create and update for people. However, there are notable gaps in CRUD operations for other resources like groups, donations, and events (e.g., no pco_create_group or pco_update_donation). These omissions could limit agents' ability to perform full lifecycle management, though core workflows are well-supported.