Skip to main content
Glama
stevehaskew

ChurchSuite Bookings MCP

by stevehaskew

Related Servers

Alternatives to ChurchSuite Bookings MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides read-only access to TrustLayer's public API, enabling users to query and retrieve data about parties, documents, projects, and other TrustLayer entities through MCP-compatible tools.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server exposing a PostgreSQL booking datastore to MCP clients, enabling read/write operations on staff, schedules, clients, and bookings with optional human-approval workflow integration.
      5
      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
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for auditing Trafft booking data with tools to list services, employees, appointments, and customers without mutation endpoints.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to SIA data, including inmates, visits, services, and daily schedules via FastMCP. Enables querying prison system information without write operations.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Semble practice-management API, enabling AI agents to search for patients, contacts, and users, as well as retrieve patient relationships via read-only tools.
      MIT

    TDQS

    B3.4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct entity or action: specific 'find' tools for next booking by name vs resource, separate 'get' and 'list' for each data type (bookings, contacts, ministries, etc.). No overlapping purposes.

    Naming Consistency5/5

    All tool names use consistent snake_case with a verb_noun pattern ('list_', 'get_', 'find_'). No mixing of conventions, making the set predictable.

    Tool Count4/5

    With 16 tools, the set covers bookings, contacts, resources, and rotas comprehensively. Slightly above the ideal range but still well-scoped; each tool has a clear role.

    Completeness2/5

    The tool set is entirely read-only, lacking any create, update, or delete operations. For a 'Bookings' server, missing mutation tools is a significant gap that will hinder common tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues