> For the complete documentation index, see [llms.txt](https://docs.owkin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.owkin.com/connect-and-integrate/authentication-and-sso-1.md).

# MCP & Agent tools

**Architecture pattern.** To maximize reasoning and agentic interoperability, K Pro integrates with customer tooling through MCP configurations rather than bespoke per-vendor connectors. Customer systems (e.g. ELN, LIMS, data lake, BI) are connected to K Pro as MCP servers, either Owkin-provided wrappers for common tools or the customer's own servers. Authentication and per-tool authorization flow through OIDC/SAML or service accounts/API keys (especially for bulk data querying where it may be more efficient).

Data stays in customer systems; K Pro queries in place. New integrations are MCP-server additions.

**Representative integrations and complementary functionality:**

* **Benchling, Dotmatics (ELN/LIMS).** Pull assay and entity data on demand into a reasoning session; push predictions and annotated records back through the same MCP surface.
* **Snowflake, S3, Databricks, GCS.** Read-only querying with customer credentials; no duplication into K Pro. The customer may run data processing components to augment their data with Owkin and industry standard models, or render it more compatible with agentic reasoning.
* **KNIME, Pipeline Pilot.** K Pro callable from REST or Python nodes as a pipeline step.
* **Spotfire, Tableau.** K Pro writes structured outputs back to the customer warehouse; existing dashboards refresh against those tables.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.owkin.com/connect-and-integrate/authentication-and-sso-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.