For Claude and other AI that supports MCP
Connect WislaSearch to Claude and work with thousands of files.
Gather, sum up, compare and see what depends on what across your contracts. Claude gets every contract that matches, with each value quoted from its document.
How it works
An ontology of your documents, checked value by value
An ontology of your documents is built under human control: types, topics and the terms of each contract. Every value has a quote from its document, and anything that does not pass the checks goes to a person.
- Read each document
- Sort by type and topic
- Extract terms, each with its quote
- Send unconfirmed values to a person
In the ontology
- Document types
- Topics
- Terms of each contract
Where data stays
Two ways to connect, and what stays with you
Our own chat can run on a local model: your questions, documents and answers stay inside your perimeter. Already use Claude? Connect it over MCP. Then your question and the passages our tools return go to Claude, under the terms your organisation already has with it. The documents and the index stay with you.
Our own chat on a local model
Claude over MCP
Documents and index stay with you
Why trust it
A complete list you can recount
The documents your AI works from are picked by a deterministic filter. It goes through every document you connected and returns each one that matches, so the list is complete and you can recount it. The AI chooses which filter to ask for; the filter decides what is on the list. Every value links back to the document it came from.
Example
Which contracts set an hourly rate of 10 to 30 euros?
Ask Claude. WislaSearch hands it exactly those contracts, each with the quote that sets the rate.
What comes back:
- the contracts, and only those
- the quote behind each rate
- a link to each contract
Pilot
A pilot on your documents
You pick a set of documents and the questions you need answered. We bring the core fields for your domain.
We run WislaSearch on your real documents, inside your perimeter or on a machine you control.
Together we ask your questions, recount the lists and read what went to a person.
You decide.
FAQ
From the blog
Three-way matching: what to check, and when to call a person
Matching an invoice against its purchase order and the goods receipt: the fields to agree first, the three outcomes, and what an exception card has to carry.
Built by WislaCodeWislaCode is an engineering unit that owns client and partner integrations end to end for banks, payment providers, lenders and acquirers - delivered under your controls, your architecture and your standards. wislacode.com

