Set up ENLYZE MCP

Connect your AI assistant to ENLYZE MCP and start querying production data.

In this guide, you'll connect your AI assistant to ENLYZE MCP. Select your assistant from the tabs below.

Prerequisites

• ENLYZE account with active access to the ENLYZE Manufacturing Data Platform

• One of the supported AI assistants: Microsoft Copilot (with Copilot Studio), Claude Desktop, Claude Code, Cursor, VS Code, OpenAI Codex, or another MCP-compatible client

Setup

Select your AI assistant from the tabs below and follow the instructions to connect it to ENLYZE MCP.

Microsoft Copilot

Microsoft Copilot is not to be confused with the Co-Pilot of the ENLYZE Platform.

Step 1: Get a Copilot Studio license

To connect Microsoft Copilot to an external service like ENLYZE MCP, a Copilot Studio license is required. A Microsoft 365 Copilot license is not sufficient. The Copilot Studio license is purchased for the tenant (typically the whole company).

Step 2: Assign a Copilot Studio user license

The people who configure the agent also need a Copilot Studio user license. It is free and gives individual users access to Copilot Studio. It is only needed for configuration, not for usage: every user with a Microsoft 365 Copilot license can use the finished agent.

Step 3: Enable the new Copilot Studio version

Open Copilot Studio in your browser. Only the new version of Copilot Studio supports the full feature set of ENLYZE MCP. It is currently not enabled automatically: turn it on with the New experience toggle in the top-right corner. The interface should then look like this:

Copilot Studio with the new version enabled

Step 4: Create an agent

Click Agents in the left sidebar.

The Agents entry in the left sidebar

Then click New agent to start creating one:

The agent overview with the New agent button

Step 5: Add ENLYZE MCP as a tool

Add a new tool in the Tools section:

The Tools section in the agent configuration

Click Add and select Model Context Protocol (MCP):

Selecting Model Context Protocol (MCP)

Then enter the server details:

Server Name

ENLYZE MCP

Description

Access to ENLYZE production data: sites, machines, OEE, downtimes, and production runs.

Server URL

https://app.enlyze.com/api/mcp

Fully completed server details

Then click Add. The connector is created.

Step 6: Configure the connection

Next to Connection, click the Not connected dropdown:

The Not connected dropdown next to Connection

Then select Create new connection:

The Create new connection option

Then click Create. A name for the connection is not required:

Creating the connection, the display name can stay empty

Step 7: Authenticate

While the connection is being set up, you'll be redirected to the ENLYZE login page. Select the matching organization there and allow access:

Select your organization and allow access

Afterwards, the connection appears with a green checkmark:

The connection is established

Click Add. ENLYZE MCP is now available to the agent and appears under Tools:

ENLYZE MCP in the agent's tool list

Step 8: Test the agent

Switch to the Preview tab at the top:

The Preview tab in the agent view

There you'll see a familiar chat interface and can test the agent. Example prompts:

Show me a list of production sites.

How did the OEE of machine XYZ develop over the last X days? What stands out?

Step 9: Publish the agent

Publishing puts the agent into production so your colleagues can use it too. To do so, click Publish in the top-right corner:

The Publish button in the top-right corner

To make the agent available to all users in Microsoft 365 Copilot, you also need to adjust the publish details:

1. Click the arrow-down button next to Publish.

2. Select Teams + Microsoft 365 in the channel list.

3. Under Turn on Microsoft 365, check Make agent available in Microsoft 365 Copilot.

4. Click Save and publish.

The Teams + Microsoft 365 channel with Make agent available in Microsoft 365 Copilot enabled

Microsoft Copilot is now connected to ENLYZE. Every user with a Microsoft 365 Copilot license can use the published agent.

Claude Desktop

Step 1: Open connector settings

In Claude Desktop, open Customize → Connectors, click the + button, and then select Add custom connector.

Step 2: Add ENLYZE MCP

Enter a name (for example ENLYZE) and the server URL, then click Add:

• URL: https://app.enlyze.com/api/mcp

You don't need to fill in an OAuth Client ID or Secret under Advanced settings. Claude runs the OAuth flow for you.

Custom connectors reach your MCP server from Anthropic's cloud, not from your computer, so the server must be reachable over the public internet. app.enlyze.com is, so this works out of the box.

Step 3: Authenticate

The first time your AI assistant uses ENLYZE MCP, you'll be automatically redirected to a login screen. Follow these steps:

1. Sign in: Log in with your ENLYZE account

2. Grant permission: The consent screen asks you to allow your AI assistant to access your ENLYZE account and its production data

3. Confirm: Click Approve or Accept to allow access

Your client saves the OAuth2 token after granting permission. You won't need to log in again until the token expires. When it does, you'll be prompted to sign in again on your next request.

Claude Desktop is now connected and will load available tools on your next chat.

Alternative: local bridge via claude_desktop_config.json

claude_desktop_config.json only supports local (stdio) servers, so a { "type": "http", "url": … } entry won't work there. If you prefer a config-file setup, bridge the remote server with mcp-remote (requires Node.js):

{
  "mcpServers": {
    "enlyze": {
      "command": "npx",
      "args": ["mcp-remote", "https://app.enlyze.com/api/mcp"]
    }
  }
}

Claude Code

Step 1: Add ENLYZE MCP

Run the following command in your terminal:

claude mcp add enlyze --transport=http https://app.enlyze.com/api/mcp

Step 2: Start Claude Code and authenticate

Enter Claude Code:

claude

Once inside Claude Code, type the /mcp command to view available MCP servers. Claude Code will automatically redirect you to the OAuth2 consent screen:

1. Sign in: Log in with your ENLYZE account

2. Grant permission: Review the access request and allow your AI assistant to access your ENLYZE account and its production data

3. Confirm: Click Approve to complete authentication

Your token is stored locally. When it expires, you'll be prompted to sign in again on your next request.

Claude Code is now connected. Use /mcp to see ENLYZE tools in your next session.

Cursor

Step 1: Add ENLYZE MCP

Based on your preference, choose one of the following options to add ENLYZE MCP to your Cursor setup:

Option A: Workspace MCP server

A workspace MCP server is only available for the project it is configured in. If it does not already exist, create a file under .cursor/mcp.json in your project directory. Cursor auto-detects a remote server from the url, so no type field is needed:

{
  "mcpServers": {
    "enlyze": {
      "url": "https://app.enlyze.com/api/mcp"
    }
  }
}

Option B: Global MCP server

To make ENLYZE MCP available across all projects, open Cursor settings with Cmd+Shift+J / Ctrl+Shift+J and select Tools & MCP → Home. Add the same configuration as in Option A (Cursor stores it in ~/.cursor/mcp.json).

Step 2: Restart Cursor

Close Cursor and open it again to load the MCP connection.

Step 3: Authenticate

The first time your AI assistant uses ENLYZE MCP, you'll be automatically redirected to a login screen. Follow these steps:

1. Sign in: Log in with your ENLYZE account

2. Grant permission: The consent screen asks you to allow your AI assistant to access your ENLYZE account and its production data

3. Confirm: Click Approve or Accept to allow access

Your client saves the OAuth2 token after granting permission. You won't need to log in again until the token expires. When it does, you'll be prompted to sign in again on your next request.

Cursor is now connected. Available tools should appear in your next chat.

VS Code

Step 1: Enable GitHub Copilot in VS Code

Make sure you have the GitHub Copilot extension installed and logged in with your GitHub account.

Step 2: Add ENLYZE MCP

Depending on your VS Code version and Copilot Agent support:

Option A: Workspace-scoped configuration (.vscode/mcp.json)

Create a file .vscode/mcp.json in your project directory:

{
  "servers": {
    "enlyze": {
      "type": "http",
      "url": "https://app.enlyze.com/api/mcp"
    }
  }
}

Option B: User configuration (mcp.json)

Run the MCP: Open User Configuration command (Cmd+Shift+P / Ctrl+Shift+P) to open your user mcp.json, then add the server using the same shape as Option A:

{
  "servers": {
    "enlyze": {
      "type": "http",
      "url": "https://app.enlyze.com/api/mcp"
    }
  }
}

Step 3: Restart VS Code

Close VS Code and open it again. Open the Copilot Chat view (Ctrl+Cmd+I on macOS, Ctrl+Alt+I on Windows/Linux). MCP tools should now be available.

Step 4: Authenticate

The first time your AI assistant uses ENLYZE MCP, you'll be automatically redirected to a login screen. Follow these steps:

1. Sign in: Log in with your ENLYZE account

2. Grant permission: The consent screen asks you to allow your AI assistant to access your ENLYZE account and its production data

3. Confirm: Click Approve or Accept to allow access

Your client saves the OAuth2 token after granting permission. You won't need to log in again until the token expires. When it does, you'll be prompted to sign in again on your next request.

VS Code Copilot is now connected to ENLYZE.

Codex

Step 1: Install Codex CLI

Make sure you have the Codex CLI installed. See the Codex documentation for installation instructions.

Step 2: Add ENLYZE MCP

Run the following command to register ENLYZE MCP:

codex mcp add enlyze --url https://app.enlyze.com/api/mcp

Alternatively, add it directly to ~/.codex/config.toml:

[mcp_servers.enlyze]
url = "https://app.enlyze.com/api/mcp"

Step 3: Authenticate

Run the login command to complete the OAuth2 flow:

codex mcp login enlyze

This opens a browser window where you sign in with your ENLYZE account and grant access. Your token is stored locally. When it expires, you'll be prompted to sign in again on your next request.

Codex is now connected. The ENLYZE tools are available in your next Codex session.

Other MCP clients

Any MCP-compatible client (e.g., custom applications, agent frameworks) can connect to ENLYZE MCP through the same HTTP interface.

Configuration

Ensure your client framework supports these parameters:

• MCP Server URL: https://app.enlyze.com/api/mcp

• Transport: http

• Authentication: OAuth2 (automatically on first connection)

Authentication

When your client first connects to ENLYZE MCP, you'll be automatically redirected to a login screen. Follow these steps:

1. Sign in: Log in with your ENLYZE account

2. Grant permission: The consent screen asks you to allow your AI assistant to access your ENLYZE account and its production data

3. Confirm: Click Approve or Accept to allow access

Your client saves the OAuth2 token after granting permission. You won't need to log in again until the token expires. When it does, you'll be prompted to sign in again on your next request.

For more information on the MCP specification, visit Model Context Protocol.

Your MCP client is now connected to ENLYZE.

Verify it worked

Ask your AI assistant a simple question to confirm ENLYZE MCP is connected, for example "Show me all sites". In Claude Code, you can also type /mcp and confirm that the enlyze server and its tools appear. In Claude Desktop, you'll find connected connectors under Customize → Connectors.

Available tools

ENLYZE MCP gives your AI assistant access to everything available in the ENLYZE platform: machines, sites, variables, time series, OEE, downtimes, production runs, products, data sources, and more. For the full list of available operations and parameters, see the ENLYZE API reference.

Troubleshooting

401 Unauthorized: OAuth2 authentication failed

Symptom: Client shows errors like "Unauthorized" or "Authentication failed"

Causes:

• OAuth2 token has expired

• Permission was not granted or has been revoked

• You are not logged in

Solution:

1. Try using ENLYZE MCP again. You should be redirected to the login screen

2. Make sure you're logging in with the correct ENLYZE account

3. Grant access on the permission screen

4. If the error persists, restart your AI assistant and try again

Connection refused: Server unreachable

Symptom: Client shows "Connection refused" or "Network error"

Causes:

• No internet connection

• The URL https://app.enlyze.com/api/mcp is mistyped

• ENLYZE server is temporarily unavailable

Solution:

1. Check your internet connection

2. Verify the URL is exactly https://app.enlyze.com/api/mcp (with https:// and no trailing slash)

3. Try opening the URL in your browser. You should get an HTTP 401 or 405 response (that's normal and indicates the server is reachable)

4. If the server is down, contact https://github.com/enlyze/enlyze-docs/blob/main/en/help/README.md

Tools not visible: MCP server not loading

Symptom: Client shows no available tools or ENLYZE tools don't appear

Causes:

• Client wasn't restarted after configuration

• Configuration file has JSON syntax errors

• Client doesn't support MCP (older version)

Solution:

1. Close your AI assistant completely (not just minimize) and open it again

2. Check your configuration file for JSON errors. Use an online JSON validator

3. Verify the server entry matches the instructions in your client's tab above

4. If the client doesn't support MCP, upgrade to the latest version or use a different client

Timeout: Query takes too long

Symptom: Chat freezes or shows "Request timeout"

Causes:

• Query is too complex or covers too much data

• Network is slow

• Server is overloaded

Solution:

1. Try a simpler query first, e.g., "Show me all sites"

2. Limit data ranges with dates, e.g., "Show me data from today"

3. Check your network connection

4. If timeouts occur regularly, contact https://github.com/enlyze/enlyze-docs/blob/main/en/help/README.md