Skip to content

How-to guide

Configuration

Connect your AI client to the platform's MCP server to manage your data using natural language.

3 min

Overview

Connect your AI client to the platform's MCP server to manage your data using natural language.

Before You Begin

  1. Create a key in the New MCP key card on the API Keys page
  2. Have an MCP client installed (Claude Desktop, VS Code, Cursor, Claude Code, or n8n)
  3. Know your Workspace ID for manual configuration (visible in your workspace settings)

Steps

The server accepts MCP 2026-07-28 and the legacy versions 2025-11-25, 2025-06-18, and 2025-03-26 at the same URL. A recent client with automatic negotiation can use server/discover; legacy clients continue with initialize. Let your client construct the protocol headers for each request.

Right after key creation, the UI offers a configuration you can copy for Claude Code, Cursor, or Devin. It uses the active workspace and the environment's MCP URL. The examples below are for other clients or manual configuration.

Claude Desktop

Open the claude_desktop_config.json file and add:

{
  "mcpServers": {
    "ontologie": {
      "url": "https://api.ontologie-growthsystemes.com/api/mcp",
      "headers": {
        "X-API-Key": "df_VOTRE_CLE_MCP",
        "x-workspace-id": "VOTRE_WORKSPACE_ID"
      }
    }
  }
}

VS Code (Copilot MCP Extension)

Add to your settings.json:

{
  "mcp": {
    "servers": {
      "ontologie": {
        "url": "https://api.ontologie-growthsystemes.com/api/mcp",
        "headers": {
          "X-API-Key": "df_VOTRE_CLE_MCP",
          "x-workspace-id": "VOTRE_WORKSPACE_ID"
        }
      }
    }
  }
}

Cursor

Open Settings > MCP Servers and add:

{
  "ontologie": {
    "url": "https://api.ontologie-growthsystemes.com/api/mcp",
    "headers": {
      "X-API-Key": "df_VOTRE_CLE_MCP",
      "x-workspace-id": "VOTRE_WORKSPACE_ID"
    }
  }
}

Claude Code

From your terminal:

claude mcp add ontologie \
  --transport http \
  https://api.ontologie-growthsystemes.com/api/mcp \
  --header "X-API-Key: df_VOTRE_CLE_MCP" \
  --header "x-workspace-id: VOTRE_WORKSPACE_ID"

Or add to your .mcp.json file:

{
  "mcpServers": {
    "ontologie": {
      "type": "http",
      "url": "https://api.ontologie-growthsystemes.com/api/mcp",
      "headers": {
        "X-API-Key": "df_VOTRE_CLE_MCP",
        "x-workspace-id": "VOTRE_WORKSPACE_ID"
      }
    }
  }
}

n8n

In n8n, configure an MCP Client node with:

  • URL: https://api.ontologie-growthsystemes.com/api/mcp
  • Authentication: Credentials of type "Header Auth"
    • Header X-API-Key with the composite value: YOUR_MCP_KEY:YOUR_WORKSPACE_ID
n8n Format
n8n only supports a single authentication header. The MCP server accepts the composite format api_key:workspace_id in the X-API-Key header.
Security Tip
Store your API key in an environment variable rather than in plain text in the configuration file.

Expected Result

Your AI client is connected to the platform. You can query your data, launch workflows, and search documents from your AI interface.

Limitations / Common Errors

SymptomProbable CauseSolution
401 UnauthorizedInvalid, expired, or revoked API keyCreate a new key in the New MCP key card
403 ForbiddenMissing scopeAdd the required scopes to your key
-32020 Header mismatchModern MCP header differs from the requestUpdate your MCP client; do not set these headers manually
-32022 Unsupported protocol versionRequested version is not supportedSelect a version from supportedVersions or enable automatic negotiation
No tools visibleWrong Workspace IDVerify the identifier in the settings
Connection droppedNetwork timeoutRestart the connection in the client

Need Help?

Contact us: Support and Contact.

Verify the connection and effective surface

Prefer the configuration offered after creating an MCP key in the application: it uses the active environment and workspace. Remote HTTP support depends on the client and version; check its connection mode before copying an example configuration.

After connecting, list available tools. Compare them with the key's profile and scopes, then read a known record. The full product catalogue does not necessarily describe the surface exposed to this key.

Missing tools may be filtered by profile, publication or permissions. Do not bypass filtering using internal routes. See Knowledge-base tools for documents and Action preparation for action contracts and controls.

Did this page help you achieve your goal?