How do I find my LGL API Key?

Log in to your Little Green Light account, navigate to Settings > Integration Settings > LGL API to enable and copy your unique API key.

What fields are required to create a gift?

You must provide a `constituent_id`, an `amount` (numerical), and a `gift_date` (YYYY-MM-DD).

Can I associate a gift with a specific campaign?

Yes, when using the `record_new_donation` tool, you can include a `campaign_id`, `appeal_id`, or `fund_id` within the JSON body.

Little Green Light MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: Little Green Light
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to Little Green Light through the Vinkius — pass the Edge URL in the `mcps` parameter and every Little Green Light tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Little Green Light Specialist",
    goal="Help users interact with Little Green Light effectively",
    backstory=(
        "You are an expert at leveraging Little Green Light tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Little Green Light "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Little Green Light MCP Server

Connect your Little Green Light account to any AI agent to automate your donor management and fundraising workflows. This MCP server enables your agent to manage constituent profiles, record new gifts, and query fundraising appeals directly from natural language interfaces.

When paired with CrewAI, Little Green Light becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Little Green Light tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Constituent Oversight — List and retrieve detailed profiles for all registered donors and organizations in your database
Gift Recording — Programmatically record new donations, pledges, and recurring gifts with associated amounts and dates
Fundraising Audit — Query active appeals, campaigns, and funds to monitor your fundraising efforts and allocations
Onboarding Automation — Create new donor records and update existing contact information seamlessly
Database Discovery — List all available organizational funds and campaign structures to map your financial logic

The Little Green Light MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Little Green Light to CrewAI via MCP

Follow these steps to integrate the Little Green Light MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 9 tools from Little Green Light

Why Use CrewAI with the Little Green Light MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Little Green Light through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Little Green Light + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Little Green Light MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Little Green Light for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Little Green Light, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Little Green Light tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Little Green Light against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Little Green Light MCP Tools for CrewAI (9)

These 9 tools become available when you connect Little Green Light to CrewAI via MCP:

create_new_donor

Requires first_name, last_name, or org_name. Create a new donor constituent

get_donor_details

Get details for a specific constituent

get_gift_details

Get details for a specific gift

list_donation_gifts

List recorded gifts and donations

list_donor_constituents

List donor constituents

list_fundraising_appeals

List active fundraising appeals

list_fundraising_campaigns

List fundraising campaigns

list_organizational_funds

List available organizational funds

record_new_donation

Requires constituent_id, amount, and gift_date. Record a new donation gift

Example Prompts for Little Green Light in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Little Green Light immediately.

"List all constituents in my Little Green Light account."

"Record a new donation of $100.00 for constituent ID '12345' dated today."

"Show active fundraising appeals."

Troubleshooting Little Green Light MCP Server with CrewAI

Common issues when connecting Little Green Light to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Little Green Light + CrewAI FAQ

Common questions about integrating Little Green Light MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.