MCP server
For most AI assistant applications, Instructions for configuring the MCP server are documented in the Hackolade Model Hub application. Users can access these instructions by opening the hamburger menu ☰ , then clicking on Connect AI assistants with MCP
Administrators are still required to perform some configuration when authentication is enabled. There is one exception: Microsoft 365 Copilot's configuration requires a deeper configuration, described below.
Authentication configuration
The same authentication configured to access the Model Hub application can be used to log users in to the MCP server.
To achieve this, a new redirect URL needs to be added to the configured authentication provider. The URL to add depends on the AI assistant application you're targeting.
The following is a list of applications with their redirect URL:
| Assistant | Redirect URL | Notes |
|---|---|---|
| Claude Desktop | https://claude.ai/api/mcp/auth\\_callback | |
| Cursor | cursor://anysphere.cursor-mcp/oauth/callback | |
| VS Code | http://127.0.0.1 | VSCode starts a server on a random port on the host machine to perform the login. |
Note: when configuring these redirect URIs in Azure Entra ID, make sure to add them for the Mobile and desktop applications platform
Microsoft 365 Copilot
To configure the MCP server to Copilot, you need to be able to create agents in Copilot Studio.
Follow these steps to complete the configuration of the MCP server
-
Open on the Agents menu, then click on Create blank agent
-
Give the agent a name like Hackolade Model Hub agent
-
Go to tools, then click on + Add a tool
-
In the modal that opens, select Add new MCP
-
Fill the form
- Server name: hackolade-model-hub
- Server description: Use the MCP tools provided by the Hackolade model HUB application
- Server URL: https://\<model-hub-domain-name>/api/v1/mcp
- Authentication: Select OAuth 2.0 then Dynamic discovery as a type
- Click on Create
The form should look like the following
In the next screen, click on Not connected then Create new connection Then click on Create.
At this point, you should probably see a login error, and the error should mention an invalid redirect_uri like the picture below
Copilot Studio generates a redirect URI that differs for each agent/tool, so make sure to copy the redirect URI from the error message and configure your authentication provider with it.
Note: when configuring these redirect URIs in Azure Entra ID, make sure to add them for the Mobile and desktop applications platform
Once the configuration in the authentication provider is done, go back to Copilot Studio and try again. The login should succeed this time, and you can click on Add and configure