Skip to main content

​
Atoti Intelligence SDK

This is part of the Atoti Intelligence SDK offer.
This guide explains how to connect Claude Desktop to the Atoti MCP Server.

​
OAuth 2.1 browser authentication

If the Atoti Server has OAuth 2.1 enabled, recent versions of Claude Desktop and Claude Code drive the browser-based PKCE flow automatically, with no Basic-auth passkey or manual token handling required. Skip the --header "Authorization: Basic {passkey}" step below and point Claude directly at the server’s POST /mcp URL. Two modes are available: external IdP discovery (Okta, Entra ID, Auth0, Keycloak) and self-issued mode, where the Atoti Server acts as its own authorization server.
The examples below use the Streamable HTTP transport at POST /mcp, which the starter configures by default. The older server-sent events transport at /sse is deprecated for removal in Spring AI 2.0.0; it is served only when the deployment sets spring.ai.mcp.server.protocol=SSE, and reaching it means pointing the client at http://localhost:9090/sse with --transport sse-only. See MCP transport.

​
Prerequisites

Before connecting Claude, ensure the following requirements are met:
  • Atoti MCP Server is set up and running
  • Claude Desktop is installed
  • Access to Claude Desktop configuration file
  • Atoti application credentials (username and password)

​
How to configure Claude Desktop

Add the MCP Server configuration to the Claude Desktop config file. The location of this file depends on the operating system. The following examples assume the application runs locally on port 9090. Replace 9090 with the port on which the application is running.

​
Option 1: Basic authentication

The following example uses HTTP Basic authentication. Replace {passkey} with a Base64-encoded string in the format Base64(<login>:<password>).

​
Option 2: Bearer token authentication

The following example uses a long-lived JWT bearer token. Replace <jwt> with a token generated from the MCP credentials page.
The bearer token approach avoids embedding credentials in the configuration file. The MCP credentials page must be enabled in the application before a token can be generated.

​
How to generate the passkey

Replace {passkey} in the Basic authentication configuration with a Base64-encoded string. Generate the passkey using the following format:
Replace <login> and <password> with the Atoti application credentials.

​
How to verify the connection

After configuring Claude Desktop, verify that the connection works:
  1. Restart Claude Desktop
  2. Check that Claude discovers the MCP Server tools
  1. Test interaction with the Atoti Server by asking Claude to use the available tools

​
Troubleshooting

If Claude does not discover the tools, check the following:
  • The Atoti application is running and accessible
  • The MCP Server endpoint is available at the configured URL
  • The passkey is correctly formatted and encoded
  • The Claude Desktop configuration file is valid JSON
After connecting Claude, explore additional capabilities: