little-green-light-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LGL_API_KEY | No | API key for Little Green Light donor CRM, obtained from Settings → Integration Settings → LGL API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_fundsA | List all funds configured in LGL. Small, rarely-changing reference data — cached for this session after the first call. |
| list_appealsA | List all appeals configured in LGL. Small, rarely-changing reference data — cached for this session after the first call. |
| list_gift_categoriesA | List all gift categories configured in LGL. Small, rarely-changing reference data — cached for this session after the first call. |
| list_gift_typesA | List all gift types configured in LGL. Small, rarely-changing reference data — cached for this session after the first call. |
| search_constituentsA | Search LGL constituents by name or email address. Returns a compact summary per match (name, email, phone, city/state). Giving totals are not included — use get_constituent for those. Pass verbose:true for the full record. |
| get_constituentA | Fetch one constituent's profile by LGL id, including giving totals computed from the full gift history. |
| get_constituent_giftsA | List the giving history for one constituent, most recent first. |
| search_giftsA | Search gifts across all constituents by date range. Useful for totals and reconciliation questions (e.g. 'gifts in 2025'). Fund/amount filtering isn't exposed by LGL's search endpoint — filter the results client-side if needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Tools are mostly distinct: list_funds, list_appeals, list_gift_categories, list_gift_types each target a different reference data type. search_constituents and get_constituent both relate to constituents but search is for lookup by name/email while get_constituent is for a specific ID with more detail. get_constituent_gifts and search_gifts are distinct (one per constituent, one across all). Only slight overlap between search_constituents and get_constituent, but descriptions clarify their purposes.
All tool names follow a consistent verb_noun pattern: 'list_' for reference data, 'search_' for search operations, 'get_' for fetching a single record, and 'get_constituent_gifts' for the gift history. This is uniform and predictable.
8 tools is well within the ideal 3-15 range. The server covers a focused set of operations for an LGL (Little Green Light) integration: listing reference data, searching constituents, fetching details, and querying gifts. Each tool has a clear purpose, and none seem redundant.
The tools cover querying and searching capabilities well, but there are no create, update, or delete operations, so it's a read-only surface. For a CRM/donation tool, one might expect capabilities like adding a gift or updating a constituent, but the server's stated purpose is not explicit about that. The lack of write operations is a notable gap for full lifecycle coverage, but it may be intentional for this MCP server.