Authenticate towards the Ardoq MCP server with OAuth so teams connect securely without managing expiring API keys.
This solves the problem where teams managing Ardoq MCP server access must manually rotate expiring API keys across every connected client, creating operational friction and security risk.
MCP Single Sign-On replaces API keys with OAuth — the same authentication standard enterprises already use across Salesforce, Workday, and their ITSM platforms. Once configured, connections stay alive without manual intervention. No rotation schedules. No scrambling when integrations silently break. If the authenticated session expires, there’s a workflow to re-authenticate with OAuth.
Managing who can set up OAuth-based MCP clients.
To configure which roles can set up OAuth-based MCP clients, open the Access control page and check the "Access Ardoq MCP via OAuth" privilege
To grant an individual user the privilege, locate the user under "User management", click the kebab menu and select "Assign privileges".
Example: How to set up MCP Single Sign-On for Claude
Please refer to the other MCP help articles for other MCP clients.
First make sure you have an Ardoq MCP registered. Please refer to this Knowledge base Article for background and details.
To add the MCP server, open a terminal and add
claude mcp add --transport http ardoq-mcp https://<your-tenant>.ardoq.com/mcp/? (note the trailing /? )
In the Claude Code terminal, type /mcp to start authenticating.
This will trigger a browser window to open for you to authenticate
Choose "Authorize", and a confirmation screen should show. You can close this.
Back in the terminal, you should also see a confirmation message:
