neon-crm

Tools

22 tools: 18 read-only, 0 change data, 4 high risk (delete, pay, send or run code).

No tool name points to sending messages.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 5,219 tokens of tool definitions and a 680 ms handshake.

• high riskneon_create_accountCreate a constituent account: an INDIVIDUAL (a person) or a COMPANY (with company_name, plus an optional primary contact). Neon's Account Match may merge it into an existing account with the same name and email, so check neon_list_accounts by email first. Returns the new id. Neon: POST /accounts.
• high riskneon_update_accountChange an account's name, email, job title, company name or do-not-solicit / email opt-out flags. Only the fields you pass are changed (PATCH). The type must match the account (see neon_get_account). Addresses are not edited here. Neon: PATCH /accounts/{id}.
• high riskneon_create_activityCreate an activity - log an interaction with a constituent (call, meeting, note) or schedule a task. Needs a subject, a start date, a time zone id (neon_list_properties name=systemTimezones), a status id (name=activityStatuses) and a priority; link it to accounts and assign it to system users. Re...
• high riskneon_update_activityChange an activity's subject, note, status (e.g. mark it completed) or priority. Only the fields you pass are changed (PATCH). Neon: PATCH /activities/{id}.
• read-onlyneon_get_organization_profileFetch the Neon CRM organization these credentials belong to - its name, org ID and app URL. A cheap way to confirm the org ID and API key work. Neon: GET /properties/organizationProfile.
• read-onlyneon_list_accountsList constituent accounts (individuals and companies), optionally filtered by email, first or last name, or type. Returns accountId, names, email and userType. For richer queries use neon_search. Neon: GET /accounts.
• read-onlyneon_get_accountFetch one account in full - returned as individualAccount or companyAccount with its primary contact, addresses, consent, custom fields, current membership status and timestamps. Neon: GET /accounts/{id}.
• read-onlyneon_list_search_fieldsDiscover the field names neon_search accepts for a resource: kind=searchFields gives filterable fields with their allowed operators; kind=outputFields gives the columns you can return (standard field names plus custom fields with numeric ids). Call this before neon_search. Neon: GET /{resource}/s...
• read-onlyneon_searchReport-style search over accounts, donations (includes pledges and pledge payments), activities or events. Give filter criteria (field + operator + value), the output columns to return (standard field NAMES as strings, or custom-field IDS as integers - both from neon_list_search_fields), and 0-ba...
• read-onlyneon_list_account_donationsList one account's donations (amount, date, fund, campaign, purpose, status, payments), newest first by default. Neon: GET /accounts/{id}/donations.
• read-onlyneon_list_account_membershipsList one account's membership history - level, term, start and end dates, fee, status (e.g. SUCCEEDED/FAILED) and auto-renewal. Filter to active or the primary active membership. Neon: GET /accounts/{id}/memberships.
• read-onlyneon_list_account_event_registrationsList the event registrations one account has made, optionally for a single event. Neon: GET /accounts/{id}/eventRegistrations.
• read-onlyneon_get_donationFetch one donation - amount, date, fund, campaign, purpose, source, tribute, soft-credit solicitor, payments and status. Neon: GET /donations/{id}.
• read-onlyneon_get_membershipFetch one membership - level, term, dates, fee, status, auto-renewal, sub-members and payments. Neon: GET /memberships/{membershipId}.
• read-onlyneon_list_membership_levelsList the organization's membership levels (id, code, description, rank, type, status). Neon: GET /memberships/levels.
• read-onlyneon_list_eventsList events, filterable by name, category, date window, published or archived state. Dates are YYYY-MM-DD. Only Neon's legacy events are exposed by the API. Neon: GET /events.
• read-onlyneon_get_eventFetch one event - name, summary, dates, location, capacity, category, campaign, registration and financial settings. Neon: GET /events/{id}.
• read-onlyneon_list_event_registrationsList the registrations for one event - registrant account, tickets and attendees, amount, payments. Optionally only one registrant. Neon: GET /events/{id}/eventRegistrations.
• read-onlyneon_list_campaignsList fundraising campaigns (id, code, name, status). Neon: GET /campaigns.
• read-onlyneon_get_campaignFetch one campaign - dates, goal, fund, purpose, parent campaign, status, page URLs and fundraising statistics. Neon: GET /campaigns/{id}.
• read-onlyneon_get_activityFetch one activity (a logged interaction or task) - subject, note, dates, linked accounts, assigned users, status and priority. Neon: GET /activities/{id}.
• read-onlyneon_list_propertiesList one of the organization's lookup lists - the ids other tools need: funds, purposes, sources, solicitation methods, activity statuses and system time zones (for neon_create_activity), system users, individual and company types, event categories, countries, states/provinces, genders, prefixes....

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-04, 680 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-052026-10-04

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Marketing, email and messaging, ranked by days answering.

What agents looked for

This week agents asked 7Maps for marketing, email and messaging servers 1 time; this server was shown 0 times and picked 0 times.

Owners see the keywords, the servers picked instead, failure reasons and a comparison with similar servers in Owner Insights.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/neon-crm.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/neon-crm.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=neon-crm.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/neon-crm.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/neon-crm.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=neon-crm.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.