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
