User Community Service Desk Downloads

Install MCP Trust Layer

Follow this guide to install the Ataccama Model Context Protocol (MCP) trust layer and start using your AI assistant to read data from Ataccama ONE. The guide uses Claude Desktop as an example.

For an overview of what the MCP trust layer is and what tools it contains, see MCP Trust Layer for External AI Agents.

Prerequisites

Before you start, prepare your environment.

Ataccama MCP server

Download the following DXT file with the Ataccama MCP server package: mcp-ataccama.dxt.

Python

Download and install:

To verify whether you have the necessary tools, run these commands:

python --version
pip --version
uv --version

Claude Desktop

Download and install Claude Desktop.

To use it, you’ll need an active Claude account.

Ataccama environment

To successfully configure the MCP server, you’ll need:

Item Description

Ataccama URL

Base URL of your Ataccama ONE environment. For example, https://your-instance.ataccama.one/.

Include the protocol (https://) and trailing slash (/).

Keycloak realm

Your organization’s realm name. Typically in the format instance-environment (for example, production-main).

Keycloak client ID

Default: agentbe-ataccama-mcp-public-client.

Only change if your organization uses a custom client.

If you don’t have access to this information, contact your Ataccama admin to obtain it.

Installation

Install MCP server in Claude

  1. Open Claude Desktop.

  2. Navigate to Settings > Extensions > Advanced Settings.

  3. Select Install Extension.

  4. Find and select the downloaded Ataccama MCP server DXT file.

  5. Select Install and confirm your choice when prompted.

  6. Remain on the same screen and proceed with Configure MCP server connection.

Configure MCP server connection

  1. Select Configure.

    If you exited the preview, find the MCP extension in Settings > Extensions and select Configure.
  2. Enter the following details:

    • Ataccama Server URL: The URL of your Ataccama environment, including the protocol and the trailing slash. For example, https://your-instance.ataccama.one/.

    • Keycloak Realm: Your organization’s Keycloak realm name.

    • Keycloak Client ID: If using a custom client ID, enter the correct Keycloak client ID. Otherwise, skip this field.

  3. Select Save to apply the configuration.

Verify installation

After saving, Claude attempts to connect to your Ataccama environment.

Once prompted, authenticate with your Ataccama credentials.

To test everything works as expected, try asking Claude: "What Ataccama tools are available?".

Troubleshooting

Here are some common issues you might encounter while installing or using the MCP trust layer, along with suggested solutions.

Common issues and how to solve them

Connection refused or timeout

Problem: Claude Desktop cannot connect to the Ataccama MCP server.

Cause: The Ataccama server URL is incorrect, the server is unreachable from your network, or a firewall is blocking the connection.

Solution:

  • Verify the server URL is correct and accessible.

  • Check that you’re on your organization’s network or VPN if required.

  • Ensure your firewall or security software is not blocking Claude Desktop.

Authentication failed

Problem: After entering your credentials, authentication fails.

Cause: Your Ataccama credentials are invalid, your account lacks the necessary permissions, or the Keycloak configuration is incorrect.

Solution:

  • Confirm your Ataccama credentials are valid.

  • Check that your user account has API access enabled.

  • Verify the Keycloak client ID is correct.

  • Ensure the Keycloak realm name matches exactly (case-sensitive).

MCP server not starting

Problem: The MCP server fails to start or Claude Desktop shows the extension as inactive.

Cause: Required runtime dependencies (Python, uv, Node.js) are missing or not properly configured on your system.

Solution:

  • Ensure built-in Node.js is enabled in Claude settings.

  • Verify Python is properly installed and in your system PATH.

  • If you have multiple Python versions installed, ensure the correct version is set as default.

Viewing error logs

For detailed error information, select error notifications in Claude Desktop to view logs, or review the MCP server logs in Settings > Extensions.

Complete restart procedure

If other troubleshooting steps don’t resolve your issue, perform a complete restart:

  1. Close Claude Desktop completely.

  2. Open Task Manager (Windows) or Activity Monitor (Mac).

  3. End any remaining Claude processes.

  4. Restart Claude Desktop.

  5. Re-enter configuration if prompted.

Was this page useful?