Skip to main content

Connecting Claude

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

  • An active SiteTrax.io account with verified email. Complete verification and confirm the intended account 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. A published Intelligence profile is optional for ordinary MCP access. If you already use the personalized Intelligence hub, its Claude card opens the same setup:

  1. Sign in at 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.

The Claude connection card on the Intelligence hub

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.

Compare the returned projects with Projects in the application under the same account. Matching results confirm read access for that request; adding a connector alone does not complete OAuth. An empty list can mean no projects are shared with the account. If account verification interrupted or expired the connection, finish verification and start again from Claude.

Permissions

Standard queries, selected published profile context, notification lists and delivery history use read access. Creating an alert or digest, or cancelling one, needs read access plus sitetrax:notifications:write. The client must request that extra permission and support it in its registration; reconnecting with the same read-only request does not add it. It may be requested initially or later. See Account Access and OAuth, Alerts and Scheduled Digests and the SiteTrax.io MCP Server reference.

Authorize with the SiteTrax.io account that 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 are not returned by the public profile tool.

Sources

No comments to display

Back to top