Configure Claude to connect with Reltio AgentFlow MCP Server

Learn how to configure the Claude desktop application to securely connect to the Reltio AgentFlow MCP Server so that Claude can access governed, context aware data.

Prerequisites

Before you begin, make sure you have:

The MCP feature enabled in the physical configuration of your tenant. Contact Reltio Support if you need help enabling the MCP feature
One of the following roles in your tenant:
- ROLE_EXECUTE_MCP, or
- ROLE_ADMIN_MCP
The AgentFlow MCP server endpoint
Claude desktop app (version 0.7.0 or later)
Permission to access and edit Claude's configuration file on your local machine
Node.js is installed

To configure Claude to connect to Reltio AgentFlow MCP Server:

Locate the configuration file for Claude desktop based on your OS:


Operating system	Configuration file path
Windows	%APPDATA%\\Claude\\claude_desktop_config.json
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Linux	~/.config/Claude/claude_desktop_config.json

Open or create the configuration file in a JSON-capable text editor with the following base structure:
```
{
  "mcpServers": {}
}
            
```

Add the Reltio AgentFlow MCP Server connection under the mcpServers object using the correct command path for your operating system.

Windows configuration

{
  "mcpServers": {
    "ReltioMcpServer": {
      "command": "C:\\PROGRA~1\\nodejs\\npx.cmd",
      "args": [
        "mcp-remote",
        "https://<Env>.reltio.com/ai/tools/mcp/",
        "9696",
        "--debug"
      ]
    }
  }
}

Mac and Linux configuration

{
  "mcpServers": {
    "ReltioMcpServer": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://<Env>.reltio.com/ai/tools/mcp/",
        "9696",
        "--debug"
      ]
    }
  }
}

Save your configuration file.
Restart the Claude desktop application.
1. Completely exit Claude, ensuring no background processes are running.
2. Reopen Claude to apply your configuration.

Result

After restart, Claude should connect to the configured Reltio AgentFlow MCP Server. Confirm connectivity by:

Checking for the server name in the Claude interface
Running a tool or request that invokes the server
Using these log locations to troubleshoot errors:
Operating system Log location
Windows %APPDATA%\Claude\logs\
macOS ~/Library/Logs/Claude/

Operating system	Log location
Windows	%APPDATA%\Claude\logs\
macOS	~/Library/Logs/Claude/

Troubleshooting

Use this section to identify and resolve common issues that can prevent Claude from connecting to the Reltio AgentFlow MCP Server or executing tools correctly.

Bearer token expires and Claude fails to connect

Cause — the configuration uses a Reltio bearer token, which expires after a set duration. When the token becomes invalid, authentication requests to the MCP server will fail with a 401 invalid access token.

Resolution — Reopen Claude and complete the authentication flow again. If prompted, sign in on the redirected login page to reauthorize access to the Reltio AgentFlow MCP Server.

Clear cached MCP authentication data

Cause — Cached authentication data in the local MCP authentication directory may prevent Claude from connecting to the Reltio AgentFlow MCP Server or completing tool execution.

Resolution — If you're having persistent issues, try clearing the local MCP authentication cache. To clear the cache, perform the following steps:

Delete the cached MCP authentication directory for your operating system by running the applicable command:
Mac/Linux
```
rm -rf ~/.mcp-auth
```
Windows
```
rmdir /s /q %USERPROFILE%\.mcp-auth
```
By default, mcp-remote stores credentials in ~/.mcp-auth. If your environment uses the MCP_REMOTE_CONFIG_DIR variable, delete the directory specified by that variable instead.
Restart the Claude desktop application.
Try the connection again and complete the authentication flow if prompted.

Additional checks — If the issue continues after clearing the cache, perform the following checks:

Confirm that your system version of Node.js is version 18 or later, because Claude Desktop uses the system-installed Node.js version.
Ensure that you restart Claude Desktop after editing the claude_desktop_config.json file.

If you're using a VPN or corporate proxy, configure the NODE_EXTRA_CA_CERTS environment variable to point to the required CA certificate file. The following example shows how to add the NODE_EXTRA_CA_CERTS environment variable in the Claude desktop configuration file:

{
  "mcpServers": {
    "ReltioMcpServer": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://<Env>.reltio.com/ai/tools/mcp/",
        "9696",
        "--debug"
      ],
      "env": {
        "NODE_EXTRA_CA_CERTS": "/path/to/your-ca-certificate.pem"
      }
    }
  }
}

Unify and manage your data

Configure Claude to connect with Reltio AgentFlow MCP Server

Footer