Features
Company knowledge, served to your AI tools
With MCP, the documents indexed in Reperix become a source that Claude, AI agents and your company automations can query. Within a precise perimeter, and always with the permissions of the person asking.
What you get
Reperix becomes the infrastructure, not just the chat
-
A standard, not a lock-in
MCP (Model Context Protocol) is the open standard AI tools use to connect to knowledge sources. Plug in Claude, your agents or your automations with no custom development.
-
A perimeter you shape
For each MCP you choose which document areas it exposes: just sales, just quality, or the whole archive. Create as many as you need, each with its own perimeter.
-
Always on behalf of a person
Every access is made with the identity of a Reperix user and inherits their permissions. An AI agent will never see a document that person could not open.
Use cases
Where an MCP makes the difference
-
The AI assistant you already use
People working in Claude or in an MCP-capable IDE query the company archive from there, without switching tools.
-
Automations and agents
Automated processes (checks, reply drafts, compliance reviews) draw on company documents as a reliable, cited source.
-
One source of truth
Instead of copying documents into every AI tool, knowledge stays in Reperix: one indexing pass, one permission model.
Security
The perimeter narrows, never widens
An MCP created for one department shows at most that department's documents, and never more than the connected user could see in the Reperix chat. The two protections stack, they do not replace each other: the perimeter selection and personal permissions always apply together. Every call is tracked, and every MCP can be revoked individually.
Want to connect your AI tools to your documents?
We will show you in a demo how an agent queries the archive with permissions and citations intact.