Skip to content

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.

1

In Elaichi

Connect EveryAction once

  1. Open Connections, choose Add connection, and pick EveryAction.

  2. Optionally set Share with to give a team access, then press Connect.

  3. 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.

everyaction
EveryAction
Affinity
Attio
Clazar
Clio Manage
Close
2

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.

EveryAction MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

EveryAction MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

EveryAction MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.”

See all 29 EveryAction tools below

Compare

Elaichi vs Zapier MCP vs Composio for EveryAction

All three can connect EveryAction to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for EveryAction, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over EveryAction tools Allow or restrict single EveryAction tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per EveryAction call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

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
ElaichiTools
Tool Action Description
List all EveryAction API key profiles List List API key profiles via the EveryAction introspection endpoint, which returns information about the API key currently in use. Returns: databaseName, hasMyVoters, hasMyCampaign, committeeName, apiKeyTypeName, keyReference, userFirstName, userLastName, username, userId.
EveryAction people search Search Search for a person in EveryAction using a match candidate such as name, date of birth, phone, or email. Returns: vanId, firstName, lastName, middleName, party, employer, occupation, sex, dateOfBirth, person, customProperties. Providing a valid vanId overrides other search criteria.
Get single EveryAction activist code by ID Get Get a specific Activist Code in EveryAction by its id. Returns: activistCodeId, type, name, mediumName, shortName, description, scriptQuestion, status. Required: id (either an integer or a VAN encoded identifier such as EID28CG).
Create a EveryAction bulk import job Create Create a bulk import job in EveryAction by specifying a zipped, delimited file URL and the actions to perform on its data. Supports creating and/or updating Contacts, Contributions, ActivistCodes, and ContactsActivistCodes. Returns: jobId, file, actions. Required: description, file, actions. The zipped file must be no more than 20 MB and the source URL must use SFTP, FTPS, or HTTPS.
Create a EveryAction commitment Create Create a Recurring Commitment record in EveryAction and process or initiate the first installment contribution with payment details in the request body. Returns: commitmentId, contributionId. Required: contact, designation, gatewayId, startDate, frequency, amount, paymentMethod. Amount must be $0.01–$999,999.99; an Idempotency-Key header is required.

Toolboxes

Every team gets its own toolbox.

Curate one EveryAction toolbox for fundraising, another for field, another for events.

  • Fundraising
  • Field
  • Events
  • Data
ElaichiToolboxes
Name Source template Tools Created

Fundraising toolbox

EveryAction · contributions and commitments

EveryAction starter 18 Mar 4, 2026

Field toolbox

EveryAction · people and activist codes

— 9 Mar 2, 2026

Events toolbox

EveryAction · events and signups

— 24 Feb 27, 2026

Data toolbox

EveryAction · bulk import and file loading jobs

EveryAction starter 6 Feb 19, 2026

Compliance toolbox

EveryAction · disbursements and reporting

— 31 Jan 30, 2026

Voter Contact toolbox

EveryAction · early vote fields and canvasses

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
EV

EveryAction (Fundraising)

Connected by Emily Carter

Personal • Active 1 team · 6 members
EV

EveryAction (Field Midwest)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
EV

EveryAction (Events)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
EV

EveryAction (Data Ops)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
EV

EveryAction (Compliance)

Connected by Ryan Hayes

Personal • Active Not shared
EV

EveryAction (Voter Contact)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

EveryAction Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

EveryAction People Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

EveryAction People List Toolbox

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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch people

    EveryAction

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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%

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 my team share one EveryAction connection?

Yes. One person connects EveryAction in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who searched for a supporter or recorded a contribution, not the person who set up the connection.

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.

Does the EveryAction MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. EveryAction is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for EveryAction?

Yes. Both let Claude, ChatGPT or Cursor use EveryAction. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every EveryAction call.

How is Elaichi different from Composio for EveryAction?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to EveryAction: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put EveryAction in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.