Skip to main content
Glama

Related Servers

Alternatives to pco-services-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access Planning Center Online data including worship plans, song library, teams, and volunteer information through natural language queries and direct tools.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Integrates 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.
      11
      MIT

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues