ACADEMY - My Learning DOCS & GUIDESAPIPARTNERS FAQ
User Guide
indigitall

MCP Integration Guide

Connecting indigitall Statistics to Claude, Copilot, and Gemini

This guide explains how to connect your indigitall statistics and analytics to Large Language Models (LLMs) like Anthropic Claude, Microsoft Copilot, and Google Gemini using the Model Context Protocol (MCP).

Anthropic Claude

Setting up the indigitall MCP connector in Claude requires a one-time administrator configuration, after which team members can easily link their individual accounts.

Administrator Setup

  1. Open the Claude app, navigate to the main menu, and select Company Settings.

  2. Click on the Connectors tab.

  3. Select Add Custom Web Connector.

  4. In the configuration dialog, fill in the following details:

    • Name: Enter a clear identifier for your team (e.g., indigitall or indigitall Statistics).

    • URL: Enter your specific MCP endpoint: https://mcp.XXX.indigitall.com/mcp
      (Note: Replace XXX with your console's designated cluster based on your geographical region or usage date, such as am1, eu1, eu2, or eu3).

  5. Save the configuration.

Team Member Connection Process

Once the administrator has deployed the custom connector, team members can enable it by following these steps:

  1. Navigate to the Connectors section in your Claude app.

  2. Locate the indigitall connector under the available list and click Connect.

  3. A browser pop-up window will appear prompting you to log in. Enter your indigitall console credentials (Email and Password).

  4. For enhanced security, enter the Verification Code sent to your registered email address.

    verification-code

  5. Once authenticated, the browser will display: "Taking you back to the desktop app. You can close this tab."

  6. Return to your Claude app and verify that the connector status is listed as Connected under the Web category.

    Connected_web


Usage Details

When interacting with Claude regarding your indigitall analytics, please keep the following guidelines in mind:

  • Mandatory Use of IDs: You must always query data using specific Project IDs and Journey IDs. The system does not recognize user-friendly or display names. Since journey and campaign directories cannot be listed directly via MCP at this time, you must retrieve these IDs directly from your indigitall console first.
  • Switching Projects: To change or query a different project, you must initiate a completely new conversation thread in Claude.
  • Data Availability & Latency: Analytics are not updated in real-time. The accessible data range covers from yesterday up to the previous 90 days.
  • Result Validation: As with any generative AI system, the LLM may occasionally hallucinate or make errors regarding specific metrics or channels. Always cross-verify critical statistics against the official console.
  • Permissions: The data accessible via the MCP connection strictly matches your console user role; you will only be able to view and query projects you already have permission to access.

Microsoft Copilot & Google Gemini

To integrate indigitall statistics with Microsoft Copilot or Google Gemini via the Model Context Protocol (MCP), add the following JSON configuration snippet to your respective environment configuration settings:

{
  "servers": {
    "indigitall-mcp": {
      "type": "http",
        "url": "https://mcp.xxx.indigitall.com/mcp",
        "headers": {
          "Authorization": "ServerKey <valid-server-key>",
          "X-Application-Id": "12345" 
        }  
     } 
  } 
}
{ 
  "servers": { 
    "indigitall-mcp": {
      "httpUrl": "https://mcp.xxx.indigitall.com/mcp", 
    } 
  } 
}