Little Green Light MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Little Green Light MCP by usefulapi is answering right now. Last checked 3 min ago. It exposes 20 tools. Last commit 10 Oct 2026.

Search Little Green Light donors, gifts, notes and memberships, and add gifts and contact reports.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

128 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

7 Oct a tool changed version2 times that day

30 Sep a tool changed version2 times that day

and 5 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check Little Green Light MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add little-green-light --transport http https://little-green-light.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "little-green-light": {
      "url": "https://little-green-light.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.little-green-light]
url = "https://little-green-light.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "little-green-light": {
      "url": "https://little-green-light.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "little-green-light": {
      "url": "https://little-green-light.usefulapi.io/mcp"
    }
  }
}

Available tools 20

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

lgl

lgl_create_constituent

WRITE: add a new constituent (person or organization) to the account, optionally with email addresses, phone numbers, street addresses and group memberships. LGL's schema marks first_name, last_name and email_addresses as required. Search first (lgl_search_constituents) to avoid creating a duplicate. LGL: POST /api/v1/constituents.

lgl_create_contact_report

WRITE: log a contact report (a call, email or meeting with a constituent). text is required; the type may be given by id or name (e.g. 'Call'; see lgl_list_type_values type=contact_report_types). LGL: POST /api/v1/constituents/{constituent_id}/contact_reports.

lgl_create_gift

WRITE: record a gift (donation, pledge payment, in-kind, etc.) on a constituent's record. This writes a CRM record of a gift that already happened — it does NOT charge a card or move money. Give gift_type_id or gift_type_name (required; see lgl_list_type_values type=gift_types). Fund, campaign, appeal, event, gift category and payment type may each be given by id or by exact name. Set ack_template_name to 'do_not_ack' to skip acknowledgment. LGL: POST /api/v1/constituents/{constituent_id}/gifts.

lgl_create_note

WRITE: add a note to a constituent's record. text and original_date are required; the note type may be given by id or name (e.g. 'General'; see lgl_list_type_values type=note_types). LGL: POST /api/v1/constituents/{constituent_id}/notes.

lgl_get_constituent

Full details for one constituent by LGL id: names, salutations, addresses, phone numbers, email addresses, groups, memberships and custom attributes. LGL: GET /api/v1/constituents/{id}.

lgl_get_gift

Full details for one gift by id: amount, deductible amount, dates, fund/campaign/appeal/event, payment type, acknowledgment template, tribute and custom fields. LGL: GET /api/v1/gifts/{id}.

lgl_list_appeals

Fundraising appeals (mailings, emails, asks) with campaign, date, financial goal, cost and active flag. Use the ids and names when recording gifts or filtering searches. LGL: GET /api/v1/appeals.

lgl_list_campaigns

Campaigns with start/end dates, financial goal, code and active flag. Use the ids and names when recording gifts or filtering searches. LGL: GET /api/v1/campaigns.

lgl_list_constituent_contact_reports

Contact reports (calls, emails, meetings) logged for a constituent, with type, date, text and team member. LGL: GET /api/v1/constituents/{constituent_id}/contact_reports.

lgl_list_constituent_gifts

A constituent's giving history: every gift with amount, date, gift type, fund, campaign, appeal, event and payment type. LGL: GET /api/v1/constituents/{constituent_id}/gifts.

lgl_list_constituent_memberships

A constituent's memberships: level, start date and finish date — use it to see whether someone is current or lapsed. LGL: GET /api/v1/constituents/{constituent_id}/memberships.

lgl_list_constituent_notes

Notes recorded on a constituent (type, text, original date). LGL: GET /api/v1/constituents/{constituent_id}/notes.

lgl_list_events

Events (galas, lunches, board weekends) with dates, campaign, event type, goal and active flag. Use the ids and names when recording gifts or filtering searches. LGL: GET /api/v1/events.

lgl_list_funds

Funds (where gifts are designated) with campaign, code, financial goal and active flag. Use the ids and names when recording gifts or filtering searches. LGL: GET /api/v1/funds.

lgl_list_groups

Constituent groups (e.g. Board Member, Staff, Volunteer) with their ids and keys. Use the ids and names when recording gifts or filtering searches. LGL: GET /api/v1/groups.

lgl_list_team_members

LGL user accounts on the team (name, email, admin flag) — the values a gift or contact report's team_member refers to. Use the ids and names when recording gifts or filtering searches. LGL: GET /api/v1/team_members.

lgl_list_type_values

The account's configured lookup values for one type — the ids and names other tools accept. gift_types, payment_types and gift_categories come from their own endpoints (GET /api/v1/gift_types, /payment_types, /gift_categories — the last optionally filtered by gift_type_id); every other type from GET /api/v1/types/{type} (contact_report_types, note_types, appeal_types, event_types, email/phone/street/web address types, mailing_types, volunteering_categories, list_types).

lgl_search_constituents

Search active constituents (donors, members, volunteers, organizations). Give `name` and/or `email` for the common case, or raw `terms`. Available term fields: name, eaddr (email contains), phone_number, street, city, state (2-letter), postal_code, country, keyword (keyword id), updated_from / updated_to (YYYY-MM-DDTHH:MM:SSZ), membership_status (0 lapsed, 1 active), membership_level (comma-separated ids), membership_end_date_from / _to (YYYY-MM-DD), external_id, constituent_type (0 individual, 1 organization), groups (comma-separated group ids), lists (comma-separated list ids), custom_attr (key|op|value). At least one term is required. LGL: GET /api/v1/constituents/search.

lgl_search_gifts

Search active gifts across the account — e.g. everything received in a date range, or gifts to one fund or campaign. Give date/updated bounds and/or raw `terms`. Available term fields: date_from / date_to (YYYY-MM-DD), gift_types (in|ni + comma ids, e.g. in|1,7), gift_amount (gte|lte|btw|gt|lt|eq|ne + number[s], e.g. btw|100|1000), payment_types, campaigns, funds, appeals, events, categories (in|ni|bl + comma ids), appeal_types, event_types, constituent_type (0/1), gift_ids, external_gift_ids, created_from / created_to and updated_from / updated_to (YYYY-MM-DDTHH:MM:SSZ). At least one term is required. LGL: GET /api/v1/gifts/search.

lgl_update_constituent

WRITE: change scalar fields on an existing constituent (name, salutation, job title, org name, deceased flag, etc.). Only the fields you pass are sent. LGL's update schema marks first_name and last_name as required, so pass the current values (from lgl_get_constituent) if you are not changing them. Addresses, emails and phones are not edited here. LGL: PATCH /api/v1/constituents/{id}.

Endpoints

URL	Transport	State	Latency	Checked
https://little-green-light.usefulapi.io/mcp	streamable-http	answering	148 ms	3 min ago

Alternatives to Little Green Light MCP by usefulapi

same job, measured the same way

Textline MCP by usefulapi

by usefulapi

Read Textline conversations, contacts and reports; send a text, add notes, resolve or transfer.

23 tools answering

HappyFox MCP by usefulapi

by usefulapi

Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.

23 tools answering

FreeAgent MCP by usefulapi

by usefulapi

Read FreeAgent contacts, invoices, bills, banking and reports; add contacts, draft invoices, time.

20 tools answering

Mailchimp MCP by usefulapi

by usefulapi

Read audiences, members, campaigns and reports; add, update, tag and archive subscribers.

18 tools answering

Sendlane MCP by usefulapi

by usefulapi

Manage Sendlane lists, contacts, tags and custom fields; read campaign and SMS reports.

31 tools answering

Checkout.com MCP by usefulapi

by usefulapi

Read Checkout.com payments, disputes, reports and payouts.

18 tools answering

EmailOctopus MCP by usefulapi

by usefulapi

Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus.

13 tools answering

Benchmark Email MCP by usefulapi

by usefulapi

Manage Benchmark Email lists and contacts, and read campaign reports: opens, clicks, bounces.

25 tools answering

Little Green Light MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Little Green Light MCP by usefulapi do?

It exposes 20 tools, read directly from the server on our last check. Among them: lgl_create_constituent, lgl_create_contact_report, lgl_create_gift, lgl_create_note, lgl_get_constituent, lgl_get_gift and 14 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Little Green Light MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 128 ms. The bar chart above shows every period we have measured.

How do I connect Little Green Light MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Little Green Light MCP by usefulapi need an API key?

No. Little Green Light MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 20 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Little Green Light MCP by usefulapi?

It answers our handshake in 128 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Little Green Light MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.