Skip to content

CRM

Membes MCP connector

Connecting Membes to Elaichi brings member profiles, events, registrations, groups, and forum topics to Claude, ChatGPT, Cursor, and any MCP client, so each person can look up and update membership records by asking, inside their own access.

  • 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 Membes to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Membes once

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

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

  3. Paste a Membes API key. One person generates a token in Membes 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.

membes
Membes
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.

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

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

Membes 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 Membes 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 Membes through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Membership

    Catch a member's profile up after a call

    Ask for a member by name or ID, see their details and past interactions, then log the conversation and update their contact information without opening Membes.

  • Events

    Set up an event and its registration types

    Describe the event, its dates, and the ticket categories you need, and have them created in Membes, then check what is already on the calendar for the same month.

  • Member services

    Register a member and fix a booking

    Register a member for an upcoming event, or change an existing registration when someone needs a different type or has updated their details.

  • Community

    See what groups and forums are discussing

    Pull the latest topics and replies across your Membes groups and forums, summarize what members are raising, and spot questions that still need an answer.

  • Marketing

    Build a list of members to invite

    Search profiles by membership type or custom field values, then pair the list with the events on your Membes calendar to decide who to invite to what.

  • Leadership

    Report on events and membership types

    List every event in a date range alongside your membership types and custom fields, and turn it into a plain summary for a board or committee meeting.

Try asking

  • “Which events have registrations open next month?”
  • “Find member profiles with no interaction since June.”
  • “Create a registration type for the autumn conference.”

See all 58 Membes tools below

Compare

Elaichi vs Zapier MCP vs Composio for Membes

All three can connect Membes 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 Membes, 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 Membes tools Allow or restrict single Membes 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 Membes 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

Membes tools for your AI agents

58 tools are ready to call through Elaichi's MCP endpoint the moment you connect Membes, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Membes gets you

6 screens from the product, each doing one job for your Membes account.

The agent

Ask about Membes profiles, get real answers.

Plain language questions run against live Membes profiles, events and registrations.

  • profiles
  • interactions
  • events
  • registration types

Ask Elaichi to work across your apps.

Which events have registrations open next month?

Find member profiles with no interaction since June.

Create a registration type for the autumn conference.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Membes.

One governed MCP endpoint over OAuth, no SDK and no shared API 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

58 Membes tools ready without custom code.

Profiles, interactions, events and registration types, with every method already wired up.

  • Membes token get access token
  • Membes token validate
  • Get single Membes profile by ID
  • Create a Membes profile
ElaichiTools
Tool Action Description
Membes token get access token Get Generate access token. This endpoint returns a JWT access token on success. An empty JSON object is returned on failure. Returns: access_token. Required: org_id, secret.
Membes token validate Validate Validate access token. This endpoint returns a JWT access token on success. An empty JSON object is returned on failure. Returns: membership_status, membership_type, surname, first_name, id, profile_number, membership_type_id, membership_status_id, email. Required: token_to_validate.
Get single Membes profile by ID Get Get Profile Detail. Returns: profile_details, groups, custom_fields, address. Required: id.
Create a Membes profile Create This endpoint adds a new profile. Required: first_name, surname.
Update a Membes profile by ID Update This endpoint update a profile. Required: id, first_name, surname.

Toolboxes

Every team gets its own Membes toolbox.

Membership, events and finance each see only the Membes tools they need.

  • Membership
  • Events
  • Engagement
  • Finance
ElaichiToolboxes
Name Source template Tools Created

Membership toolbox

Membes · profiles and renewals

Membes starter 18 Mar 4, 2026

Events toolbox

Membes · events and registration types

— 9 Mar 2, 2026

Engagement toolbox

Membes · profile interactions

— 24 Feb 27, 2026

Finance toolbox

Membes · registration fees and invoices

Membes starter 6 Feb 19, 2026

Support toolbox

Membes · member enquiries

— 31 Jan 30, 2026

Marketing toolbox

Membes · event promotion and segments

— 12 Jan 22, 2026

Shared connections

Teammates use Membes accounts, never the credential.

Each Membes connection shows who connected it and which teams share it.

  • Membership
  • Events team
  • Chapter operations
  • Finance
ElaichiConnections
Connection Scope Status Access
ME

Membes (Membership)

Connected by Emily Carter

Personal • Active 1 team · 6 members
ME

Membes (Events team)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
ME

Membes (Chapter operations)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
ME

Membes (Finance)

Connected by Tyler Reed

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

Membes (Support desk)

Connected by Ryan Hayes

Personal • Active Not shared
ME

Membes (Marketing)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Membes call is on the record.

When, who, what happened, type and resource, appended for each Membes request.

  • 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

Membes Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Membes Profiles Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Membes Profiles 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, Membes gets updated.

Fetch profiles, group them, draft a digest, approve it, post back to Membes.

Membes digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch profiles

    Membes

    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

    Membes

    Queued

Collections and dashboards

Membes numbers arrive before anyone asks.

Four metrics, 14 days of new profiles and a team breakdown, refreshed on schedule.

Membes health

Refreshed 4 minutes ago · every 15 minutes · from the profiles collection

Live

Profiles

1,284 ↓ 12%

Interactions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Profiles created

Last 14 days

By team

Share of activity

Membership 34%

Events team 27%

Chapter operations 21%

Finance 18%

FAQ

Frequently asked questions

How do I connect Membes to Claude?

There are two steps. First, connect Membes in Elaichi by pasting your Membes API key when prompted; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi and Membes is ready to use in Claude.

Does Membes work with ChatGPT and Cursor as well as Claude?

Yes. Once Membes 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 Membes once and every client you use picks it up.

What can an AI agent actually do with my Membes data?

With Membes connected, an agent can find a member's profile, see their event history and past interactions, create or update a profile, and log a new interaction. It can list events in a date range, create events and their registration types, register a member, and update an existing registration. It can also read your groups, forum topics, and replies, and list your membership types and custom fields. Because Membes has many actions available, short and specific asks such as "find the profile for Jane Lee" work better than long paragraphs.

Does connecting Membes give the AI everything in my membership database?

No. The AI only sees what the Membes account that was connected can see, and every request runs as the person who signed in to Elaichi. Elaichi can narrow that access further, for example to reading profiles but not creating events, but it can never widen it beyond what Membes itself allows that account.

Can my team share one Membes connection?

Yes. One person connects Membes in Elaichi and shares the connection with a team, and nobody else ever handles the Membes API key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who looked up a profile or registered a member, even through a shared Membes connection.

Can I stop an agent from deleting or changing things in Membes?

Yes. Restrictions in Elaichi are set per action, so you can allow reading Membes profiles and events while blocking anything that creates or updates them. A blocked action is never shown to Claude, ChatGPT, or any other client at all, so no prompt, however worded, can reach it.

What happens to a Membes connection when someone leaves?

When you offboard a person in Elaichi, their access to Membes through every client ends at once. If they had shared a Membes connection with a team, it keeps working for everyone else. If you want to remove Membes entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

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

Yes. Membes 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 Membes?

Yes. Both let Claude, ChatGPT or Cursor use Membes. 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 Membes call.

How is Elaichi different from Composio for Membes?

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 Membes: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Membes 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.