Skip to main content

Troubleshooting Connections

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 reference.

Setting up

What you seeLikely causeWhat to do
The assistant cannot reach the server at allThe client does not support remote MCP servers, or a network control is blocking the endpointConfirm 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 startThe client only supports local servers running on your own machineA local-only client cannot reach a remote endpoint. Use a client that supports remote MCP servers
There is no option to add a connectorPlan or role restrictionOn 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 nothingThe new tab was blockedAllow the pop-up, or add the connector manually using the endpoint above
Microsoft Copilot is shown but cannot be selectedThat connection is still being builtUse ChatGPT or Claude for now. See Supported AI Platforms
It works on a laptop but not on a phonePlatform limitationChatGPT apps built on MCP are supported on the web rather than in the mobile apps

After connecting

What you seeLikely causeWhat to do
Authorization succeeded but no projects appearNo projects are shared with the account you used, or you signed in with a different accountConfirm 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 prioritiesThe account connected to the assistant is not the account that published your Intelligence profileProfiles are held per user. Reconnect using the same SiteTrax.io account you used to publish, then ask again
Fewer projects than you expectThe assistant is scoped to a different account with narrower accessCompare 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 requiredThe operation needs the notifications write scopeReconnect 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 chatIt is not enabled for that conversationIn Claude, enable SiteTrax.io from the plus button in the message box for that conversation

Confirming a connection is healthy

Two checks settle most uncertainty.

  1. Ask the assistant to list the projects you have access to, and compare against Projects in the application.
  2. Ask for the most recent observation of an identifier you can find yourself in the assets gallery, and compare the time and project.

If both match, the connection and its scope are correct, and any remaining difference is a question about how the data is being interpreted rather than about the connection.

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.