Connecting Claude

Use

SiteTrax.io connectsClaude to Claude as a custom connector over the remote MCP endpoint. Once it is added, you can ask operational questions inabout Claude and get answers scoped to yourauthorized SiteTrax.io projects.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

Anan activeactive, email-verified SiteTrax.io account with verified email. Complete verification and confirm the intendedprojects accountyou in the application before starting. Share at least one project with that account for useful operational answers. A Claude account with custom-connector support. Anthropic currently lists Free, Pro, Max, Team and Enterprise; Free accounts are limited to one custom connector. Check the linked Anthropic guide for current availability. On Team and Enterprise, only Owners can add a custom connector. Other members connect to the one an Owner adds, and each member authorizes their own SiteTrax.io account.

Connect from SiteTrax.io

You can open the SiteTrax.io connector setup in Claude directly, then confirm the details and connect.need. A published Intelligence profile is optionaloptional. forIn ordinarymanaged MCPClaude access.workspaces, Ifa youpermitted alreadyowner useor administrator must add the personalizedconnector Intelligencebefore hub,members itsconnect Claudetheir cardindividual opensaccounts.

Add and authorize the same setup:connector

1. Sign in at app.sitetrax.io and open Intelligence.

Scroll to Use SiteTrax.io with your assistant. On the Claude card, select Add to Claude. It opens Claude connector settings in a new tab with the SiteTrax.io Intelligence hub, or open Claude’s connector name and URL already filled in.settings. ConfirmAdd the details and add the connector. Select Connect, sign in to SiteTrax.io when prompted, review the requested permissions and authorize.

Adding it manually

If you would rather add it by hand, or the deep link is blocked by your browser:

Open Claude settings and go to Connectors. Select Adda custom web connector. Enternamed the SiteTrax.io remotewith MCP server URL:URL https://mcp.sitetrax.io/mcp. LeaveReview the advanceddetected authentication settings and use the OAuth setup supported by SiteTrax.io. Supply a custom client fieldsID emptyonly unlesswhen SiteTrax.io hasprovides given you valuesone for them.your connection. Add the connector, then select Connect and complete theComplete SiteTrax.io sign-in.in and consent, then enable the connector for your conversation.

Turn

Anthropic’s itcurrent oncustom-connector inguide 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 conversationprivate-network-only

Addingendpoint aneeds connectorcompatible makes it available; it is enabled per conversation. Use the plus button in the message box, choose connectors, and switch SiteTrax.io on for that conversation.connectivity.

Check the connection

Using SiteTrax.io, list the projects I havecan accessaccess. to.

Do not create or change anything.

Compare the returned projectsresult with Projects in the application under the same account.account Matchingin resultsapp.sitetrax.io. confirmThen read access for that request; addingrequest a known equipment observation with its time, timezone, project and record link. An installed connector alone does not completeprove OAuth.successful Anauthorization.

empty list can mean no projects are shared with

Use the account.result Ifin accountyour verificationwork

interrupted

Using orSiteTrax.io, expiredfind the connection,latest finishobservation verificationof trailer [complete identifier] at [project]. Draft a short customer-service response using only the returned evidence. Include the record link and startidentify againany missing evidence. Do not send the response.

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

Permissions and troubleshooting

StandardRead queries,access selectedsupports publishedauthorized profilequeries context,and notification lists and delivery history use read access.history. Creating an alert or digest, or cancelling one,supported needsalerts readand accessdigests plusadditionally requires sitetrax:notifications:write. The client must request and receive that extra permission and support it in its registration;scope; reconnecting with the samea read-only request does not add it. ItConfirm maythe beexact requestedproposed initiallynotification 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.

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 later.response-style Seeinstructions to Claude. Use Account Access and OAuth, Alertsfor scope and Scheduleddisconnect Digests and the SiteTrax.io MCP Server reference.details.

AuthorizeVendor withreference thechecked SiteTrax.io7 October 2026. Customer-account thatinstallation holds your project access. If you want published profile context, use the account that published it and ask Claude to retrieve that context. Another account may have different projects and its own profile. Selected published facts and priorities are available to the assistant; the saved working brief, custom instructions and response-style preferences arewas not returnedexercised byin thethis publicdocumentation profile tool.review.

Sources

Getting started with custom connectors using remote MCP, Anthropic Support