If answers come back generic rather than tailored to your operation, check that you authorized with the same SiteTrax.io account that published your Intelligence profile. See [Troubleshooting Connections](/books/ai-integrations/page/troubleshooting-connections).
## Sources - [Developer mode and MCP apps in ChatGPT, OpenAI Help Center](https://help.openai.com/en/articles/12584461-developer-mode-and-mcp-apps-in-chatgpt) - [Apps in ChatGPT, OpenAI Help Center](https://help.openai.com/en/articles/11487775-connectors-in-chatgpt) # Connecting Claude  SiteTrax.io connects to Claude as a custom connector over the remote MCP endpoint. Once it is added, you can ask operational questions in Claude and get answers scoped to your SiteTrax.io projects. ## Before you start - A SiteTrax.io account with at least one shared project. - A Claude account on a plan that supports custom connectors. Anthropic documents these as Pro, Max, Team and Enterprise. - On Team and Enterprise, only Owners can add a custom connector. Everyone else connects to one an Owner has already added. ## Connect from SiteTrax.io 1. Sign in at [app.sitetrax.io](https://app.sitetrax.io) and open **Intelligence**. 2. Scroll to **Use SiteTrax.io with your assistant**. 3. On the Claude card, select **Add to Claude**. It opens Claude connector settings in a new tab with the SiteTrax.io connector name and URL already filled in. 4. Confirm the details and add the connector. 5. 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: 1. Open Claude settings and go to **Connectors**. 2. Select **Add custom connector**. 3. Enter the SiteTrax.io remote MCP server URL: `https://mcp.sitetrax.io/mcp` 4. Leave the advanced OAuth client fields empty unless SiteTrax.io has given you values for them. 5. Add the connector, then select **Connect** and complete the SiteTrax.io sign-in. ## Turn it on in a conversation Adding a connector 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. ## Check the connection > Using SiteTrax.io, list the projects I have access to. Projects matching what you see in the application confirm the connection and its scope. ## Permissions Standard operational queries use read access. Notification and digest capabilities require a separate write scope and should be approved only when your workflow needs them. The [SiteTrax.io MCP Server](/books/mcp-server/page/sitetraxio-mcp-server) reference covers scopes in full.Sign in to the connector with the same SiteTrax.io account that published your Intelligence profile. A different account authenticates successfully but carries different project access and no profile context.
## Sources - [Getting started with custom connectors using remote MCP, Anthropic Support](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp) # Understanding MCP  Model Context Protocol, usually shortened to MCP, is an open standard that lets an AI assistant connect to an outside system and use it. SiteTrax.io implements it so that assistants can work with your operational data without anyone exporting it first. ## Why it exists Before MCP, getting an assistant to answer a question about your yard meant copying data into a prompt or building a bespoke integration for each assistant. Both approaches age badly. A copied extract is stale the moment it is pasted, and a bespoke integration has to be rebuilt for the next tool. MCP replaces that with one connection the assistant understands. SiteTrax.io publishes what it can do once, and any compatible assistant can use it. ## What it means in practice| Without MCP | With MCP |
|---|---|
| Export a report, paste it into a chat | The assistant reads the live record at the moment you ask |
| The extract reflects one moment and one filter | Every question is answered against current data |
| The assistant cannot check its own answer | The assistant can retrieve the supporting record and its image |
| Sharing the extract shares everything in it | Access follows the signed-in SiteTrax.io account |
| If you need to | Ask for |
|---|---|
| Locate one unit | The most recent observation of a specific identifier, with project, time and image |
| Understand a period | Activity across your sites for a date range, with totals and trends |
| Compare | A breakdown by project, camera, asset type, status code or time period |
| Measure dwell | Observed time between defined operational boundaries, such as gate-in to gate-out |
| Find problems | Records meeting review criteria, unreadable results, or unusual volume gaps |
| Check capture health | Camera activity and scan health across your projects |
| Get the evidence | The detection image or video metadata behind a specific record |
Your published Intelligence profile shapes the response style you get back. If you asked for answer plus why, expect a short explanation underneath the number.
# Supported AI Platforms  SiteTrax.io exposes one remote MCP endpoint, so any assistant that supports remote MCP servers with OAuth can use it. The table below records the platforms SiteTrax.io provides a direct route for, and their current status in the application. ## Status| Platform | How it connects | Status | Guide |
|---|---|---|---|
| ChatGPT | Published SiteTrax.io app, opened from the Intelligence hub | Available | [Connecting ChatGPT](/books/ai-integrations/page/connecting-chatgpt) |
| Claude | Custom connector pointed at the SiteTrax.io remote MCP endpoint | Available | [Connecting Claude](/books/ai-integrations/page/connecting-claude) |
| Microsoft 365 Copilot | SiteTrax.io connector | Not yet available. The Intelligence hub lists Copilot for visibility and states that the connection is still being built. | [Connect SiteTrax.io to Microsoft 365 Copilot](/books/mcp-server/page/connect-sitetraxio-to-microsoft-365-copilot) |
| Other MCP-compatible clients | Add `https://mcp.sitetrax.io/mcp` as a remote MCP server | Supported where the client meets the requirements below | [SiteTrax.io MCP Server](/books/mcp-server/page/sitetraxio-mcp-server) |
The Microsoft 365 Copilot guide describes the connection as designed. Until the Intelligence hub stops showing Copilot as coming soon, treat that page as preparation rather than as a connection you can complete today.
## What a client needs to qualify - Support for **remote** MCP servers. A client that only runs local servers on your own machine cannot reach the endpoint. - **Streamable HTTP** transport. Server-Sent Events transport is not supported. - **OAuth** support, so authorization completes on the SiteTrax.io side. - Support for MCP **tools and resources**. SiteTrax.io does not expose MCP prompts. ## Platform limits worth knowing before you commit - **ChatGPT.** Apps built on MCP are supported on the web rather than in the mobile apps. On workspace plans an administrator controls whether apps can be added. - **Claude.** Custom connectors are available on Pro, Max, Team and Enterprise. On Team and Enterprise only Owners can add one; other members connect afterwards. ## Choosing between them There is no data difference. Every platform reaches the same records under the same permissions, and analytical work happens on the SiteTrax.io server either way. Choose the assistant your team already uses, and connect with the SiteTrax.io account that holds your project access and published profile. # Troubleshooting Connections  Connection problems, in the order they usually appear. For problems with the data in an answer rather than the connection itself, see the troubleshooting section of the [SiteTrax.io MCP Server](/books/mcp-server/page/sitetraxio-mcp-server) reference. ## Setting up| What you see | Likely cause | What to do |
|---|---|---|
| The assistant cannot reach the server at all | The client does not support remote MCP servers, or a network control is blocking the endpoint | Confirm the endpoint is `https://mcp.sitetrax.io/mcp`, that the client supports remote servers over HTTPS with OAuth, and that no firewall or security tool blocks it |
| Nothing happens when authorization should start | The client only supports local servers running on your own machine | A local-only client cannot reach a remote endpoint. Use a client that supports remote MCP servers |
| There is no option to add a connector | Plan or role restriction | On Claude Team and Enterprise only Owners can add custom connectors. In ChatGPT workspaces an administrator controls app creation. Ask whoever administers your assistant |
| The Add to Claude or Open in ChatGPT link does nothing | The new tab was blocked | Allow the pop-up, or add the connector manually using the endpoint above |
| Microsoft Copilot is shown but cannot be selected | That connection is still being built | Use ChatGPT or Claude for now. See [Supported AI Platforms](/books/ai-integrations/page/supported-ai-platforms) |
| It works on a laptop but not on a phone | Platform limitation | ChatGPT apps built on MCP are supported on the web rather than in the mobile apps |
| What you see | Likely cause | What to do |
|---|---|---|
| Authorization succeeded but no projects appear | No projects are shared with the account you used, or you signed in with a different account | Confirm which account you authorized with, and that at least one project is shared with it. This is a sharing question rather than an authentication one |
| Answers are generic and ignore your priorities | The account connected to the assistant is not the account that published your Intelligence profile | Profiles are held per user. Reconnect using the same SiteTrax.io account you used to publish, then ask again |
| Fewer projects than you expect | The assistant is scoped to a different account with narrower access | Compare the project list in the assistant against Projects in the application while signed in as the same user |
| A tool reports that another permission is required | The operation needs the notifications write scope | Reconnect and approve the extra permission, but only if creating alerts or digests is part of your workflow |
| The connector is present but does nothing in a chat | It is not enabled for that conversation | In Claude, enable SiteTrax.io from the plus button in the message box for that conversation |
Never paste SiteTrax.io passwords, OAuth tokens or client secrets into a prompt, a configuration field or a support email.
## Getting help When reporting a connection problem, include the assistant you are using, the approximate time, the SiteTrax.io account email, the project involved, what you attempted, and any error message shown.