Qomon MCP connector
The Qomon connector brings your contacts, donations, memberships and transactions into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and update supporter records in plain language within their own Qomon 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 Qomon to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Qomon once
-
Open Connections, choose Add connection, and pick Qomon.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Qomon API key. One person generates a token in Qomon 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.
Qomon MCP connector for 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.
Qomon MCP connector for 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.
Qomon MCP connector for 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 Qomon 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 Qomon through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Organizing
Catch a supporter up after a canvass
Back from the doors, tell the agent what changed and it updates the Qomon contact with the new phone number, address or support level. No typing into the app on your phone in the rain.
-
Fundraising
Check this week's donations before the meeting
Ask how donations in Qomon are tracking against last week and get the totals, the count and the average gift in one answer. Follow up with which donation prices people actually chose.
-
Membership
See which memberships are due to renew
Pull the list of Qomon memberships ending soon, grouped by price group, so the renewal drive starts with names rather than a spreadsheet export.
-
Finance
Reconcile a transaction bundle without digging
Open a Qomon transaction bundle by asking for it, see every transaction inside it and its history, and fix the bundle if a payment landed in the wrong place.
-
Data
Load a sign-up sheet without duplicates
Paste the names and emails from a rally sign-up sheet and the agent creates or updates each Qomon contact, matching people you already have instead of adding them twice.
-
Communications
Find the right form and campaign code
Ask which Qomon forms and code campaigns are live before a mailing goes out, and confirm the exact form a link should point to.
Try asking
- “Show this month's donations in Qomon and compare them to last month.”
- “Which Qomon memberships are up for renewal this quarter?”
- “Update Marie Dupont's Qomon contact with her new phone number.”
AI tools
Qomon tools for your AI agents
53 tools are ready to call through Elaichi's MCP endpoint the moment you connect Qomon, 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 Qomon gets you
6 screens from the product, each doing one job for your Qomon account.
The agent
Ask about supporters and donations in plain language.
Get answers from live Qomon contacts, memberships and transactions without opening a report.
- contacts
- donations
- memberships
- transactions
Ask Elaichi to work across your apps.
Show this month's donations in Qomon and compare them to last month.
Which Qomon memberships are up for renewal this quarter?
Update Marie Dupont's Qomon contact with her new phone number.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Qomon works in Claude, ChatGPT and Cursor.
One governed endpoint, connected once, no SDK and no shared API key to pass around.
Copy the endpoint
Tool catalog
53 Qomon tools, ready without writing code.
Contacts, donations, memberships, transaction bundles and forms, every resource and method already covered.
- Create a Qomon contact
- Get single Qomon contact by ID
- Update a Qomon contact by ID
- Delete a Qomon contact by ID
Toolboxes
Every team gets its own Qomon toolbox.
Fundraising sees donations, organizing sees contacts, each toolbox scoped to the team that needs it.
- Organizing
- Fundraising
- Membership
- Finance
Shared connections
Share one Qomon connection, never the key.
Teammates work through a connection you set up without ever seeing the API key.
- Field organizing
- Fundraising
- Membership
- Finance
Audit log
Know who touched every Qomon record.
When, who, what happened and which contact or transaction, kept in an append-only log.
- 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 runs your Qomon donation digest.
Donations are fetched, grouped and drafted into a digest, approved by a person, then posted back.
Qomon digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch contacts
Qomon
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
Qomon
Queued
Collections and dashboards
Qomon numbers that arrive without asking.
Contacts created over 14 days and donations by team, refreshed on a schedule, no model involved.
Qomon health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Donations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Field organizing 34%
Fundraising 27%
Membership 21%
Finance 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Qomon to Claude?
Connect Qomon in Elaichi first: paste your Qomon API key when prompted, and the connection is ready. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Claude can work with your Qomon contacts, donations and memberships.
Does Qomon work with ChatGPT and Cursor as well as Claude?
Yes. Once Qomon 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 Qomon once and every client you use picks it up.
What can an AI agent actually do with my Qomon data?
With Qomon connected, an agent can look up a supporter, create or update a contact, load a list of new sign-ups without duplicates, and answer questions about donations, memberships and transactions. It can open a transaction bundle and its history, list your forms and code campaigns, and show donation and membership prices. Short, concrete asks such as "show donations this month" work better than long paragraphs.
Does connecting Qomon give the AI everything in my organization?
No. Every call to Qomon runs inside the access of the person who signed in, so an agent sees the contacts, donations and memberships that person could already see in Qomon. Elaichi can narrow that further, for example to reading only, but it can never widen it beyond what Qomon itself allows.
Can I stop an agent from deleting or changing things in Qomon?
Yes. Restrictions in Elaichi work per action, so you can allow reading Qomon contacts and donations while blocking deletion of contacts or transaction bundles. A restricted action is never shown to the AI client at all, so no prompt, however worded, can reach it.
What happens to a Qomon connection when someone leaves?
Offboarding a person in Elaichi ends their access to Qomon through every client at once. If they set up a shared Qomon connection, it keeps working for everyone else on the team. When you want Qomon gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Qomon MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Qomon 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.
Put Qomon in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
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.