Your SharePoint. Connected to your agents.
Argos indexes your on-premises SharePoint sites, from version 2013 to Subscription Edition, and exposes them to your agents through an MCP server. ODIN extracts the content; search covers text, meaning and the knowledge graph. SharePoint permissions are collected with the documents: an agent only returns to a user what that user can read.
On-premises SharePoint- Search & knowledge
- MCP-connected agents
- Per-user permission filtering
What you can do
Targeted synchronization
Libraries, pages and subsites: choose the folders and metadata in your scope. Additions, changes and deletions are picked up at every run.
SharePoint permissions enforced
Argos collects permissions with the documents and applies removals at the next synchronization. The agent only returns what the user can read.
One MCP server per team
Create MCP servers with their own scopes and keys. Full-text, semantic and graph search are included.
In detail
What Argos does with your SharePoint. What your agents see of it.
Argos now collects SharePoint permissions with the documents and filters answers for each user. Here is how it enforces those permissions, syncs your sites, makes them searchable and exposes them to your agents.
An application that queries Argos on behalf of a user only receives the documents that user can read in SharePoint. The filter is switched on server by server.
- Permissions collected at the source
- During a full synchronization, Argos records who can read each site, library and item with unique permissions, subsites included.
- Removals applied
- Every incremental synchronization reads SharePoint’s security change log: permissions removed, inheritance broken or restored, groups changed.
- Identity verified
- The application sends the user’s token (X-User-Token header), validated with Entra ID, ADFS, Keycloak, Authentik or Devana.
- Active Directory
- The user’s groups are resolved over LDAPS, nested groups and other forests included. SAML and FBA identities are declared through mappings.
- Cautious when in doubt
- The token narrows what the key can see and never widens it. When in doubt, access is reduced. A document the user cannot read is reported as not found.
- Tested before it is switched on
- Test a user: provider, groups, readable documents per site. The filter can only be switched on once a directory and a provider have been tested.
Good to know: a permission removed in SharePoint applies at the next incremental synchronization. Drafts are indexed like published versions, and site collection administrators see fewer documents through MCP than in SharePoint.
Argos reads SharePoint with a read-only service account and keeps its index up to date.
- Your existing access
- Kerberos with a keytab, NTLM or Basic, from SharePoint 2013 to Subscription Edition. The connection test checks authentication and lists the libraries.
- A scope you choose
- Libraries, pages and, optionally, subsites. Include or exclude subsites and folders, filter by metadata: future documents follow the same rule.
- Full and incremental
- The incremental run reads the change log: additions, changes, moves, deletions. The full run reconciles the whole site. Both can be scheduled.
- Extraction by ODIN
- A fast pass makes the whole collection searchable. A second one adds OCR and image descriptions, throttled so that user requests always come first.
- Reading on demand
- A file never processed that an agent asks for is extracted straight away, with priority.
- Recovery without loss
- Every document ends in an explicit status. An interrupted synchronization resumes from its cursor; failures are recorded with their reason and can be retried.
Agents query the index by words, by meaning or by the entities mentioned in the documents.
- Hybrid search
- Full text, name similarity and semantic search are merged into a single ranking.
- Knowledge graph
- People, companies, projects and their relationships are extracted from the documents, with their source files. The graph can also be explored in the dashboard.
- Metadata filters
- Dates, author, file type and your SharePoint columns. Agents only see the fields you choose to expose.
- Read and compare
- Content is read page by page, email attachments and embedded files included. Two documents are compared by lines or by words.
- Your models
- Semantic search, graph and vision use the models you declare, with any OpenAI-compatible provider: vLLM, Ollama, Azure, Mistral.
Argos is an MCP server: any MCP client connects to it over HTTP with a dedicated key.
- One space per team
- Each space is a full MCP server: its address, its keys, its sites and folders. Outside that scope, a document is reported as not found.
- Rules tied to folders
- A rule follows its folder when it is renamed or moved. Another folder cannot take the place of an excluded one.
- Dedicated keys
- A key is shown only when it is created and only its hash is stored. Optional expiry, immediate revocation.
- Tools you choose
- Browsing, reading, search, graph and comparison: each tool can be switched on or off.
- Clients ready to connect
- Copy-ready configurations for Devana, Suite 366, Claude, Cursor, VS Code and the TypeScript and Python SDKs.
- Logged calls
- Every call is logged with the tool, the key, the space and, where applicable, the end user.
Settings, tests and monitoring all happen in the dashboard.
- MCP test bench
- Run the tools as an agent would, on the server or space of your choice. An administrator can simulate a user, by identifier or by token.
- Metrics
- Duration per stage, queue wait, synchronizations, MCP calls and latency per tool, failures by reason, over 24 hours, 7 or 30 days. A Prometheus endpoint is provided.
- Failed processing
- Every failure keeps its reason. Retry by reason, by connection or by selection.
- Roles
- Viewing, operating, administering: three roles, enforced on the server. Sign-in to the dashboard goes through Devana.
- Encrypted secrets
- Passwords, keytabs and model keys are encrypted in the database (AES-256-GCM) and never returned by the interface.
- Deployment
- Docker Compose, Kubernetes or OpenShift. Adding workers increases processing throughput.
Runs on your premises.
Where this application runs, and the technologies that come with it.
- On-premises
- On your servers, with a configuration sized for you.
- Requirements
- Argos extends Devana.ai and uses a dedicated ODIN v2 instance. For SharePoint: a read-only service account, with Kerberos, NTLM or Basic. For permission filtering: the Full Read policy for that account, LDAPS access to Active Directory and an identity provider.
- Works with
Explore further
Technologies that work together.