How do I get API Keys for GiveWP?

Log in to your WordPress admin, go to your User Profile, and scroll to 'Account Management'. Check 'Generate API Keys' and update your profile to see your keys.

What is the WordPress Base URL?

This is the root domain where your WordPress site is installed, for example: 'https://my-nonprofit.org'. Do not include '/wp-admin/'.

Can I edit donation forms via the agent?

The current version of the GiveWP API tools is primarily designed for data retrieval and reporting. Editing capabilities are not supported in this release.

How do I see donor history?

Use the 'find_donor_history' tool and provide the donor's email address. The agent will retrieve all donation records associated with that person.

GiveWP MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: GiveWP
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to GiveWP through Vinkius, pass the Edge URL in the `mcps` parameter and every GiveWP 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="GiveWP Specialist",
    goal="Help users interact with GiveWP effectively",
    backstory=(
        "You are an expert at leveraging GiveWP 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 GiveWP "
        "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 GiveWP MCP Server

Connect your GiveWP (WordPress plugin) account to any AI agent to automate your donation data extraction and fundraising reporting through the Model Context Protocol (MCP). GiveWP is the most popular WordPress plugin for online giving. This MCP server enables you to retrieve donation forms, track individual donor profiles, and monitor real-time fundraising statistics directly through natural conversation.

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

Key Features

Form Oversight — List all donation forms published on your WordPress site and fetch detailed configuration metadata and goal progress.
Donation Management — List all donations processed via the plugin, with support for filtering by specific forms or donors.
Donor Discovery — Retrieve detailed profile metadata for your unique donors and search across their giving history.
Real-time Analytics — Fetch high-level earnings and donation count statistics for your entire site or individual forms.
Read-only Security — Safely query your WordPress donation database with a secure integration designed for data visibility.
Plugin Transparency — Access high-level plugin metadata to verify API connectivity and account health.
Real-time Synchronization — Keep your self-hosted fundraising data accessible to your AI assistant without leaving your primary workspace.

The GiveWP 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 GiveWP to CrewAI via MCP

Follow these steps to integrate the GiveWP 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 GiveWP

Why Use CrewAI with the GiveWP MCP Server

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

GiveWP + CrewAI Use Cases

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

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

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

GiveWP MCP Tools for CrewAI (9)

These 9 tools become available when you connect GiveWP to CrewAI via MCP:

find_donor_history

Search by donor

get_form_details

Get form metadata

get_form_performance

Get form stats

get_plugin_stats

Get general stats

list_donation_forms

List all forms

list_plugin_donations

List all donations

list_plugin_donors

List all donors

list_recent_donations

List latest records

verify_api_connection

Check connection

Example Prompts for GiveWP in CrewAI

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

"List all active donation forms on my website."

"Show me the donation history for donor 'jane@example.com'."

"Get the fundraising stats for the 'Annual Fund' form (ID: 987)."

Troubleshooting GiveWP MCP Server with CrewAI

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

GiveWP + CrewAI FAQ

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