Skip to main content
A knowledge store isn’t limited to what you upload or interview into it. By connecting an external MCP server, you give Clara access to data and actions that live in other systems.

​
Why connect an external MCP

There are two moments where this matters:
  • Work with Clara. Plug in an external data source or tool so Clara can draw on it while consolidating knowledge, on top of your uploaded documents and connected sources.
  • Use. In a chat or Task session, an external MCP gives Clarifeye the ability to act on your other applications, not just answer from what it knows.

​
How it works

External MCPs are configured at the knowledge store level, in the Settings tab. You need admin permission to add or edit one. To add a server, provide:
  • URL of the MCP server.
  • Client ID and Client secret, if the server requires them.
Then choose an authentication method:
  • OAuth 2.0 (recommended), the standard flow for MCP servers.
  • API key, for servers that authenticate this way instead.
The knowledge store defines the MCP server once; each user then connects with their own credentials.
When registering Clarifeye as an OAuth app on the external MCP server, it may ask for a callback (redirect) URL. Use https://<your-instance>/api/v1/mcp-oauth/callback/, e.g. https://eu.app.clarifeye.ai/api/v1/mcp-oauth/callback/ or https://us.app.clarifeye.ai/api/v1/mcp-oauth/callback/, replacing the host with your dedicated instance URL if you have one.