All integrations

Custom MCP / APIs

The answer a shopper needs often lives in your own systems. WisWes calls your inventory, CRM or ERP directly through the MCP connector, so it answers and acts on real data.

What it does

WisWes calls your own endpoints — local store inventory, a CRM lookup, an ERP availability check — so it can answer questions and take actions grounded in your real systems, not a stale copy.

If your business logic can be reached over an API, the assistant can use it inside the conversation.

How it connects

You expose your services through an MCP server (we provide the pattern and docs) and authorize it once in your workspace. WisWes then calls those tools when a shopper’s question needs them.

See the MCP guide for how to define tools, arguments and return shapes — the assistant picks the right one automatically.

What you get

  • The assistant calls your inventory, CRM or ERP directly
  • Answers and actions grounded in your live systems
  • Define tools once via MCP — the assistant chooses when to use them
  • No data duplication or brittle sync jobs

How your services are wired in

Expose your systems as MCP tools once; WisWes picks the right one mid-conversation and acts on live data.

Shopper chatasks a question
WisWes agentpicks the right tool
MCP connectoryour authorized endpoints
Inventory · CRM · ERPyour live systems
Grounded answerback in the chat

Frequently asked questions

How do I expose my own API?

Through an MCP server — we provide the pattern and docs. You define the tools; WisWes calls them when a question needs them.

Is my data copied into WisWes?

No. WisWes calls your systems live through the connector, so answers reflect your real data with no duplication.

Connect it to your stack.

Start a 14-day free trial of WisWes — no credit card, cancel anytime. Or see the plans first.