Skip to main content
Glama
Sign In
Little Green Light MCP Server

Little Green Light MCP Server

by WillHeadlee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Little Green Light MCP Server

No user-submitted related servers found.

    Related Servers

    • CiviCRM MCP Server

      johncallhub
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to access and manage CiviCRM data, including contacts, activities, contributions, events, and memberships, with full custom field support.
      5
      MIT

    • com.addtocrm/crm

      crm-inputs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to look up work contact and company details, search prospects, check existing CRM records, and add or update people and companies in a connected CRM without exposing CRM credentials.
      MIT

    • HubSpot MCP Server

      Christos6996
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to access and manage CRM data by creating contacts and companies, retrieving activities and conversations, and performing semantic search over previously retrieved information with built-in vector storage and caching.
      -

    • db-connector

      adlkt
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query business databases directly via natural language, with enforced read-only access and secure query limits. Supports SQLite and PostgreSQL, and works with any OpenAI-compatible model.
      0
      ISC

    • Autotask MCP Server

      ddurko1950
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to directly query and manage Autotask PSA data through natural language, including ticket triage, time entry creation, company lookups, project management, billing review, and more.
      Apache 2.0
    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

    B3.1/5.0

    Scored across 148 tools

    Disambiguation4/5

    The overwhelming majority of tools use a clear entity+action pattern, so a CRUD tool for gifts, appeals, notes, etc. is easy to distinguish. The main friction points are the two invitation-creation tools (create_constituent_invitation vs create_event_invitation) and the cluster of constituent search/donor-lookup/report tools that overlap in audience even if their descriptions are careful.

    Naming Consistency4/5

    Most tools consistently follow verb_noun snake_case (list_, get_, create_, update_, delete_, search_). Deviations such as record_gift, recent_donors/lapsed_donors/top_donors, add_constituent_to_group, and constituents_missing_info break the pattern but remain understandable.

    Tool Count1/5

    At 148 tools this is an extreme surface for an MCP server, far beyond the 25+ threshold, and will create significant context overhead and selection difficulty. The broad entity coverage explains some of the size, but the toolset would be more usable split across focused servers or substantially consolidated.

    Completeness5/5

    The server covers full CRUD/lifecycle workflows for constituents, contact methods, gifts, campaigns, funds, events, appeals, notes, relationships, groups, memberships, volunteer time, class affiliations, and invitations, plus specialized donor analytics and review-queue submissions. The raw call_lgl_api passthrough also closes any remaining endpoint gaps, so there are no obvious dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources