How do I get an API Key for GivingFuel?

Log in to your GivingFuel account, navigate to Extras > Integrations > API Keys, and click 'Add API Key' to generate your key.

Can I add new donations via the agent?

The GivingFuel Public API is primarily designed for data extraction and polling. To record new donations, use your GivingFuel hosted donation pages.

How do I filter donations for a specific date range?

Use the 'filter_orders_by_date' tool and provide an ISO date (YYYY-MM-DD). The agent will retrieve all records created after that date.

Does this support multiple Webconnex products?

This MCP server is specifically configured to filter results for GivingFuel (givingfuel.com). It ensures you only see fundraising-related data.

GivingFuel MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: GivingFuel
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to GivingFuel through Vinkius, pass the Edge URL in the `mcps` parameter and every GivingFuel 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="GivingFuel Specialist",
    goal="Help users interact with GivingFuel effectively",
    backstory=(
        "You are an expert at leveraging GivingFuel 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 GivingFuel "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 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 GivingFuel MCP Server

Connect your GivingFuel account to any AI agent to automate your fundraising data extraction and donor relationship management through the Model Context Protocol (MCP). GivingFuel is a powerful, flexible fundraising platform for nonprofits and ministries. This MCP server enables you to retrieve donation orders, track individual donor responses (registrants), and monitor active fundraising pages directly through natural conversation.

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

Key Features

Donation Oversight — List all donation orders for your organization, including transaction totals and status (completed, refunded, pending).
Donor Detail Discovery — Retrieve detailed records for individual donors and their specific form responses to understand donor sentiment.
Financial Transaction Tracking — Access financial processing data for both successful and failed charges to monitor payment health.
Page Management — List all active fundraising pages and events, retrieving detailed configuration metadata for each.
Donor CRM Insights — Access unified donor profiles from the Webconnex platform to track long-term donor engagement.
P2P Campaign Discovery — Retrieve data related to Peer-to-Peer fundraising campaigns and participant activity.
Real-time Synchronization — Keep your organization's fundraising data accessible to your AI assistant without leaving your primary workspace.

The GivingFuel MCP Server exposes 10 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 GivingFuel to CrewAI via MCP

Follow these steps to integrate the GivingFuel 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 10 tools from GivingFuel

Why Use CrewAI with the GivingFuel MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with GivingFuel 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 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

GivingFuel + CrewAI Use Cases

Practical scenarios where CrewAI combined with the GivingFuel MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries GivingFuel 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 GivingFuel, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain GivingFuel 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 GivingFuel against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

GivingFuel MCP Tools for CrewAI (10)

These 10 tools become available when you connect GivingFuel to CrewAI via MCP:

filter_orders_by_date

Filter by date range

filter_orders_by_status

Filter by completion

list_crm_contacts

List donor profiles

list_donation_orders

List all orders

list_donation_registrants

List individual donors

list_financial_transactions

List successful charges

list_fundraising_pages

List donation pages

list_peer_campaigns

List P2P campaigns

list_recent_donations

List latest 10 orders

verify_api_connection

Check connection

Example Prompts for GivingFuel in CrewAI

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

"List the last 5 donation orders received."

"Show me all fundraising pages active in my account."

"How many donations were marked as 'refunded' today?"

Troubleshooting GivingFuel MCP Server with CrewAI

Common issues when connecting GivingFuel 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

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

GivingFuel + CrewAI FAQ

Common questions about integrating GivingFuel 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.