01 — Cover

ai show & tell #4 · wix marketing

Plug Claude Into Wix

The bridge that lets the LLM talk to our other tools

MondayTableauCreative EngineGoogle Workspace+ ~95 more

Fabio Goldman · AI Transformation Team12 august 2026

02 — What an MCP is

01 / the idea

What an MCP actually is ?

A shared language, so any AI can talk to any tool that speaks it.

any tool

>_

Claude Code

one connection, then it just works

01

The server

Published once, by the tool.

02

The client

Your AI: Claude.ai, Claude Code, Cursor...

03

The connection

You make it only once.

03 — Willow

02 / ours

And this is Wix’s internal MCP = Willow

one endpoint

mcp-s.wewix.net/mcp

One address, then you have access to every tool your roles allow.

+ 100 systems

Your Wix identity

Reaches only what you already can.

Any agent

Desktop, Code, Cursor, Copilot.

Maintained for you

An expert team maintains it.

Monday

Slack

Tableau

User Voice

Creative Engine

Google Workspace

Babel

Octocode

+

~95 more

04 — Why Willow

03 / the argument

Why Willow, when native exists?

There is no native connector for some of them, and there never will be.

User VoiceBabelTableauPrompt Hub
Creative EngineOctocode

AND MOST OF THE TIME IT DOES MUCH MORE

Same tool, more capability. Over Willow, Google Workspace can edit Docs and Sheets. While the native connector only reads them. Willow is not just wider, it is often deeper.

One install, not hundreds

Native means you do an OAuth dance per tool.

Work identity

Permissions follow your Wix roles.

Stays inside Wix

If broken once, fixed for everybody.

05 — What to consider

04 / the honest part

What do you need to take into consideration?

the problem · three costs

It eats your context

~100 servers of tool definitions load into every chat.

It needs the VPN

Off the VPN network nothing works.

Cloud schedules can’t use it

A task that runs in the cloud has no VPN, so every Willow tool it calls fails.

the fix

Name three servers in the MCP field. Claude loads three, not a hundred.

MCP = creative-engine,
      tableau, google-workspace_

TIP

Go wide while you are learning. Scope down once you know what you use.

06 — Problem and fix

05 / when it stops

Willow gets you in. But not everywhere.

the problem

Sometimes it cannot reach the data.

Willow listed every Tableau dashboard, then would not open the workbook itself. Not a bug: that permission is not mine, and Willow only ever acts as me.

Claude

I tried to open that workbook and it came back refused.

MCP error −32603: tableau
get_dashboard_data_sources: 403 forbidden

The tool is connected. The permission is not.

the fix

Add a second, narrower door beside it.

Add it exactly the way you added Willow: the tool publishes its own extension file, and you install that one too. Try Willow first, then keep both. They coexist.

Claude

The dedicated Tableau connector is in.

willow: connected
tableau-direct: connected

Both doors open. Nothing else changed.

07 — Connect it

06 / live

Let us connect it.

claude desktop · one install

download it

On the Willow page: Connect MCP, pick Claude, Download extension.

find it

Browse extensions, pick Willow, then Install. The red warning is expected: it is an internal extension.

install it

Settings › Extensions › Advanced settings › Install Extension, or drag the .MCPB straight in.

it is in

Willow appears under Installed. Configure is where you scope it to a few servers.

claude code · one command

$ claude mcp add --transport http willow "https://mcp-s.wewix.net/mcp"
  willow: connected_

Two things that look like bugs

1.

VPN off means every tool fails. It is an internal address.

2.

The browser log-in pop-up is Willow authenticating you. Once, then never again.

08 — Ask what it can do

07 / the habit

Ask Claude what it can do.

one prompt, no tool names

example prompt

I need to audit which of our marketing dashboards nobody maintains any more. Which of your tools can do that, and what would you use each one for?|

A hundred tools is a wall, not a menu. Describe the job and Claude reads its own catalogue for you. It works on day one, before you know a single tool name.

Claude

I would use three of my Willow tools:

Tableau to list dashboards

Google Workspace to write it up

Slack to ask owners

reading tool catalogue...

Only works if you went wide. Scoped to three, it can only offer three.

09 — Showcase 1

showcase 01

Creative Engine

your prompt

/creative-engine_

Here remove the background and create the cover. Do not forget you should use the Creative Engine MCP.

the tool call

creative-engine

generate_image()
check_my_balance()
2 credits · rendering

the output

Same tool edits, removes backgrounds, expands a canvas and upscales. 2 credits per image, from your own Wix AI balance.

10 — Showcase 2

showcase 02

Tableau to Google Slides

your prompt

Search Tableau for our marketing dashboards, pull owner and last update, then build me a slide flagging everything nobody has touched in six months.

three tool calls

search dashboards

get metadata

create slide

the output

Marketing dashboard audit · Google Slides

Dashboard
Updated
Status

Performance Marketing Daily

Aug 2025

stale

Marketing Tools KPIs

Nov 2025

stale

Enterprise LP Traffic

Jul 2026

current

Marketing Home

Jun 2026

current

2 of 4 stale

No native Tableau connector exists. Half of this chain needs Willow.

11 — Where to start

08 / the shortlist

Where to start.

Roughly a hundred servers exist. So choose wisely!

make

Create the asset instead of briefing someone.

Creative Engine

edword

Prompt Hub

know

Answer the question with real numbers.

User Voice

Tableau

similarweb

daily

Make your daily work more efficient

Monday

Slack

Google Workspace

specialist

Narrow options, but unbeatable in their lane.

Babel

Octocode

wix-connect

Pick one from make, one from know, one you already use. That is a week of experiments.

12 — From GitHub

09 / from the outside world

Adding something from GitHub.

A public website where people share code. Nearly every open-source Claude skill, plugin and MCP server lives there.

how to add it, step by step

1

Open the repo and find the install line in the README.

2

Run it in Claude Code, or drag the downloadable file into Claude Desktop, Settings, Extensions.

3

Restart Claude, then confirm the tool appeared.

$ /plugin install [name-of-the-github-repo]
$ /plugin install watch@claude-video

github.com/bradautomates/claude-video

★ ~15k · MIT

GitHub repo front page for claude-video, zooming into the Code and Clone panel

The README is the instructions

It gives you the exact install command. You copy it. That is the whole skill.

Willow was checked by Wix. This was not

Anyone can publish here. Have a quick look at who made it before you install.

13 — Before you connect anything

10 / TRUST

Before you connect anything.

Who runs it?

Wix internal system? A company on GitHub? Or just a random person?

What can it read?

Your whole Drive, or one folder?

What can it change?

Many can post, create and send. Nobody checks this one.

Where does the data go?

Inside Wix, or out to somebody else’s cloud?

Can it run code on my machine?

A different risk class entirely.

Adding something from outside Wix?

Installing an external MCP from the terminal will not resolve on our network. Point npm at the internal mirror first:

npm config set registry
http://npm.dev.wixpress.com

14 — Three things to try

11 / WRAP

Three things to try this week.

Install Willow, VPN on

One click on Desktop, one command in Claude Code.

15 minutes

Use it wide for a week, then scope it

Try different tools, Discover first, optimise second. Deliberately that order.

week one

Ask the question you would open several tools for

Tableau, Monday and Slack in one sentence instead.

next question

None of this needs permission, a budget, or an hour blocked out.

15 — Close

ai show & tell #4

Thank You!

Claude does not need to be smarter.
It needs to have the right connections!

~100 tools · one endpoint

twenty minutes · one of us shows what they are actually doing with AInext up #5 · live artifacts