Skip to main content
Glama
YogiAdhik

civicrm-mcp

by YogiAdhik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to civicrm-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-worker-kit

      moraph-com
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to securely connect to your data through a remote deployment with OAuth 2.1 and PKCE, configurable sign-in, read/write consent, and audit logging. It exposes public tools without sign-in and authenticated tools that respect each user's permissions while validating arguments and recording every call.
      Apache 2.0

    • dataverse-mcp-server

      rededis
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Microsoft Dataverse API with safe-by-default configuration. Works with any Dataverse / Dynamics 365 environment.
      23
      46 npm
      8
      MIT

    • Twenty CRM MCP

      0xfabrica
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to read, search, create, update, and manage records in Twenty CRM with a safe, composable 14-tool interface and guarded destructive operations.
      14
      3
      MIT

    • wpagent-mcp

      THE-KIPDEV
      A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      58
      16 npm
      MIT

    • FORGE

      croresnos
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables exposing any REST or GraphQL API as MCP tools from a single JSON spec, with writes requiring explicit confirmation before being sent.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 25 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources