> ## Documentation Index
> Fetch the complete documentation index at: https://f82cc46-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://f82cc46-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://f82cc46-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://f82cc46-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Connect Product Metrics MCP with a browser sign-in (/docs/mcp/connect)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1693 · updated: 2026-11-16 -->
Related: [Get started with the Product Metrics MCP server](/docs/mcp/overview.md), [Connect Product Metrics MCP from a coding agent](/docs/mcp/for-agents.md), [Product Metrics MCP tools](/docs/mcp/tools.md), [Product Metrics MCP server reference](/docs/mcp/reference.md)

> Add the Product Metrics MCP server to Claude, ChatGPT, Cursor or VS Code and sign in through your browser. No API key.

## Sign in

Server URL (remote HTTP; your client starts the browser sign-in): `https://www.productmetrics.io/mcp`

* **Claude** (web, Desktop and Cowork): open [**Add custom connector**](https://claude.ai/new?modal=add-custom-connector#customize/connectors), name it `Product Metrics`, paste the URL, then click **Connect**. See [Claude Desktop & Cowork](/docs/integrations/claude-desktop).
* **ChatGPT**: turn on **Developer mode** under **Settings → Apps → Advanced settings**, then **Create app** with the URL and **OAuth**. See [ChatGPT & Codex](/docs/integrations/chatgpt).
* **Cursor**: [**Add to Cursor**](cursor://anysphere.cursor-deeplink/mcp/install?name=product-metrics\&config=eyJ1cmwiOiJodHRwczovL3d3dy5wcm9kdWN0bWV0cmljcy5pby9tY3AifQ==), or add `{"mcpServers": {"product-metrics": {"url": "https://www.productmetrics.io/mcp"}}}` to `~/.cursor/mcp.json`. See [Cursor](/docs/integrations/cursor).
* **VS Code**: [**Add to VS Code**](vscode:mcp/install?%7B%22name%22%3A%22product-metrics%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fwww.productmetrics.io%2Fmcp%22%7D), then sign in when VS Code asks.
* **Claude Code or Codex**: one terminal command, see [For agents](/docs/mcp/for-agents).

A person completes the sign-in and approves the connection. There is no API key or header to copy.



> **Note:** `https://www.productmetrics.io/mcp` is a server URL for your MCP client, not a page to open in a browser. Your client opens the sign-in page for you.

## The consent page

Your client opens a Product Metrics page that names the app and lists what it **Can read** and **Can change**.

1. **Signed out?** Click **Continue with Google**: it signs you in, or creates an account, and brings you back. **Already have an account? Sign in** uses your usual sign-in.
2. **Check the request.** The page names the app and its website, and where your answer returns to (**Returns to an app on this computer** for the CLI and other local apps).
3. **Click Connect** with the app's name, for example **Connect Claude**. **Cancel** sends the app a refusal.

* **Wrong account?** Signed in, the page shows your email and **Not you? Sign out**.
* **A request expires after 30 minutes**, or once it is answered. The page then says **This request has expired**: start connecting again from your client.
* **One connection covers every workspace** you can open. It lasts **30 days** from approval, however often you use it; then you sign in again.

Scopes, tokens and the OAuth flow: [Reference](/docs/mcp/reference#access-control).

## Before you start

* **A Product Metrics account.** No account yet? **Continue with Google** creates one. The assistant can then set up your workspace with the API tools.
* **Pro on each property** you want the analysis tools to read. Without it the assistant gets "This property needs a Product Metrics Pro subscription for the MCP server."
* **The MCP server turned on for your account** for the analysis tools. If the assistant says "The MCP server is not enabled for this account yet", ask Product Metrics support to turn it on.

## Choose a store

The analysis tools read one property (one store with its Google Ads account).

* **Name the store in your question.** The assistant calls `list_properties` and passes that store's `property_id`. With one property, it uses that one without asking.
* **Pin one property in the URL**, for a script or agent that should only see one store:

  ```text
  https://www.productmetrics.io/mcp?selectedAccountPropertyId=<propertyId>
  ```

## Try

```text
Which Product Metrics stores can I open, and what is left to set up?
```

The assistant calls `list_properties`, then `execute` with `GET /setup/status`. More to try:

* "Why did my Google Ads ROAS drop last week?" → `explain_google_ads_change`
* "Which products should I look at first?" → `list_products_to_investigate`

If no Product Metrics tools appear, start a new chat and check that **Product Metrics** is switched on in the chat's tools or connectors menu.

## Troubleshooting

| What the assistant says                                                           | What to do                                                                                                              |
| --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| "This connection expired or was removed; connect Product Metrics again."          | Reconnect: sign in again from the client's connector or MCP settings, or remove the connector and add it again.         |
| "This connection only has MCP access, so it cannot call the Product Metrics API." | Remove Product Metrics from the client and add it again. Allow the read, setup and write access the consent page shows. |
| "The MCP server is not enabled for this account yet."                             | Ask Product Metrics support to turn on the MCP server for your account.                                                 |
| "This property needs a Product Metrics Pro subscription for the MCP server."      | Upgrade that store to Pro, or ask about another store.                                                                  |
| "No property chosen."                                                             | Tell the assistant which store you mean; it calls `list_properties` and tries again.                                    |
| "The limit of … tool calls per hour … is reached."                                | Wait the minutes it names. Expensive tools have a lower hourly limit: see [MCP tools](/docs/mcp/tools).                      |

To disconnect, remove the connector in the assistant's settings. To revoke the app's access on the Product Metrics side as well, ask Product Metrics support: it takes effect within about a minute.

## More



* [Choose a tool](/docs/mcp/tools): what each Product Metrics MCP tool does, with its arguments.
* [For agents](/docs/mcp/for-agents): add the server from the terminal, with skills and the CLI.

## For AI assistants

If you are an AI assistant and the Product Metrics tools (list_properties, search, execute and the rest) are not available to you, the user has not connected the MCP server yet. Give them the URL [https://www.productmetrics.io/mcp](https://www.productmetrics.io/mcp) and the steps for their client from this page. Never ask the user for a password, token or API key: sign-in happens in their browser on a Product Metrics page. For what each tool does, read [https://www.productmetrics.io/docs/mcp/reference](https://www.productmetrics.io/docs/mcp/reference).
