Configuring the Docebo MCP server

Introduction

The Model Context Protocol (MCP) server allows you to seamlessly integrate Docebo with enterprise AI assistants (MCP clients) like ChatGPT, Claude, Microsoft Copilot Studio, and Gemini Enterprise. Once the integration is configured, users in your organization can interact with Docebo content and data using natural language, directly inside the AI tools they already use, without navigating through the LMS.

Learn more on how to use the Docebo MCP server (opens in a new tab).

This article is intended for Docebo Superadmins and describes how to complete the one-time configuration required to activate the integration.

Requirements and limitations

• A Docebo Superadmin must complete the initial configuration in Docebo.

• The administrator of the target MCP client (for example, ChatGPT, Claude, Microsoft Copilot Studio, or Gemini Enterprise) must have the necessary privileges to add and configure connectors in that platform.

• The current Docebo OAuth flow does not automatically redirect users to the SSO (Single Sign-On) page. Users must already be actively logged into Docebo in their browser before completing the OAuth authentication in the MCP client. If your organization relies strictly on SSO, users may not have direct Docebo credentials and will be unable to complete the flow. This limitation is expected to be resolved in future releases.

• The current Docebo OAuth flow includes a scope check that could prevent non-superadmins from connecting the Docebo MCP Server to some MCP clients. However, following the step-by-step instructions provided in this article ensures this limitation does not prevent usage with tested clients like ChatGPT, Claude, Microsoft Copilot Studio, and Gemini Enterprise. This limitation is expected to be resolved in future releases.

• If your Docebo platform uses a custom domain, you must use it in place of your original domain when configuring the MCP Server URLs. Please note that while the configuration process for ChatGPT, Microsoft Copilot Studio, and Gemini Enterprise allows you to successfully set up the integration using a custom domain, the configuration for Claude currently does not. This limitation is expected to be resolved in future releases.

Configuring the Docebo MCP server

Configuring the Docebo MCP server consists of three steps:

1. Configure an OAuth2 application in Docebo.

2. Configure an MCP server.

3. Connect the MCP server to your AI assistant.

Once completed, users can authenticate with Docebo and interact with the tools exposed by the MCP server.

Step 1: Create an OAuth2 application in Docebo

To allow secure communication between your AI assistant and Docebo, a Superadmin must register the AI assistant as an OAuth2 application within the platform.

Whenever the configuration steps ask you to enter https://[docebo-instance-name], use your platform's domain (e.g., https://yourcompany.docebosaas.com). If your platform uses a custom domain, you must enter your custom domain.

1. Log into your Docebo platform as a Superadmin.

2. Follow the instructions in the Activating and managing the API and SSO app article to create a new OAuth2 application.

3. During setup, use the following configuration:

   • App Name: Docebo MCP Server

   • App Description: App to connect Docebo MCP Server

   • Client ID: docebo_mcp_server

   • Client Secret: automatically generated

   • Redirect URI: the value depends on your MCP client. Use the values listed below for the most common clients. For other clients, refer to their documentation.

     • ChatGPT: the Redirect URI is generated in Step 2. Enter a temporary placeholder for now and return to update this field once ChatGPT provides the URI.

     • Claude: https://claude.ai/api/mcp/auth_callback

     • Microsoft Copilot Studio: the Redirect URI is generated in Step 2. Enter a temporary placeholder for now and return to update this field once Copilot Studio provides the URI.

     • Gemini Enterprise: https://vertexaisearch.cloud.google.com/oauth-redirect

   • Advanced settings: keep the defaults, with grant types set to Authorization code + implicit grant.

The OAuth2 application name and description are displayed to end users when they authorize the connection between their AI assistant and Docebo. Choose values that are recognizable within your organization and clearly identify the purpose of the integration.

Once the application is created, safely store the Client ID and Client Secret. You will need these values in Step 2.

Step 2: Configure an MCP server

After creating the OAuth2 application, configure an MCP server in Docebo.

1. Log in as a Superadmin.

2. Open the Navigation menu.

3. Find the Configuration menu (spanner icon).

4. Select Artificial intelligence.

5. Locate the Docebo MCP server card.

6. Click Configure.

An MCP server exposes a specific set of Docebo tools to external AI assistants through a unique URL.

The MCP configurator allows you to manage the MCP servers available in your platform.

By default, Docebo provides a built-in Learner server that exposes learner-focused tools. This server cannot be edited or deleted. You can use this server as is, or create additional servers for specific use cases.

To create a custom server:

1. In the Docebo MCP server page, click Create server.

2. Enter a Server name and Server path.

3. Select the tools to expose through the server.

4. Click Create server at the bottom of the panel.

Each MCP server has its own URL and tool configuration. Before proceeding, ensure that the server you want to use is enabled, then copy its URL.

You will use this URL when configuring your AI assistant in the next step.

Example URL: https://[docebo-instance-name]/mcp/servers/[server-path]/http

If your platform uses a custom domain, use the custom domain version of the URL.

Step 3: Connect the MCP client

The administrator of your enterprise AI assistant must connect the Docebo MCP server.

The steps below describe the setup process for the most common clients. Note that these interfaces change frequently. If the steps no longer match your client's current interface, refer to the client's official documentation: ChatGPT (opens in a new tab), Claude (opens in a new tab), Microsoft Copilot Studio (opens in a new tab), Gemini Enterprise (opens in a new tab).

Before proceeding:

• Ensure that an OAuth2 application has been configured.

• Ensure that the MCP server is enabled.

• Copy the MCP server URL from the Docebo MCP server page.

ChatGPT (Enterprise / Team)

1. Log into ChatGPT with administrative or workspace owner privileges.

2. Navigate to Workspace Settings > Apps.

3. Click Create in the top-right corner.

4. Configure the connection with the following details:

   1. Name: Docebo (You can choose a name that best fits your organization. This name will be visible to final users, so we suggest using the same name they are used to seeing for your Docebo platform.)

   2. MCP Server URL: https://[docebo-instance-name]/mcp/servers/[server-path]/http

   3. Authentication Type: OAuth

      • OAuth advanced settings:

        • Client ID: paste the Client ID from Step 1

        • Client Secret: paste the Client Secret from Step 1

      • Scopes:

        • Disable the api scope

      • OAuth endpoints:

        • Auth URL: https://[docebo-instance-name]/oauth2/authorize

        • Token URL: https://[docebo-instance-name]/oauth2/token

        • Registration URL: leave this field empty

        • Authorization server base: https://[docebo-instance-name]

        • Resource: https://[docebo-instance-name]

      • Select I understand and want to continue

5. Click Create.

6. ChatGPT will generate a Callback URL. Copy this URL, return to your Docebo OAuth2 app settings from Step 1, paste it into the Redirect URIs field, and save.

7. Enable the connector for the target users.

Claude (Enterprise / Team)

1. Log into Claude with administrative privileges.

2. Navigate to Organizational Settings > Connectors.

3. Click Add custom connector at the bottom of the page.

4. Configure the connection:

   • Name: Docebo (You can choose a name that best fits your organization. This name will be visible to final users, so we suggest using the same name they are used to seeing for your Docebo platform.)

   • Remote MCP Server URL: https://[docebo-instance-name]/mcp/servers/[server-path]/http

   • Client ID: paste the Client ID from Step 1

   • Client Secret: paste the Client Secret from Step 1

5. Click Add.

6. Enable the connector for the target users.

Microsoft Copilot (via Copilot Studio)

1. Log into Microsoft Copilot Studio as an administrator or environment maker.

2. Select your desired agent, then navigate to the Tools section.

3. Click Add a tool, then select the Model Context Protocol filter tab.

4. Click New tool to add a new MCP server.

5. Provide the following details:

   • Server Name: Docebo (You can choose a name that best fits your organization. This name will be visible to final users, so we suggest using the same name they are used to seeing for your Docebo platform.)

   • Server URL: https://[docebo-instance-name]/mcp/servers/[server-path]/http

   • Authentication: select OAuth 2.0, type Manual

   • Client ID: paste the Client ID from Step 1

   • Client Secret: paste the Client Secret from Step 1

   • Authorization URL: https://[docebo-instance-name]/oauth2/authorize

   • Token URL template: https://[docebo-instance-name]/oauth2/token

   • Refresh URL: https://[docebo-instance-name]/oauth2/token

   • Scopes: (Leave this field empty)

6. Click Create.

7. Copilot Studio will generate a Redirect URI. Copy this URL, return to your Docebo OAuth2 app settings from Step 1, paste it into the Redirect URIs field, and save.

8. Enable the connector for the target users.

Gemini Enterprise

The Gemini Enterprise configuration interface changes frequently. The values below are always required; for the full, current step-by-step instructions, refer to Google's "Set up a custom MCP server" documentation (opens in a new tab).

When prompted, provide the following details:

• MCP Server URL: https://[docebo-instance-name]/mcp/servers/[server-path]/http

• Authorization URL: https://[docebo-instance-name]/oauth2/authorize

• Token URL: https://[docebo-instance-name]/oauth2/token

• Client ID: paste the Client ID from Step 1

• Client Secret: paste the Client Secret from Step 1

Once the data store is created, enable the Docebo tools for the target users as described in Google's documentation.

End-user authentication

Once the administrator configuration is complete, the integration is ready for end users. Upon first use, users must add the Docebo connector from the list of enterprise connectors made available by their MCP client administrators. After selecting the Docebo connector, they will click the authorization link to initiate the OAuth flow, securely linking their AI assistant profile to their Docebo user account.

Best practice for SSO environments

Advise your users to open a new browser tab, log into Docebo via their normal SSO route, and only then click the authorization link inside the MCP client.

Once this one-time authentication is complete, users can access Docebo capabilities directly from their AI assistant going forward.

Available tools

The tools available to users depend on the MCP server they connect to and the tools enabled by the administrator.

The built-in Learner server provides access to learner-focused tools, while custom MCP servers can expose additional capabilities for different personas and use cases.

For a complete list of available tools, including descriptions, permissions, and example prompts, see the Supported MCP tools article.

Managing existing servers

Enabling or disabling a server

Each MCP server can be individually enabled or disabled. Disabling a server prevents AI assistants from connecting to it without removing its configuration.

To change a server's status:

1. In the Docebo MCP server page, locate the server you want to manage.

2. Click the status dropdown (showing Enabled or Disabled) in the server’s row.

3. Select Enabled or Disabled as needed.

The change takes effect immediately. Before proceeding to Step 3, ensure the server you intend to use is set to Enabled.

Editing or deleting a custom server

To edit or delete a custom server:

1. In the Docebo MCP server page, locate the server you want to manage.

2. Click the ellipsis button in the server’s row.

3. Select one of the following options:

   1. Edit server: Opens the server configuration panel, where you can update the server name, server path, and the tools exposed through the server. Click Save to apply your changes.

   2. Delete: Permanently removes the custom server. This action cannot be undone.

Please note

The built-in Learner server cannot be edited or deleted. The ellipsis button is only available for custom servers.