Important
This repository is archived. MCP Servers are now a feature of version 11.14.0.
Repository bringing together all the MCP-related experiments within the Sinequa platform.
Important
Prerequisites
- Sinequa release >= 11.13.0.2057
- .NET Core only
- Beta mode
- Standalone WebApps only
The very first integration of MCP capacities within Sinequa WebApps is plugin-based only, i.e. we don’t deliver built-in tools for the moment but only the capacity to add tools by plugin.
In the plugins repository can be found implementations of such plugins corresponding to various usecases.
First of all, make sure to add the <sinequa>\bin\ModelContextProtocol.dll to the dependency of your plugin, and add the EnterpriseSearchMcpPlugin.cs file
To enable MCP capacity in a given WebApp, simply check this option and list the plugin you want to be usable.
Now that your tools are configured, make sure to restart your targeted Sinequa WebApps so it is launched with the MCP capacities.
Warning
When defining a new tool plugin, the restart of the WebApp is mandatory
The serving route is /mcp.
First, you are going to need an Access Token for the client. In the Admin, add /mcp to the Allowed JSON Methods of the Access Token(s) you want to use.
Now, you need an MCP client such as MCP inspector which is easily runnable locally using
npx @modelcontextprotocol/inspector
If you visit the URL logged when starting inspector you should see the following UI from which you can connect to your Sinequa MCP WebApp, list your tools and execute them.
Important
Authentication Support
- Bearer Token
- OAuth will coming soon