churchtools-mcp
Related Servers
Alternatives to churchtools-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables any MCP client to run natural-language queries and actions against CRM and ticket systems, with schema-validated tools, audit logging, and server-side write gating.7MIT
- 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 gradedqualityCmaintenanceGives MCP clients such as Claude, ChatGPT and Cursor access to a recruitment firm's database — candidates, contacts, companies, jobs, pipelines, notes and outreach — so assistants can search, match, draft and update records. Every request runs under the signed-in user's own account, workspace and role permissions, with sensitive actions confirmed as a preview first.MIT
- AlicenseAqualityBmaintenanceProvides Claude and any MCP client with live access to property management data, enabling operations on properties, units, leases, tenants, work orders, vendors, accounting, and file attachments through natural language.25MIT

magicsword-mcpofficial
AlicenseAqualityAmaintenanceEnables Claude Desktop, Cursor, and other MCP-aware clients to conversationally manage endpoints, query and triage alerts, inspect events, manage policies and intel feeds, mint enrollment tokens, and preview or commit fleet changes.22508 npmApache 2.0- FlicenseNot gradedqualityAmaintenanceEnables LLM-based agents and MCP-compatible clients such as Claude Desktop to perform CRUD operations on FHIR resources and query or manipulate clinical data through natural-language prompts, with document processing, semantic search, and LOINC terminology lookup.-
TDQS
Scored across 33 tools
Most tools map to a single resource/action, and the plan/preview write workflow is explicit, so agents can usually select correctly. However, the generic ct_search_api/ct_get_operation/ct_api_request trio overlaps in capability with every specialized tool, and the event-service assignment tools require close reading to distinguish.
All names use a consistent ct_ snake_case prefix and mostly follow verb_noun (list_, get_, create_, update_, delete_, search_). A few exceptions such as ct_status, ct_login, and ct_api_request break the verb_noun pattern but remain readable and consistent in style.
33 tools is heavy for an MCP server, and the generic API fallback means some specialized tools are optional rather than essential. Still, the broad ChurchTools domain (persons, groups, appointments, events, services) and the safe plan/execute pattern justify a larger surface, so it is borderline rather than excessive.
Core resources have strong lifecycle coverage: persons and groups are near-CRUD, appointments have full CRUD, and events support list/get/update/delete plus service assignment. Minor gaps remain (e.g., no create_event, calendar/service CRUD), but the generic ct_api_request provides a documented workaround.