CRM
EveryAction MCP connector
The EveryAction connector brings supporters, contributions, events, and survey questions into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person on your team can search, record, and update EveryAction records as themselves, with every action logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect EveryAction to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect EveryAction once
-
Open Connections, choose Add connection, and pick EveryAction.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an EveryAction API key. One person generates a token in EveryAction and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect EveryAction to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect EveryAction to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect EveryAction to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect EveryAction to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with EveryAction through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Development
Log a gift right after the call
After a donor conversation, record the contribution in EveryAction and set up their pledge as a commitment, without leaving the conversation you are already in.
-
Organizing
Look up a supporter before you call
Search EveryAction for a person by name or email and see the activist codes and scores attached to them before you pick up the phone or knock on the door.
-
Events
Set up a canvass or house party
Create the event in EveryAction from the details in your planning notes, so it is ready for shifts and sign-ups the moment the date is confirmed.
-
Field
Keep the survey script current
Add a new survey question or reword an existing one in EveryAction as the script changes, and update a worksite when its details move.
-
Voter registration
Submit registration forms as a batch
Turn a stack of completed voter registration forms into a batch in EveryAction, and check the early vote fields your program tracks.
-
Finance
Reconcile contributions against disbursements
Pull the contributions and disbursements recorded in EveryAction for a period and check them against your books before the filing deadline.
Try asking
- “Search EveryAction people in Ohio added this week.”
- “Total contributions logged this month by activist code.”
- “Create an EveryAction event for the Saturday canvass.”
AI tools
EveryAction tools for your AI agents
29 tools are ready to call through Elaichi's MCP endpoint the moment you connect EveryAction, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting EveryAction gets you
6 screens from the product, each doing one job for your EveryAction account.
The agent
Ask about contributions, get real answers.
Plain language questions run against live EveryAction people, events and contributions.
- people
- contributions
- disbursements
- events
Ask Elaichi to work across your apps.
Search EveryAction people in Ohio added this week.
Total contributions logged this month by activist code.
Create an EveryAction event for the Saturday canvass.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect any MCP client to EveryAction over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
29 EveryAction tools ready to call.
People, contributions, disbursements, events and activist codes, with no custom code written.
- List all EveryAction API key profiles
- EveryAction people search
- Get single EveryAction activist code by ID
- Create a EveryAction bulk import job
Toolboxes
Every team gets its own toolbox.
Curate one EveryAction toolbox for fundraising, another for field, another for events.
- Fundraising
- Field
- Events
- Data
Shared connections
Teammates use the account, never the credential.
One person connects EveryAction, then shares that connection with named teams and members.
- Fundraising
- Field Midwest
- Events
- Data Ops
Audit log
Every contribution written is on the record.
When, who, what happened, type and resource, appended for every EveryAction call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, the digest ships.
Fetch EveryAction contributions, group them, draft a digest, approve it, post it back.
EveryAction digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch people
EveryAction
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
EveryAction
Queued
Collections and dashboards
Contribution numbers arrive before anyone asks.
Four metrics, 14 days of new EveryAction records, split by team, refreshed on schedule.
EveryAction health
Refreshed 4 minutes ago · every 15 minutes · from the people collection
People
1,284 ↓ 12%
Contributions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
People created
Last 14 days
By team
Share of activity
Fundraising 34%
Field Midwest 27%
Events 21%
Data Ops 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect EveryAction to Claude?
There are two steps. First, in Elaichi, choose EveryAction and paste the API key from your EveryAction account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and EveryAction is available in your next conversation.
Does EveryAction work with ChatGPT and Cursor as well as Claude?
Yes. Once EveryAction is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect EveryAction once and every client uses it, with the same access and the same log.
What can an AI agent actually do with my EveryAction data?
An agent can search EveryAction for a supporter and read the activist codes and scores on their record, record a contribution or a pledge commitment, and create an event. It can add or reword survey questions, submit a batch of voter registration forms, update a worksite, and start a bulk import from a list you already have. It can also list contributions, disbursements, folders, printed lists, and MiniVAN exports so you can ask questions about them in plain language.
Does connecting EveryAction give the AI access to my whole committee database?
No. The agent works inside what the connected EveryAction account is allowed to see, and each person signs in to Elaichi as themselves, so every request runs under their own access. Elaichi can narrow that further by team or by action, and it can never widen it beyond what EveryAction itself allows.
Can I stop an agent from deleting or changing things in EveryAction?
Yes. Restrictions in Elaichi work per action, so you can allow searching people and listing contributions in EveryAction while blocking deleting employers, creating contributions, or changing survey questions. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt can reach it.
What happens to an EveryAction connection when someone leaves?
Offboarding the person in Elaichi ends their access to EveryAction at once, in every client they used. A shared EveryAction connection keeps working for everyone else on the team. If you want to remove EveryAction entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Put EveryAction in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.