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: 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.

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

Cursor

VS Code

Codex

Other MCP clients

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