Documentation · Use
AI assistants over MCP
Both paid plans include a hosted MCP server. An assistant that supports the Model Context Protocol, such as Claude, ChatGPT or Cursor, can ask about your store in plain words ("why did renewals fail on Tuesday?", "what changed before checkout broke?") and get answers from your own data, with the evidence cited. The connection is read-only: an assistant can look at your sites and can never change them.
Connect with your account
| Server URL | https://mcp.operanse.com |
| Sign-in | Your Operanse email and password, entered on our sign-in page. The assistant never sees them. |
| You choose | Which organisations the assistant can read. Disconnect it at any time under AI assistants in the dashboard. |
In Claude (web, desktop or mobile), add a custom connector with the server URL and sign in when it asks. In Claude Code:
claude mcp add --transport http operanse https://mcp.operanse.comOther assistants that support MCP sign-in work the same way: add the server by URL, sign in, tick the organisations.
Or create a personal token
For assistants that cannot sign in, create a personal token under AI assistants. A token works for one organisation and is sent as a bearer token:
Authorization: Bearer <token>A token is shown once. It lasts 90 days unless you choose between 1 and 365, and can be revoked on the same page. Anyone who holds it can read that organisation's data, so keep it private.
What an assistant can read
The server exposes one tool per question, and every answer states its source and how fresh it is: cached telemetry, or a live read from the site.
| Tool | Answers |
|---|---|
list_sites | The sites the signed-in person can see. |
get_site_health, explain_site | The site's current state and what is unusual, in context. |
get_incidents, get_active_anomalies, get_alert_history | What is open, what was detected, what was sent. |
get_recent_changes | Plugin, theme, setting and page changes, with who made them. |
get_payment_health, get_subscription_health, get_business_metrics, get_funnel_metrics | Payments, renewals, orders and the checkout funnel against the store's normal. |
get_action_scheduler_health, get_integration_health, get_webhook_health, get_uptime_history, get_host_resources | Background jobs, outbound services, WooCommerce webhooks, uptime and the server. |
get_site_forms, get_form_monitors, get_custom_events, get_baselines | Forms, the monitors on them, your own reported events, and the learned bands. |
investigate_issue, get_investigation | Starts a live investigation of a question and returns its findings with evidence ids. |
A member limited to certain sites sees only those sites over MCP, and a viewer cannot start investigations. Organisations on the free Watch plan are not shown to an assistant.