🌐

Kindful (No MCP Server Available)

Updated June 2026

The Kindful (No MCP Server Available), built by Kindful (Bloomerang), provides kindful is a nonprofit donor-management CRM (now part of Bloomerang) for gift processing, campaign tracking, and volunteer coordination, but no Model Context Protocol server exists for it today. It is community-built and best for API & Web.

by Kindful (Bloomerang)

About

Kindful is a nonprofit donor-management CRM (now part of Bloomerang) for gift processing, campaign tracking, and volunteer coordination, but no Model Context Protocol server exists for it today. Kindful's official GitHub organization is real and has 32 public repositories, but they're all internal engineering tooling from years past (OmniAuth strategies, a Drupal Commerce module, Rails/Ruby infrastructure gems) — none related to MCP or AI-agent access. GitHub searches for "kindful mcp" return nothing relevant beyond unrelated hackathon projects that happen to share the name. This is consistent with most nonprofit CRMs in this cluster having no AI-agent bridge built on top of their APIs yet. If you need AI-agent access to Kindful data today, the closest real option is building a custom server against Kindful's REST API directly. This entry is kept as a placeholder so the "kindful mcp" search term stays discoverable and will be updated the moment a real server ships.

Unverifiable
not scored

No repository for this entry resolves against the live GitHub API, so there is nothing to verify. It is deliberately left unscored rather than given a number we cannot stand behind.

What could not be measured

These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.

  • Source verificationunknown

    No repository for this entry resolves against the live GitHub API. Without a confirmed source there is nothing to inspect, so this entry is excluded from trust scoring entirely rather than scored on catalog metadata alone.

Frequently Asked Questions

What is Kindful (No MCP Server Available)?
Kindful (No MCP Server Available) is an MCP server built by Kindful (Bloomerang). Kindful is a nonprofit donor-management CRM (now part of Bloomerang) for gift processing, campaign tracking, and volunteer coordination, but no Model Context Protocol server exists for it today. Kindful's official GitHub organization is real and has 32 public repositories, but they're all internal engineering tooling from years past (OmniAuth strategies, a Drupal Commerce module, Rails/Ruby infrastructure gems) — none related to MCP or AI-agent access. GitHub searches for "kindful mcp" return nothing relevant beyond unrelated hackathon projects that happen to share the name. This is consistent with most nonprofit CRMs in this cluster having no AI-agent bridge built on top of their APIs yet. If you need AI-agent access to Kindful data today, the closest real option is building a custom server against Kindful's REST API directly. This entry is kept as a placeholder so the "kindful mcp" search term stays discoverable and will be updated the moment a real server ships.
Who built Kindful (No MCP Server Available)?
Kindful (No MCP Server Available) was built by Kindful (Bloomerang).
Is Kindful (No MCP Server Available) free?
Yes, Kindful (No MCP Server Available) has a free option. This MCP server is free and open-source. Check the GitHub repository for details.
How do I install Kindful (No MCP Server Available)?
Kindful (No MCP Server Available) has no verified public repository, so there is no confirmed install command for it.
What does Kindful (No MCP Server Available) integrate with?
Kindful (No MCP Server Available) integrates with Claude Desktop, Cursor.
No verified public repositoryVisit Website

Repo Health

Local install

Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.

Install
npm

Repo recency not yet available for this server.

Quick Info

Install Type
npm
Author
Kindful (Bloomerang)
Categories
2
Integrations
2

Related Servers

🌐

Fetch

Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.

Local
📋

Time

Time and timezone conversion capabilities for AI assistants.

Local
💻

21st.dev Magic

Create crafted UI components inspired by the best 21st.dev design engineers.

Local
🌍

Apify MCP Server

The Apify MCP server gives AI agents access to 6,000+ ready-made cloud scrapers, crawlers, and automation tools on the Apify Store — no infrastructure required. Connect to Apify Actors that extract data from social media platforms (Instagram, TikTok, LinkedIn), search engines (Google, Bing), e-commerce sites (Amazon, eBay), maps (Google Maps), and virtually any website. Each Actor runs in the cloud with managed proxies, browser fingerprinting, and anti-bot bypass built in. Use the Apify MCP server to query Actors by task, stream results directly into your AI context, run custom scraping Actors from your Apify account, and chain multiple data extraction steps in a single workflow. Supports tool filtering to expose only the Actors you need, and integrates with Apify's RAG web browser Actor for retrieval-augmented generation use cases.

Auth required
🌍

Browserbase MCP Server

Browserbase MCP and Stagehand MCP are the same server under two names, and this catalog lists both because people search for both — this page is the platform view, /servers/stagehand covers the natural-language automation layer that runs inside it. What Browserbase supplies is the browser itself: a headless Chrome session running in Browserbase's cloud rather than on the machine your agent is on, which is the reason to use it at all. The session is a real, addressable browser with its own residential-proxy and stealth configuration and a recorded replay you can watch afterwards, so an agent's browsing survives being run from a datacenter IP, and a failed run is debuggable after the fact instead of being a black box. Nothing renders on the developer's machine, so a long-running agent is not tied to a desktop staying awake. Browserbase's recommendation is the hosted server at https://mcp.browserbase.com/mcp over streamable HTTP — they operate it and absorb the model inference that the instruction-following tools require. Clients without HTTP transport connect via npx mcp-remote https://mcp.browserbase.com/mcp. Self-hosting installs @browserbasehq/mcp-server-browserbase from npm and needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID from your dashboard. Six tools are exposed — start and end for session lifecycle, navigate, act, observe and extract — and they are documented in detail on the Stagehand entry, because the act/observe/extract trio is Stagehand's model rather than Browserbase's. One thing to know before self-hosting: the browserbase/mcp-server-browserbase repository was archived on 2026-07-20 and its README now says it is kept for historical reference and should not be read as representative of the current production service. The npm package still installs and the star count on this page belongs to that archived repo; the hosted endpoint is the path Browserbase actually maintains.

Local

Sponsored

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →