Neon CRM (No MCP Server Available)
Updated June 2026The Neon CRM (No MCP Server Available), built by Neon One, provides neon CRM (Neon One) is a widely used nonprofit relationship-management platform for donations, memberships, events, and fundraising campaigns, but no Model Context Protocol server exists for it today. It is community-built and best for API & Web.
by Neon One
About
Neon CRM (Neon One) is a widely used nonprofit relationship-management platform for donations, memberships, events, and fundraising campaigns, but no Model Context Protocol server exists for it today. Neon One's official GitHub organization is real but only hosts 2 unrelated internal repos (a Tailwind plugin and a Laravel worker), with no MCP implementation among them, and GitHub searches for "neon crm mcp" / "neoncrm mcp" surface only unrelated legacy API client libraries (a PHP SDK, a Node.js REST client) rather than any MCP server. This is consistent with most nonprofit CRMs in this space having a documented REST API but no AI-agent bridge built on top of it yet. If you need AI-agent access to Neon CRM data today, the closest real option is building a custom server against Neon's published REST API using one of those existing client libraries as a starting point. This entry is kept as a placeholder so the "neon crm mcp" search term stays discoverable and will be updated the moment a real server ships.
Trust verdict
How grades are computed →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.
Categories
Works With
Frequently Asked Questions
What is Neon CRM (No MCP Server Available)?
Who built Neon CRM (No MCP Server Available)?
Is Neon CRM (No MCP Server Available) free?
How do I install Neon CRM (No MCP Server Available)?
What does Neon CRM (No MCP Server Available) integrate with?
Repo Health
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
- Neon One
- Categories
- 2
- Integrations
- 2
Related Servers
Fetch
Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.
Time
Time and timezone conversion capabilities for AI assistants.
21st.dev Magic
Create crafted UI components inspired by the best 21st.dev design engineers.
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.
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.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →