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 installed.
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/
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 403 Forbidden error.
- Customer IP not allowlisted for AgentFlow MCP Server access
- Cause - Reltio currently applies IP filtering to all MCP environments as a security measure. If your organization has not yet purchased an AgentFlow MCP Server access, your IP address will not be allowlisted. This results in a 403 Forbidden error when trying to connect, even with valid credentials and tokens.