developer-toolsapi_key

PageVitals

PageVitals provides website performance monitoring, synthetic testing, real-user monitoring reports, performance budgets, and optimization insights.

Integration

Vendor
PageVitals
Category
developer-tools
Auth
API_KEY
Tools
28
Composio slug
page_vitals

Tools

  • Add Configured Pages

    Add one or more explicitly supplied pages to PageVitals monitoring for a website. This persistent bulk operation can consume monitored-page quota and cause future synthetic tests, so call it only when the user explicitly requests every URL

  • Create Budget

    Create a persistent PageVitals performance budget for a website. This changes monitoring and may change owner alerting behavior, so call only when the user explicitly requests the budget and supplies the complete metric, comparison directio

  • Create Multistep Test

    Create an empty PageVitals multistep test definition with an explicit name and device profile. This only saves persistent configuration: it does not run the test, trigger any synthetic checks, or consume test-run quota.

  • Create Website

    Add a domain to the PageVitals account and begin managing it. This may consume website quota and start monitoring, so call only when the user explicitly asks to add the domain.

  • Delete Budget
    destructive

    Delete one PageVitals performance budget and stop enforcing its threshold. This is a destructive alerting mutation; use only when the user explicitly selects the exact budget ID for deletion.

  • Delete Configured Page
    destructive

    Permanently delete one PageVitals configured page and all of its test results, including historical results. This is irreversible; use only for an explicit request naming the exact website ID and configured-page ID.

  • Delete Multistep Test
    destructive

    Permanently delete one PageVitals multistep test definition. This is irreversible; use only when the user explicitly identifies the exact website ID and test ID.

  • Delete Website
    destructive

    Permanently delete one PageVitals website and all of its tests, metrics, analytics, and configuration. This is irreversible; use only for an explicit request naming the exact website ID.

  • Get Multistep Test

    Get one multistep test definition, including its configured steps.

  • Get Page Metrics

    Get the latest Lighthouse and Chrome UX metrics for one configured page and device.

  • Get Page Opportunities

    List Lighthouse improvement opportunities for a page/device, or return the full variable-shape details for one opportunity ID.

  • Get Page Timeline

    Get one historical timeline for a page/device: combined loading metrics, CrUX, network bytes, CPU time, or Google Search performance. Google Search requires that integration on the website.

  • Get Test

    Get the detailed Lighthouse, timing, resource, budget, and validation summary for one synthetic test. Provider values, nulls, metric scales, and JSON-looking strings are returned unchanged.

  • Get Test Report

    Get one specialized synthetic-test report: keyed Lighthouse opportunities, the request waterfall, or grouped HTML validation findings. Validation always omits the embedded raw HTML.

  • Get Test Series

    Get one synthetic test series and its individual tests, statuses, page IDs, device variants, and failure messages.

  • List Budgets

    List performance budgets, current status, notification settings, and affected pages for a website.

  • List Configured Pages

    List the raw pages configured for PageVitals monitoring on a website.

  • List Multistep Runs

    List historical runs for one multistep test, including status, duration, interaction, layout-shift, CPU, transfer-size, and blocking-time metrics.

  • List Multistep Tests

    List multistep tests configured for a website with recent metrics, state, and success rates. A website with no configured multistep tests returns an empty tests list.

  • List Page Metrics

    List every configured page/device combination for a website with recent timeline and latest performance metrics.

  • List Test Series

    List recent synthetic test series for a website, including status and failure counts.

  • List Website Opportunities

    List Lighthouse improvement opportunities aggregated across a website and the affected pages.

  • List Websites

    List websites visible to the connected PageVitals API key. Use the returned website IDs with all website-scoped tools.

  • Run Multistep Tests

    Trigger exactly one named multistep test or intentionally fan out to every multistep test configured for a website. Every triggered run consumes PageVitals test quota and may incur cost. Choosing target='all' can start many jobs, so use it

  • Run Test Series

    Trigger synthetic tests for selected page/device variants, or for every configured test when pages is omitted. This action consumes PageVitals test quota and may incur cost; call it only when the user explicitly requests a new run.

  • Update Budget

    Replace a PageVitals performance budget's complete metric threshold and device scope. This may change monitoring alerts or notifications. Read the current budget first, use its exact website and budget IDs, and provide all four desired stat

  • Update Configured Page

    Update a configured PageVitals page's URL, display alias, or both. This changes persistent monitoring configuration; use the exact page ID from List Configured Pages and provide at least one new value.

  • Update Multistep Test

    Update a multistep test's alias and device. Both fields are required because PageVitals PUT replacement and partial-update semantics were not safely live-tested; read the current test first when preserving either value.

Setup

  1. Create or open a Switchy Project.
  2. Open Integrations and connect PageVitals.
  3. Authorise through api_key. Switchy stores the connection against your org.
  4. Everyone in the Project can now @-mention the PageVitals tools in chat.

What teammates see: by default, memories from PageVitals are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

Starter prompts for this model will land here soon.

More developer tools MCPs

See all developer tools MCPs

Data last verified 31 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.