> ## 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

# Product Metrics in Claude Desktop and Cowork (/docs/integrations/claude-desktop)

<!-- agent-signals: reading_time_min: 4 · est_tokens: 1649 · updated: 2026-11-16 -->
Related: [Product Metrics in ChatGPT and Codex](/docs/integrations/chatgpt.md), [Product Metrics in Claude and Claude Code](/docs/integrations/claude-code.md), [Product Metrics in Cursor](/docs/integrations/cursor.md)

> Connect Product Metrics once as a Claude custom connector and use it in claude.ai, Claude Desktop chat, Cowork and the Code tab.

Claude on the web, Claude Desktop, Cowork and the Code tab all read connectors from your **Claude account**. Connect Product Metrics once and it is available in each.

| Setting                   | Value                                                                            |
| ------------------------- | -------------------------------------------------------------------------------- |
| **Connector name**        | `Product Metrics`                                                                |
| **Remote MCP server URL** | `https://www.productmetrics.io/mcp`                                              |
| **Sign-in**               | Browser sign-in to Product Metrics (OAuth), then **Connect Claude**. No API key. |

`https://www.productmetrics.io/mcp` is a client setting, not a page to open in a browser.

## 1. Add the connector

1. Open [**Add custom connector**](https://claude.ai/new?modal=add-custom-connector#customize/connectors), or go to **Customize > Connectors** in Claude Desktop and click **Add**.
2. Enter `Product Metrics` as the name and `https://www.productmetrics.io/mcp` as the remote MCP server URL. Leave **OAuth Client ID** and **OAuth Client Secret** empty: Claude registers itself. Click **Add**.
3. Click **Connect** on Product Metrics. A Product Metrics page opens and lists what Claude **Can read** and **Can change**. Signed out, click **Continue with Google** or **Sign in**, then click **Connect Claude**.

`productmetrics mcp-config --client claude` prints the same steps.

## 2. Use it in chat and Cowork

In the Chat or Cowork tab, open the **+** menu next to the prompt box, go to **Connectors**, and check that **Product Metrics** is on. Then try:

```text
Where is my Product Metrics setup, and what is the next step?
```

```text
Which products lose money after ads this month?
```

## 3. Use it in the Code tab

Local Code tab sessions use the same connector. Click **+** next to the prompt box, select **Connectors**, and turn on **Product Metrics**.

The Code tab also loads servers you added to Claude Code with `claude mcp add`. If you set up Product Metrics there with the [Claude Code guide](/docs/integrations/claude-code), check that only one Product Metrics server is active in the session.

## What you can ask

```text
"Where is my Product Metrics setup, and what is the next step?"
→ execute (GET /setup/status)

"Connect my Shopify store to Product Metrics."
→ execute (POST /companies/:companyId/stores), then a link to approve
  the install in Shopify Admin

"Create the Product Metrics conversion actions in Google Ads."
→ execute (POST /properties/:propertyId/google-ads/conversion-actions)

"Which products lose money after ads this month?"
→ list_properties, then get_poas_report (level: product,
  only_unprofitable: true)

"Why did my Google Ads ROAS drop last week?"
→ list_properties, then explain_google_ads_change
```

* **Pick a store first.** One connection covers every store you can open. Claude calls `list_properties`, then uses that store. With one store, it doesn't ask.
* **Analysis tools only read.** They never change Google Ads or your store. Setup runs through `search` and `execute`, and deletes run only after you confirm.
* **Browser steps come back as a link.** Google consent, a store install or checkout needs you in a browser. Claude gives you the link, waits, then checks the setup status again.
* **Secrets stay out of the chat.** Fields such as a store setup token show only in the Product Metrics app or the CLI.

Every tool: [MCP tools](/docs/mcp/tools). The connector alone is enough here: the skills and the `productmetrics` CLI are for coding agents such as [Claude Code](/docs/integrations/claude-code).

## Troubleshooting

| Problem                                                                           | Fix                                                                                                                                                                                            |
| --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Product Metrics tools don't appear                                                | Start a new conversation or session after connecting, and check that **Product Metrics** is on in the **Connectors** menu.                                                                     |
| Product Metrics appears more than once                                            | Remove extra entries so one connector remains. Connectors you add in **Customize > Connectors** work in Cowork; local servers in `claude_desktop_config.json` do not, so prefer the connector. |
| "This connection expired or was removed; connect Product Metrics again."          | Click **Connect** on Product Metrics in **Customize > Connectors**. If that fails, remove the connector and add it again. The connection lasts 30 days from approval.                          |
| "This connection only has MCP access, so it cannot call the Product Metrics API." | Remove the connector, add it again and allow everything the consent page shows.                                                                                                                |
| "The MCP server is not enabled for this account yet."                             | Ask Product Metrics support to turn it on 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."                                                             | Name the store in your question; Claude calls `list_properties` and tries again.                                                                                                               |

## More

* [Get started](/docs/mcp/overview) with Product Metrics MCP in other clients.
* [For humans](/docs/mcp/connect): the consent page and browser sign-in in detail.
* [MCP tools](/docs/mcp/tools): what each tool does, with its arguments.
