> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure GermainUX with WebMCP

> Use an AI agent in the browser to configure GermainUX through WebMCP tools exposed by the GermainUX web application.

Availability
TODO: version or later

Browser support
Chrome 149 or later (WebMCP origin trial)

> [card] [Overview](#overview)
>
> Configure GermainUX with AI

> [card] [What You Can Configure](#what-you-can-configure)
>
> Configuration areas

> [card] [Get Started](#get-started)
>
> Requirements and setup

> [card] [Security](#security-and-access-control)
>
> Permissions and review

> [!WARNING]
>
> Draft: items marked **TODO** need to be confirmed by the GermainUX team before publishing.

## Overview

The GermainUX web application supports **WebMCP**. It exposes structured tools to AI agents running in the browser, so you can configure GermainUX by asking an agent in plain language instead of navigating each settings screen yourself.

WebMCP lets a web page register tools that an AI agent can call directly, with defined inputs and outputs, rather than simulating clicks and typing. You stay in the browser while the agent works, and you see every change in the same GermainUX session. Learn more about WebMCP in [WebMCP Monitoring](https://docs.germainux.com/integrations/browser-monitoring/webmcp-monitoring.md#what-is-webmcp).

> [!NOTE]
>
> Any GermainUX configuration can be created or updated through WebMCP, so the agent can handle a multi-step setup in one request.

## Example Requests

* "Create a KPI that tracks checkout errors and alert me on Teams when it exceeds 5 per minute."
* "Add a maintenance window every Sunday from 1 AM to 3 AM."
* "Give the Support team read access to the Salesforce dashboards."
* "Change data retention for Session Replay to 90 days."
* "Turn on AI Session Replay summaries and update the prompt to focus on checkout friction."

TODO: replace with examples confirmed against the available tools.

## What You Can Configure

| Area | Examples | Learn More |
| - | - | - |
| Monitoring | Data sources, monitoring profiles, components | [Monitoring Management](https://docs.germainux.com/management/monitoring-management.md) |
| KPIs | Create and update KPIs | [KPIs Management](https://docs.germainux.com/management/manage-kpis.md) |
| Automation | Alerts, SLAs, RPA bots, notifications | [Automation Management](https://docs.germainux.com/management/automation-management.md) |
| Templates | Email, Slack, and Teams templates | [Templates](https://docs.germainux.com/management/templates.md) |
| Users and Access | Users, roles, teams, API keys | [User Management](https://docs.germainux.com/management/user-management.md) |
| Dashboards | Dashboard visibility and owners | [Dashboard Visibility](https://docs.germainux.com/management/dashboard-visibility-team-owners.md) |
| AI | LLM selection, AI features, prompts | [AI Settings](https://docs.germainux.com/management/ai-settings.md) |
| Data | Retention, maintenance windows, time ranges | [Data Retention](https://docs.germainux.com/management/data-retention.md) |

TODO: confirm the full list of WebMCP tools and any areas that are excluded.

## Get Started

### Requirements

* GermainUX TODO: version or later.
* Chrome 149 or later through the WebMCP origin trial. For local testing, enable `chrome://flags/#enable-webmcp-testing`.
* An AI agent in the browser that supports WebMCP.
* A GermainUX user account with permission to the settings you want to change.

### Configure GermainUX with an Agent

**1. Sign in to GermainUX**

Open GermainUX in a supported browser and sign in.

**2. Enable WebMCP tools**

TODO: describe whether WebMCP is on by default or where to enable it.

**3. Ask the agent**

Describe the configuration you want. The agent discovers the GermainUX tools on the page and calls them.

**4. Review the result**

Check the change in GermainUX before relying on it.

## Security and Access Control

* The agent acts within your GermainUX session, so it can only change what your user account is allowed to change (TODO: confirm).
* Changes made through WebMCP appear in the audit trail (TODO: confirm).
* Review configuration changes, especially to users, access, automation, and data retention.
* Review your organization's AI policies before using an agent with an online LLM.

See [AI Governance](https://docs.germainux.com/management/compliance-privacy-and-security/ai-governance.md) for how GermainUX handles AI security and responsible use.

## Related Documentation

> [card] [MCP Server](https://docs.germainux.com/integrations/mcp-server.md)
>
> Connect AI agents to GermainUX data

> [card] [WebMCP Monitoring](https://docs.germainux.com/integrations/browser-monitoring/webmcp-monitoring.md)
>
> Monitor WebMCP in your applications

> [card] [AI Settings](https://docs.germainux.com/management/ai-settings.md)
>
> Configure GermainUX AI

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't Find What You Need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.