Little Green Light MCP by usefulapi

Every tool targets a distinct resource and action: create/get/update/search constituents, create/get/search gifts, create/list notes and contact reports, list memberships, and list lookup entities. The boundary between global searches (lgl_search_gifts) and per-constituent lists (lgl_list_constituent_gifts) is clearly explained. No two tools appear to do the same thing.

All tools use a uniform snake_case lgl_verb_noun pattern (e.g. lgl_create_constituent, lgl_list_funds, lgl_search_constituents). The subresource lists follow a predictable lgl_list_constituent_<resource> pattern. The distinction between list_ for lookup entities and search_ for query-driven retrieval is consistent.

20 tools is slightly heavy for a single MCP server but justified by the CRM’s many distinct resources (constituents, gifts, notes, contact reports, memberships, plus seven lookup lists). Each tool maps to a separate LGL endpoint, so consolidation would reduce clarity. The count is reasonable, not excessive.

Core constituent flow is covered (create, get, update, search), but gifts, notes, contact reports, and memberships lack update/delete operations. For example, a gift can be created, fetched, listed, and searched but never edited or removed. These notable gaps will block agents that need to correct or clean up records, though the read/write surface covers common recording and lookup tasks.