Skip to content

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.

1

In Elaichi

Connect Wiwink once

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

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

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

wiwink
Wiwink
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.

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

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

Wiwink 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 Wiwink 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 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.”

See all 100 Wiwink tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Wiwink, 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 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 $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

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.

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.

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

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
ElaichiTools
Tool Action Description
List all Wiwink countries List List countries in wiwink. Returns: id, name, iso. Optionally filter results by name or ISO code, or include related states by passing 'states' via the with[] parameter.
Get single Wiwink country by ID Get Get a single wiwink country by id. Returns: id, name, iso. Optionally include related states via the with[] parameter. Required: id.
List all Wiwink states List List states in wiwink. Returns: id, country_id, name for each state. Optionally filter by country_id or name, and include the related country object by passing 'country' via with[].
Get single Wiwink state by ID Get Get a single wiwink state by id. Returns: id, country_id, name. Optionally include the related country object via with[]. Required: id.
List all Wiwink sources List List all lead sources in wiwink. Returns: id, name, color, owned per source. Optionally filter results by name.

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
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Wiwink · contacts and sources

Wiwink starter 18 Mar 4, 2026

Marketing toolbox

Wiwink · lead sources and campaigns

— 9 Mar 2, 2026

Customer success toolbox

Wiwink · contact records and follow ups

— 24 Feb 27, 2026

Support toolbox

Wiwink · contact lookups

Wiwink starter 6 Feb 19, 2026

Operations toolbox

Wiwink · countries, states and data hygiene

— 31 Jan 30, 2026

Finance toolbox

Wiwink · contact and account reporting

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
WI

Wiwink (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
WI

Wiwink (Sales North America)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
WI

Wiwink (Marketing)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
WI

Wiwink (Customer success)

Connected by Tyler Reed

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

Wiwink (Support desk)

Connected by Ryan Hayes

Personal • Active Not shared
WI

Wiwink (Operations)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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

Wiwink Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Wiwink Contacts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Wiwink Contacts 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, 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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch contacts

    Wiwink

    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

    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

Live

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%

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 my team share one Wiwink connection?

Yes. One person connects Wiwink with the API key and shares the connection with a team in Elaichi, and nobody else on the team ever handles or sees that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every contact update or status change 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.

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