Wiwink MCP connector
The Wiwink connector lets Claude, ChatGPT, Cursor, Microsoft Copilot 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.
- Connects with an API key
- Free 14-day trial
- No credit card
List Wiwink contacts created this week by source.
Working in Wiwink with Elaichi
-
List all Wiwink countries
-
Get single Wiwink country by ID
-
List all Wiwink states
How to connect Wiwink to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Wiwink 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.
Wiwink MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Wiwink 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. The plugin directory lives at chatgpt.com/plugins.
Wiwink 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.
Wiwink MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Wiwink through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Wiwink is logged.
-
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.”
What connecting Wiwink gets you
6 screens from Elaichi, each doing one job for your Wiwink account.
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, Cursor or Microsoft Copilot
The agent
Ask in plain language, read live Wiwink records.
Questions about contacts, sources and states get answered from Wiwink itself.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Connect any MCP client to Wiwink over OAuth, no SDK, no shared key.
Tool catalog
100 Wiwink tools arrive ready to call.
Contacts, sources, states and countries are covered without a line of custom code.
Toolboxes
Every team gets its own Wiwink toolbox.
Curate one toolbox per team so each sees the Wiwink tools it needs.
Shared connections
Teammates use Wiwink without seeing a credential.
See who connected each Wiwink account and which teams and members it reaches.
Audit log
Every Wiwink call is written down.
When, who, what happened, type and resource for each contact and source touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Wiwink digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Wiwink
Queued
Automations
A schedule fires, Wiwink work gets done.
Fetch contacts, group them, draft a digest, get approval, post back to Wiwink.
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%
Collections and dashboards
Wiwink health counted, not asked for.
Four metrics, 14 days of contacts created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Wiwink
All three can connect Wiwink to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 Wiwink tools | Allow or restrict single Wiwink 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 Wiwink 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 role 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 restricting deletion of contacts, sources or statuses. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client at the same time.
Does the Wiwink MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Wiwink 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, Microsoft Copilot, 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 Wiwink?
Yes. Both let Claude, ChatGPT or Cursor use Wiwink. 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 Wiwink call.
How is Elaichi different from Composio for Wiwink?
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 Wiwink: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Wiwink in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot