Connect Neon CRM to Claude Code

Make Claude track donors and record gifts in Neon CRM. From the terminal, inside the sessions where you already work.

How do you connect Neon CRM to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Neon CRM, you add a Neon CRM MCP server: a small hosted service that exposes Neon CRM's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Neon CRM account. No API keys pasted into config files.

claude mcp add --transport http neon-crm https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Neon CRM once connected?

Full read-write means Claude can pull a donor's complete giving history before a call, summarize donations by campaign or date range, record offline gifts and pledges, update donor accounts, and log touchpoints as activities. Fundraisers get answers and follow-through in one conversation, with approval on every write.

Search donor accounts by name or email and pull complete giving history
Summarize donations over a date range by campaign, fund, or amount
Create or update a donor account, after you approve
Record an offline donation or a pledge on an account, after you approve
Log a call or meeting as an activity on a donor's account
List upcoming events and pull their registration counts

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Neon CRM access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Neon CRM API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Neon CRM changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Neon CRM connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Neon CRM connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Neon CRM account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Neon CRM's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Neon CRM?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Neon CRM account it signs in with. Revoking access is one click in Neon CRM.

More on the Neon CRM connector

Neon CRM connector for claude.ai Bloomerang + Claude Code Follow Up Boss + Claude Code Acuity Scheduling + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us