CRM
Wiwink MCP connector
The Wiwink connector lets Claude, ChatGPT, Cursor and other AI clients look up, create and update contacts, lead sources and pipeline statuses in Wiwink, with every call running under the signed-in person's own access and recorded in an audit log.
-
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 Wiwink to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Wiwink once
-
Open Connections, choose Add connection, and pick Wiwink.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Wiwink API key. One person generates a token in Wiwink 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 Wiwink 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 Wiwink 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 Wiwink 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 Wiwink 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 Wiwink through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Catch a contact up after a call
Ask the agent to find the contact you just spoke to in Wiwink, update their details and move their status to the next stage, all in one request.
-
Sales
Find every contact stuck at one stage
Pull a list of Wiwink contacts sitting at a given status and ask which ones have not moved, so you know who to chase before the week ends.
-
Marketing
See which sources bring real contacts
List the lead sources set up in Wiwink and ask for the contacts that came in through each one, so campaign spend can be compared against what actually landed in the CRM.
-
Marketing
Add a new campaign source in seconds
When a new campaign, event or partner starts sending leads, ask the agent to create the source in Wiwink so contacts are tagged correctly from day one.
-
Sales operations
Tidy pipeline statuses without clicking through
Rename, add or retire the statuses your team uses in Wiwink by describing the change, and keep contact statuses consistent as the sales process evolves.
-
Customer success
Check a customer's record before a renewal
Look up a customer's contact record in Wiwink, see their current status and source, and correct anything out of date before the renewal conversation.
Try asking
- “List Wiwink contacts created this week by source.”
- “Which Wiwink sources brought the most contacts last month?”
- “Update the Wiwink contact for Acme with a new state.”
AI tools
Wiwink tools for your AI agents
100 tools are ready to call through Elaichi's MCP endpoint the moment you connect Wiwink, 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 Wiwink gets you
6 screens from the product, each doing one job for your Wiwink account.
The agent
Ask in plain language, read live Wiwink records.
Questions about contacts, sources and states get answered from Wiwink itself.
- contacts
- sources
- states
- countries
Ask Elaichi to work across your apps.
List Wiwink contacts created this week by source.
Which Wiwink sources brought the most contacts last month?
Update the Wiwink contact for Acme with a new state.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect any MCP client to Wiwink over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
100 Wiwink tools arrive ready to call.
Contacts, sources, states and countries are covered without a line of custom code.
- List all Wiwink countries
- Get single Wiwink country by ID
- List all Wiwink states
- Get single Wiwink state by ID
Toolboxes
Every team gets its own Wiwink toolbox.
Curate one toolbox per team so each sees the Wiwink tools it needs.
- Sales
- Marketing
- Customer success
- Support
Shared connections
Teammates use Wiwink without seeing a credential.
See who connected each Wiwink account and which teams and members it reaches.
- Sales EMEA
- Sales North America
- Marketing
- Customer success
Audit log
Every Wiwink call is written down.
When, who, what happened, type and resource for each contact and source touched.
- 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, Wiwink work gets done.
Fetch contacts, group them, draft a digest, get approval, post back to Wiwink.
Wiwink digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch contacts
Wiwink
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
Wiwink
Queued
Collections and dashboards
Wiwink health counted, not asked for.
Four metrics, 14 days of contacts created and a team breakdown, refreshed on schedule.
Wiwink health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Sources
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales North America 27%
Marketing 21%
Customer success 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Wiwink to Claude?
First, connect Wiwink in Elaichi by pasting in your Wiwink API key. 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 https://api.elaichi.ai/mcp as the address. Claude asks you to sign in to Elaichi as yourself, and from then on Wiwink is available in your conversations.
Does Wiwink work with ChatGPT and Cursor as well as Claude?
Yes. Once Wiwink 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 Wiwink once and every client picks it up, so there is nothing to set up again per tool.
What can an AI agent actually do with my Wiwink data?
With Wiwink connected, an agent can look up contacts, create new ones, update their details and change their status, as well as list, add and edit the lead sources and pipeline statuses your team uses. It can also look up the countries and states Wiwink recognizes when filling in a contact's address. Because Wiwink offers many actions, short concrete asks such as "move this contact to Qualified" work better than long paragraphs.
Does connecting Wiwink give the AI access to my whole CRM?
No. Every call to Wiwink runs under the access of the person who signed in, so the agent sees and changes only what that person could see and change in Wiwink themselves. Elaichi can narrow that further with restrictions per team or per action, but it can never widen what someone is allowed to do in Wiwink.
Can I stop an agent from deleting or changing things in Wiwink?
Yes. In Elaichi you can restrict individual actions on the Wiwink connector, for example allowing contacts to be read and updated but blocking deletion of contacts, sources or statuses. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt, accidental or otherwise, can reach it.
What happens to a Wiwink connection when someone leaves the company?
When you offboard someone in Elaichi, their access to Wiwink through every AI client ends at once. If they were using a shared Wiwink connection, it keeps working for everyone else on the team. If you ever want to remove Wiwink entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Wiwink in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.