Configure the Docebo MCP Server

Overview

Docebo hosts an MCP server inside your own Docebo platform, exposing learner-facing tools for courses, enrollments, and learning content. Each MCP server has its own URL and its own set of enabled tools — a built-in Learner server ships with the platform, and Superadmins can create additional servers scoped to specific tools. Access is authorized through OAuth via an OAuth2 app you register in Docebo.

1. Configure Docebo

You need Superadmin access in Docebo for all three steps.

If it isn’t already active, activate the API and SSO app from Apps & Features — it’s listed under the Docebo Additional Features tab.
Open the Admin menu (gear icon) and go to API and SSO → Manage → API Credentials, then select Add OAuth2 App. Give it a name and description that your users will recognize on the consent screen (for example Dtwo Gateway), set the Client ID to a unique value (for example dtwo_gateway), and set the Redirect URL to your gateway’s OAuth callback URL — found in the Overview tab for your gateway in the Dtwo UI. The Client Secret is generated for you. Leave the grant types at Authorization code + implicit grant, select Confirm, then activate the app with the checkmark in its row.
Open the Navigation menu → Configuration (spanner icon) → Artificial intelligence, find the Docebo MCP server card, and select Configure. Use the built-in Learner server, or select Create server to expose a different set of tools. Make sure the server’s status is Enabled, then copy its URL.

2. Add the MCP server to your gateway config

Go to your gateway in the Dtwo UI and open Configuration → Advanced. In the mcp_servers section add the following entry:

  - name: docebo
    description: "Docebo's hosted MCP server for courses, enrollments, and learning content."
    url: https://<DOCEBO_DOMAIN>/mcp/servers/<SERVER_PATH>/http
    transport_type: streamablehttp
    authentication:
      type: oauth
      grant_type: authorization_code
      client_id: "<CLIENT_ID>"
      client_secret: "<CLIENT_SECRET>"
      authorization_url: "https://<DOCEBO_DOMAIN>/oauth2/authorize"
      token_url: "https://<DOCEBO_DOMAIN>/oauth2/token"
      redirect_uri: "<CALLBACK_URL>"

Replace the placeholder values:

<DOCEBO_DOMAIN> — your Docebo platform’s domain (for example yourcompany.docebosaas.com), or your custom domain if you use one.
<SERVER_PATH> — the path of the MCP server you enabled in step 1, taken from the server URL Docebo shows on the Docebo MCP server page.
<CLIENT_ID> and <CLIENT_SECRET> — come from the OAuth2 app you created in step 1.
<CALLBACK_URL> — the same Redirect URL you set in step 1, found in the Overview tab for your gateway in the Dtwo UI.

3. Deploy and verify

Save the configuration and deploy the gateway.

Then, in your AI client, ask it to authorize Docebo via the gateway. This opens the Docebo login screen — sign in as the user whose permissions the agent should inherit, and approve the consent prompt. Once authorized, confirm the server’s tools appear and run a quick call to make sure the connection works.

If the tools don’t appear after you authorize, refresh the tool list in your AI client — some clients don’t pick it up automatically.