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.
58 tools
How to connect
How to connect Membes to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Membes once
-
Open Connections, choose Add connection, and pick Membes.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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 Membes 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 Membes 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 Membes 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 Membes 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 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.”
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.
No tools match your search.
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 clientsClaude
ChatGPT
Cursor
Copy the endpoint
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
ElaichiToolsToolboxes
Every team gets its own Membes toolbox.
Membership, events and finance each see only the Membes tools they need.
- Membership
- Events
- Engagement
- Finance
ElaichiToolboxesShared 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
ElaichiConnectionsAudit 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 logLaunching 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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch profiles
Membes
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
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
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%
Related connectors
More from the catalog
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 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.
Put Membes in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.