# Claude

# Connecting Claude

Use Claude to ask questions about authorized SiteTrax.io observations and analytics. The remote connector makes SiteTrax.io tools available to Claude; SiteTrax.io continues to enforce your account’s project access.

## Before you start

Use an active, email-verified SiteTrax.io account with the projects you need. A published Intelligence profile is optional. In managed Claude workspaces, a permitted owner or administrator must add the connector before members connect their individual accounts.

## Add and authorize the connector

1. Use **Add to Claude** in the SiteTrax.io Intelligence hub, or open Claude’s connector settings.
2. Add a custom web connector named **SiteTrax.io** with URL `https://mcp.sitetrax.io/mcp`.
3. Review the detected authentication settings and use the OAuth setup supported by SiteTrax.io. Supply a custom client ID only when SiteTrax.io provides one for your connection.
4. Complete SiteTrax.io sign-in and consent, then enable the connector for your conversation.

Anthropic’s [current custom-connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) covers individual and managed-workspace setup. Labels and available authentication choices vary by account. Remote connector requests originate from Anthropic’s cloud, including when you use Claude Desktop; a private-network-only endpoint needs compatible connectivity.

## Check the connection

> Using SiteTrax.io, list the projects I can access. Do not create or change anything.

Compare the result with the same account in [app.sitetrax.io](https://app.sitetrax.io). Then request a known equipment observation with its time, timezone, project and record link. An installed connector alone does not prove successful authorization.

## Use the result in your work

> Using SiteTrax.io, find the latest observation of trailer \[complete identifier\] at \[project\]. Draft a short customer-service response using only the returned evidence. Include the record link and identify any missing evidence. Do not send the response.

A draft is different from a sent message. Sending through another system requires a separately connected tool and authorization.

## Permissions and troubleshooting

Read access supports authorized queries and notification history. Creating or cancelling supported alerts and digests additionally requires `sitetrax:notifications:write`. The client must request and receive that scope; reconnecting with a read-only request does not add it. Confirm the exact proposed notification before creation.

If Claude gives a general answer, confirm SiteTrax.io is enabled for the conversation and ask it to use the tools. If the project list differs from the application, check the connected account and sharing. See [Troubleshooting Connections](https://docs.sitetrax.io/books/ai-integrations/page/troubleshooting-connections).

Authorized results are returned to Anthropic. A published profile can supply selected facts and priorities, but it does not pass your saved working brief or response-style instructions to Claude. Use [Account Access and OAuth](https://docs.sitetrax.io/books/ai-integrations/page/account-access-and-oauth) for scope and disconnect details.

<small>Vendor reference checked 7 October 2026. Customer-account installation was not exercised in this documentation review.</small>