How AI clients sign in
AI clients can sign in to the MCP Server in two ways. You can enable both, and the server tells them apart automatically.Turn on the MCP Server
Open the MCP settings
Enable it

The MCP configuration with the Enable button highlighted
/mcp, for example https://example.cloud.germainux.com/mcp.
Set up OAuth sign-in (recommended)
With OAuth, users connect by entering only the endpoint URL in their AI client. The client then opens a browser window where the user logs in to GermainUX and approves access.Open the OAuth server settings
Set the issuer
issuer) to the address users reach GermainUX on, for example https://example.cloud.germainux.com. The MCP endpoint is then <Issuer>/mcp.Leave Login Page (loginPage) and Consent Page (consentPage) at their defaults unless your workspace is served from a different address.
The OAuth server configuration with the Issuer set
Check which AI clients are allowed
Restart the REST service
Allowed AI clients
GermainUX only issues tokens to clients you have allowed. The defaults cover Claude, ChatGPT and clients that run on the user’s machine, so most installations don’t need to change anything here.chatgpt.com entries to stop ChatGPT from connecting. Turn off Allow Loopback Redirects to block clients that run on users’ machines.
Session lifetimes
Advanced: token and approval lifetimes
Advanced: token and approval lifetimes
Use API keys (alternative)
Use a GermainUX API key if your AI client can’t use OAuth, or if you’re connecting an automated agent.Enable bearer authentication
Create an API key

Creating an API key
Hand it to the user
Authorization: Bearer <key> header.What users can see and do
- Every tool call runs as the signed-in user (or the API key’s user). That user’s permissions, team-based visibility and data-masking settings apply exactly as they do in the workspace.
- Almost all tools only read data. The exception is
update_ux_profile_customizations, which changes UX monitoring profile scripts. It requires the configuration-write permission, and its changes only apply to new sessions. search_contentis only offered when a content indexer is configured.
Limit which tools are offered
To hide tools from all AI clients, add their names to Disabled Tools under Services → REST → MCP. For example, addupdate_ux_profile_customizations to make the server strictly read-only. This takes effect immediately, without a restart.
See Available Tools for all tool names.
Query limits
These limits protect GermainUX’s query capacity for dashboards and alerting. They apply per server node and take effect immediately.Monitor MCP usage
Every MCP tool call is recorded in the Audit Log. This includes calls that failed or were stopped by a query limit.Open the Audit Log
Find the calls you're interested in

MCP tool calls in the Audit Log
Open a call for details
- whether it succeeded or failed, and how long it took
- the AI client that made the call (for OAuth sign-in)
- the error, if it failed
- the arguments the AI client sent. For
run_scripted_query, the script is shown separately as code. - the result. Small results are shown in full. Larger ones are summarized, for example as a row count rather than the rows themselves.

Details of one MCP tool call
Next steps
Connect an AI Client
Example Prompts
Get Help
Contact GermainUX Support
Can't Find What You Need?
The content of this document is proprietary to GERMAIN SOFTWARE.

