Calibre MCP is read-only, and limited to what your own Calibre account can see. To set it up, see Connect an AI assistant.
What it can access#
- Read-only: it can’t run tests, record Deploys or change Sites. Use the CLI for those. The one exception is
send_feedback, which sends a note to the Calibre team. - Your Teams’ Sites only: it sees the active Sites in the Teams you belong to, in the organisation you chose when you signed in. This applies to every role, including administrators.
- One organisation per connection: to use another organisation, add a second connection.
- Revoke at any time: go to Profile → Connected apps. Administrators can see and revoke everyone’s connections in Manage → Connected apps.
- Admins can turn it off: the AI assistants setting in Manage → Settings turns MCP off for the whole organisation. It disconnects every assistant and stops new connections. It’s on by default.
- Rate limit: each connection can make 60 requests a minute.
- Treat answers as untrusted input: answers include text from your monitored websites, such as page URLs, element names and third-party names. Review what your assistant does with it, as with any web content.
On the Company plan, the Audit log records each assistant that is connected or revoked.
What your assistant can look up#
Your assistant picks the tools it needs. You don’t need to name them.
| Tool | What it does |
|---|---|
list_sites | Lists the Sites you can access. |
get_site_overview | Summarises a Site: Pages, Test Profiles, page groups, Budgets, RUM status and recent Deploys. |
list_pages | Ranks pages, or RUM page groups, by a metric from RUM, CrUX or Synthetic. |
get_rum_metrics | Real-user metrics by page, page group, device, country, city, browser, OS, navigation type or element. For INP, also by script or third party. |
get_ux_rating | The UX Rating over time, from RUM or CrUX, with the share of good, needs improvement and poor results. |
get_element_attribution | The elements behind poor LCP, CLS and INP, with timing breakdowns. For INP, also the handler and script behind each interaction. |
get_crux_metrics | Google’s CrUX values for the whole site or a page, with weekly history and optional LCP subparts. |
get_synthetic_metrics | Synthetic metrics by Page and Test Profile, compared with the period before. |
get_snapshot | One scheduled test run: each Page and Test Profile’s Core Web Vitals, Lighthouse scores and any errors. |
get_test_audits | The failing Lighthouse audits for one test, ordered by estimated savings, with the resources or elements responsible. |
compare_performance | Compares time periods, pages, Test Profiles or devices, from RUM, CrUX or Synthetic. |
list_deploys | Lists Deploys, newest first, with the revision, repository and commit link. |
get_deploy_impact | Whether a Deploy made your Site faster or slower than the one before it, per metric, from RUM or Synthetic. Flags regressions. |
list_budgets | Budgets and whether each Page and Test Profile meets them. |
list_third_parties | Third parties found in tests, or ranked by how much they slow real visitors’ interactions. |
send_feedback | Sends a note to the Calibre team when a tool fails, returns something that looks wrong, or can’t answer your question. |
How far back it looks#
- RUM: the last 30 days by default, or up to 12 months by month. Interaction attribution covers the last 7 days by default.
- CrUX: 28-day values, reported weekly. The last 3 months by default, and up to 24 months.
- Synthetic: the last 30 days by default, and up to 90 days. Values are the median, as in your dashboard.
- Deploys: the last 30 days by default, and up to 90 days.
Long lists are shortened. Your assistant is told when this happens, so it can narrow the question.