eSagu MCP setup – Step-by-step guides for ChatGPT, Mistral, Open WebUI …

This guide describes how to integrate the eSagu Remote MCP Server into multiple AI platforms such as ChatGPT, Claude, Mistral, Open WebUI (and similarly Claude) using a unified OAuth-based setup. The goal is to make eSagu services available directly from the chat across platforms, without separate API keys or platform-specific configurations.

The Model Context Protocol (MCP) acts as a standardized interface that allows AI models to securely and structurally access external services. Through MCP, the AI can call well-defined eSagu functions and work with them in a context-aware manner. Authentication is handled via OAuth, ensuring access is user-specific and restricted to the authorized services.

The eSagu Remote MCP Server supports multiple eSagu services, including RePricing for Amazon, RePricing for eBay, RePricing for Kaufland, Lost & Found for Amazon FBA, and the eSagu HelpDesk. Depending on which service is authorized during the OAuth process, different context-dependent tools become available to the AI. This ensures that the AI only has access to the functions and data relevant to the selected service.

Once connected, the eSagu MCP Server can be activated within the respective platform and used directly in chat to, for example, list items, retrieve repricing information, handle Lost & Found cases, or create and manage support requests via the HelpDesk.

ChatGPT

1. Click the profile area in the bottom-left and open Settings.

2. Select Apps in the left sidebar.

3. Open Advanced settings at the bottom.

4. Enable Developer mode (Beta) (note: memory is disabled in this mode).

5. Go back to Apps and click Create app in the top-right.

6. In the New App dialog, enter:

   • Name: e.g. eSagu
   • MCP Server URL: https://api.esagu.de/mcp
   • Authentication: OAuth Optional: set icon/description. Confirm the warning and click Create.
     Here your can download our App-Icon

7. In the OAuth window, open Select Service, choose the service, enter your password, and click Authorize access.

8. In the app details, verify that “… is now connected” appears and the URL is correct.

9. In a chat, click + → More → eSagu to activate the app.

10. Send a request (e.g., “List my items.”).

Claude

1. Open the profile menu in the bottom-left corner and select Settings.

2. Navigate to Connectors in the left sidebar.

3. Click Add custom connector.

4. Enter the following details:

   • Name: eSagu MCP
   • Connector URL: https://api.esagu.de/mcp

   Confirm with Add.

5. In the OAuth authorization screen:

   • Open Select Service
   • Choose the desired eSagu service
   • Enter your password
   • Click Authorize access

6. After successful authorization, the connector appears in the list. Click Configure.

7. Set tool permissions:

   • Read-only tools → Always allow
   • Write/delete tools → Needs approval

The following setup is recommended because it provides a balanced trade-off between usability and control:

• Read-only tools → Always allow Read-only actions (e.g. listing data, fetching information, status checks) can run without confirmation. This enables smooth, fast chat interactions and is safe since no changes are made.

• Write/delete tools → Needs approval Actions that modify or delete data require explicit user approval. This ensures full control over critical operations.

This configuration is not mandatory. Depending on your use case, security requirements, or personal preference, permissions can be adjusted, for example:

• setting everything to Needs approval for maximum control
• or using Always allow for highly automated workflows in trusted environments

8. The connector is now active. In any new chat, Claude can automatically use eSagu tools when appropriate.

Mistral

1. Click Intelligence (Beta) in the left navigation.

2. Select Connectors.

3. Click Add Connector in the top-right corner.

4. In the dialog, select Custom MCP Connector.

5. Fill in the following fields:

   • Name: eSagu
   • Connector Server: https://api.esagu.de/mcp
   • Description (optional): eSagu Repricing & more …
   • Authentication Method: OAuth2.1

6. In the OAuth window, open Select Service, choose the service, enter your password, and click Authorize access.

7. Confirm with Create. The connector will now appear as Connected.

8. Enable tools that you are planning to use.

9. Open a new chat or use an existing chat to activate the connector.

10. Type / in the input field and select eSagu.

11. Send a request (e.g. “List my items on second page.”).

The following setup is recommended because it provides a balanced trade-off between usability and control:

• Read-only tools → Always allow Read-only actions (e.g. listing data, fetching information, status checks) can run without confirmation. This enables smooth, fast chat interactions and is safe since no changes are made.

• Write/delete tools → Needs approval Actions that modify or delete data require explicit user approval. This ensures full control over critical operations.

This configuration is not mandatory. Depending on your use case, security requirements, or personal preference, permissions can be adjusted, for example:

• setting everything to Needs approval for maximum control
• or using Always allow for highly automated workflows in trusted environments

Open WebUI

1. Open Admin Panel from the bottom-left menu.

2. Go to Settings → External Tools.

3. Click + (top-right) to add a new connection.
4. Configure the connection:
   • Type: MCP Streamable HTTP
   • URL: https://api.esagu.de/mcp
   • Auth: OAuth 2.1

5. Click Register Client. The OAuth authorization window opens.

6. In Select Service, choose the service, enter your password, click Authorize access.

7. Verify the status changes to Registered.

8. Click Save.

9. Open a new or existing chat, enable tools via the tool icon next to the input field, Select eSagu.

10. Send a request, e.g. (List all items with "Einstein" in the name)

Disclaimer MCP is currently in beta across all supported platforms. The Model Context Protocol itself is still relatively new (introduced in November 2024) and is under continuous development and extension. As a result, platform user interfaces may change at any time, and the MCP protocol is subject to ongoing updates and enhancements.