civicrm-mcp
Related Servers
Alternatives to civicrm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Microsoft Dataverse API with safe-by-default configuration. Works with any Dataverse / Dynamics 365 environment.2339 npm7MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to read, search, create, update, and manage records in Twenty CRM with a safe, composable 14-tool interface and guarded destructive operations.142MIT
- AlicenseNot gradedqualityAmaintenanceTurns a WordPress site into a native MCP server: 39 structured tools for content, media, taxonomies, comments, widgets and site settings, with OAuth 2.1 + PKCE and per-call WordPress capability checks. Pure PHP inside WordPress — no bridge server or middleware to host.GPL 2.0
- AlicenseBqualityCmaintenanceEnables MCP-compatible clients to securely operate a WordPress site through a signed REST API, managing plugins, content, themes, menus, media, users, WooCommerce, Elementor, audits, and allowlisted WP-CLI commands.5836 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables exposing any REST or GraphQL API as MCP tools from a single JSON spec, with writes requiring explicit confirmation before being sent.MIT
- AlicenseNot gradedqualityAmaintenanceAn embeddable library and self-hosted MCP server for administering Joomla 6.x through bounded, auditable semantic actions via the Joomla Web Services API or a native companion plugin.3 npm4GPL 2.0
TDQS
Scored across 25 tools
Every tool has a clear, distinct purpose. There is no overlap between tools like find_contacts vs get_contact or list_entities vs describe_entity. The descriptions further clarify each tool's role.
All tools follow a consistent 'civicrm_verb_noun' pattern (e.g., list_events, create_contact, tag_contacts). The few exceptions like whoami and system_info are standard and do not break the overall pattern.
25 tools is on the higher side but appropriate for a comprehensive CRM server covering many entities (contacts, events, contributions, groups, memberships, tags, etc.). Each tool serves a specific need and the count feels justified.
The tool set covers most common CRM operations for reading and writing major entities. Some operations are missing (e.g., listing groups, updating contributions), but the generic civicrm_api4 tool can fill gaps if enabled. Overall, the surface is solid.