Skip to main content

MCP Server Connection

Microsoft Azure

App Registration #1

Open URL: https://portal.azure.com/#home.

  1. Click on App registrations
  2. Click on "New registration".
NKkCQz9icqKLyder-drawing-8-1780315123.png

Name

Please use "DeDeSales KI MCP API"

Supported account types

Usually, "Accounts in this organisational directory only - ..." with your client name should be selected here. If access to multiple clients is required, you must configure this accordingly.

Now click on "Register"

Summary

Application ID URI

Enter the URL provided by us here, for example: https://demo4.ki.dedenet.dedesales.de/mcp.

Token Configuration

Click on "Add optional claim", then select Access and "email", "preferred_username" and "upn".

image.png

The screenshot shows only an excerpt. The required selections are listed above in the text.

Then click "Add". You must confirm the subsequent message (checkbox for Enable the Microsoft Graph permission "email").

API permissions

We require the standard permissions that are already created automatically:

  1. Microsoft Graph" User.Read permission.

Then click "Grant admin consent for "your tenant name".

Make an API available

Click on "Add scope" and enter the following:

  1. Scope name: access_as_user
  2. Who can consent: Only administrators
  3. Admin consent display name: DeDeSales MCP Server
  4. Admin consent description: This grants access to the DeDeSales MCP Server.

Then click "Add scope"

Application ID (Client)

You can find the Application ID by clicking on Summary. Copy the Application ID that appears, as we will need it. 

App Registration #2

Name

Please use "DeDeSales KI MCP Client"

Supported account types

Usually, "Accounts in this organisational directory only - ..." with your client name should be selected here. If access to multiple clients is required, you must configure this accordingly.

Set redirect URIs

The platform to select is "Mobile and desktop applications".

The redirect URIs must be entered depending on your chosen KI provider.

KI Provider Redirect URI
Claude Desktop / Claude.ai https://claude.ai/api/mcp/auth_callback

Now click on "Register"

Authentication (Preview)

Click on Settings and enable "Allow public client flows".

MUEaTMsqnBnB5ldL-drawing-8-1786965784.png

API permissions

We require the standard permissions that are already created automatically:

  1. Microsoft Graph" User.Read permission.
  2. DeDeSales KI MCP API
    1. You find this by clicking on Add permission.
    2. Then select "APIs my organisation uses".
    3. Type "DeDeSales KI MCP API".
    4. Select the entry (Note! It can take 15-30 minutes until this entry is available, as it was only recently created by you)
    5. Select "Delegated permissions"
    6. Under Select permissions, choose "access_as_user".
    7. Click "Add permissions".

Then click "Grant admin consent for "your tenant name".

Application ID (Client)

You can find the Application ID by clicking on Summary. Copy the Application ID that appears, as we will need it. 

From your setup we need

  1. Your TenantId

DeDeSales Backend

In the DeDeSales backend you must now do the following:

  1. Under Administration / User select the users who should have MCP access. For these users, activate the checkbox "Enable MCP Server".
  2. Under Basic configuration / Employee select the corresponding employee for this user. If there is no match, you must create one. This employee controls which customer data access is granted. In the dropdown "User" select the user who was previously enabled for MCP access under "Administration / User".

KI Provider

The configuration of the KI provider can only be done once we have received the data from the section "From your facility we need" from you and have completed the configuration.

Anthropic (Claude Desktop)

Add a custom connector in Claude Desktop.

  1. Name: DeDeSales MCP Server
  2. Remote MCP Server URL: https://<the domain provided by us>/mcp
  3. OAuth Client ID: The Application ID from "DeDeSales KI MCP Client"