MCP Server

• SiteTrax.io MCP Server
• Connect SiteTrax.io to Microsoft 365 Copilot

SiteTrax.io MCP Server

Connect AI assistants and MCP-compatible applications directly to SiteTrax.io operational data and SiteTrax.io Intelligence.

Overview

The SiteTrax.io Model Context Protocol (MCP) server provides secure access to SiteTrax.io operational data through compatible AI applications and MCP clients.

The MCP server lets authorized users query the same SiteTrax.io projects and operational information that their SiteTrax.io account is permitted to access. This can include asset observations, project activity, operational metrics, exceptions, images, video metadata, equipment movement history, camera health, and other SiteTrax.io Intelligence capabilities.

SiteTrax.io remains the system of record. The MCP server provides controlled access to SiteTrax.io data and capabilities based on the authenticated user's permissions.

MCP Server Endpoint

Use the following remote MCP endpoint:

https://mcp.sitetrax.io/mcp

The SiteTrax.io MCP server uses HTTPS and is designed for remote MCP clients that support Streamable HTTP.

Requirements

To connect to the SiteTrax.io MCP server, you need:

• An active SiteTrax.io account.

• Access to at least one SiteTrax.io project, site, or yard.

• An MCP-compatible client that supports remote HTTPS MCP servers.

• OAuth authentication support in the MCP client.

• Any SiteTrax.io permissions required for the data or capabilities you want to use.

Your MCP client can only access SiteTrax.io information available to your authenticated SiteTrax.io account.

Connect to SiteTrax.io

The exact setup interface depends on the MCP client you use.

In most compatible clients:

1. Open the application's MCP, integrations, connectors, or tools settings.

2. Add a new remote MCP server.

3. Enter the SiteTrax.io MCP endpoint:

   https://mcp.sitetrax.io/mcp

4. Start the connection.

5. When prompted, sign in to SiteTrax.io.

6. Review the requested SiteTrax.io permissions.

7. Authorize the connection.

8. Return to your MCP client.

9. Confirm that SiteTrax.io tools are available.

No SiteTrax.io password should be entered directly into the MCP configuration. Authentication is completed through the SiteTrax.io OAuth authorization process.

Authentication and Permissions

SiteTrax.io uses OAuth-based authorization for protected MCP capabilities.

Permissions are scope-based. The tools available to an MCP client depend on the scopes approved for that connection.

Read Access

Standard operational queries use SiteTrax.io read access.

Read access can include:

• Projects and sites shared with the user.

• Asset observations.

• Container, chassis, trailer, and other supported asset identifiers.

• Project activity.

• Asset history.

• Operational aggregates.

• Status and exception information.

• Camera and processing health.

• Detection images and available media metadata.

• SiteTrax.io product and operational reference information.

Read access does not grant access to SiteTrax.io projects that have not been shared with the authenticated user.

Additional Capabilities

Some MCP integrations can support additional SiteTrax.io capabilities, such as notifications or scheduled digests.

These capabilities require separate permissions. For example, notification-management operations require the applicable notification write scope.

Grant additional permissions only when the MCP client and intended workflow require them.

What You Can Ask

The SiteTrax.io MCP server supports natural-language interaction with SiteTrax.io operational data.

Examples include:

Find an Asset

Prompt

Where was container SITU 123456 7 last observed?

Result

SiteTrax.io can return the most recent authorized observation of that asset, including available project, time, capture, and operational metadata.

Review Site Activity

Prompt

Summarize activity at my SiteTrax.io sites for the last seven days.

Result

SiteTrax.io can calculate activity across the projects available to your account and return operational totals and trends for the requested period.

Analyze Asset Types

Prompt

Show today's SiteTrax.io detections by asset type.

Result

SiteTrax.io can provide server-calculated totals and breakdowns for the requested sites and time period.

Review Processing Status

Prompt

Break down today's detections by status code and asset type.

Result

SiteTrax.io can return processing results grouped by status and asset type so that the results can be interpreted correctly.

Find Exceptions

Prompt

Show me records that may require review today.

Result

SiteTrax.io can retrieve records that meet the applicable review criteria for projects available to the user.

Check Operational Health

Prompt

Were there any unusual volume gaps at my sites this week?

Result

SiteTrax.io can analyze authorized site activity and identify potential low-volume periods, repeated observations, or other operational anomalies supported by the available data.

Analyze Equipment Movement

Prompt

What was the observed time between gate-in and gate-out for trailers this week?

Result

Where the site configuration and available observations support the calculation, SiteTrax.io can perform server-side sequence and duration analysis using defined operational boundaries.

Available Capability Groups

The tools exposed to a specific MCP client vary with the scopes approved for that connection and with what the client supports. Read capabilities use sitetrax:read. Notification and digest capabilities require sitetrax:notifications:write and must be approved separately.

Capability group	What you can ask for	Scope required	Read-only
Projects and sites	Projects available to your account, project detail and configuration, recent activity, cameras and gate configuration, activity compared across projects	sitetrax:read	Yes
Assets	Asset observation search, the latest observation for an identifier, detailed asset records, asset history, detection images, video metadata, filtering by project, camera, type, status, identifier or time	sitetrax:read	Yes
Analytics	Observation counts, distinct asset totals, grouping by project, camera, type, status or time period, sequence analysis, observed durations between defined operational boundaries, activity trends, potential anomalies	sitetrax:read	Yes
Review and exceptions	Processing status review, records matching defined review criteria, unreadable or unusual results, supplied-list exceptions, exact asset records when more context is needed	sitetrax:read	Yes
Video	Video search and individual video detail records	sitetrax:read	Yes
Camera and processing health	Camera activity and scan health across the projects available to your account	sitetrax:read	Yes
Reference information	Supported capture methods, SiteTrax.io data fields, asset types, processing status codes, terminology, operational metric definitions and product capabilities	sitetrax:read	Yes
Notifications and digests	Creating, listing and cancelling alerts, and creating recurring email digests	sitetrax:notifications:write	No

SiteTrax.io performs analytical reductions on the server. MCP clients do not need to download large raw datasets to calculate supported SiteTrax.io metrics.

A processing status is not automatically a physical-condition or operational exception. The asset type, status code and operational context must be interpreted together.

Grant sitetrax:notifications:write only when the client and the intended workflow require it. Integrations that expose SiteTrax.io through a read-only surface, including the Microsoft 365 Copilot connector, do not receive it.

Supported Capture Data

Depending on a customer's SiteTrax.io configuration, operational data can include information generated through SiteTrax.io capture methods such as:

• SiteTrax Mobile

• SiteTrax Snap

• SiteTrax Gate

• SiteTrax Drive

• Other supported camera-based capture configurations

Detected or processed identifiers can include supported equipment and operational identifiers such as:

• Intermodal container IDs

• Chassis IDs

• Trailer IDs

• USDOT numbers

• License plate information where supported by the configured solution

• Other configured OCR or operational outputs

Available metadata can include timestamps, project information, camera information, location data, status information, images, direction, and asset relationships.

Images and Media

Some SiteTrax.io records include links to detection images or video-related metadata.

Media availability depends on:

• The SiteTrax.io project configuration.

• The authenticated user's access.

• Record retention.

• Redaction settings.

• The type of capture.

If a record is configured as redacted, the MCP server can withhold media while still returning permitted operational metadata.

Data Access and Security

The SiteTrax.io MCP server uses the permissions of the authenticated SiteTrax.io user.

Connecting an MCP client does not automatically give that client access to every SiteTrax.io customer, project, or site.

Users can only query information made available to their SiteTrax.io account.

Remote MCP traffic uses HTTPS.

OAuth access tokens are used to authorize protected requests. Do not place access tokens, passwords, or secrets into prompts.

Data Accuracy and Interpretation

SiteTrax.io returns operational observations and processing results.

Not every stored result should be interpreted as a verified physical event without considering its type and processing status.

For example:

• A status can describe an OCR or validation outcome.

• Some records can represent structural or synthetic pairing results.

• A USDOT number identifies a registered motor carrier and does not uniquely identify an individual tractor.

• An unreadable asset result does not by itself prove that the physical asset is damaged.

• Timing between camera observations establishes an observed interval between defined boundaries. It does not automatically establish the cause of that interval.

When operational decisions depend on a result, use the supporting SiteTrax.io record and available evidence.

Troubleshooting

Symptom	Likely cause	What to do
The MCP client cannot connect	The client does not support remote HTTPS MCP servers, or a network control is blocking the endpoint	Confirm the endpoint is https://mcp.sitetrax.io/mcp, that the client supports remote HTTPS MCP servers and OAuth, and that no network or security control blocks the connection
Authentication never starts	The client only supports local stdio MCP servers	A stdio-only client cannot reach a remote endpoint. Use a client that supports remote MCP servers with OAuth
Authentication succeeds but no projects appear	The signed-in account has no shared projects, or a different account was used	Confirm you signed in with the intended SiteTrax.io account and that at least one project is shared with it. This is a sharing question rather than an authentication one
A tool reports that another OAuth scope is required	The operation needs sitetrax:notifications:write	Reconnect the integration and approve the additional permission only if that capability is required for your workflow
An asset cannot be found	Incomplete identifier, the wrong time window, or the project is not shared with your account	Use the complete identifier, check its spelling, widen the time period, name the project or site, and confirm your account can reach that project
Results are too broad	The prompt carries no operational context	Add the project or site, a date or time range, the asset type, the camera, the status, or the exact equipment identifier
An image or video is not available	Project configuration, record retention, user permissions, or redaction	Media can be withheld while permitted operational metadata is still returned. The absence of media does not mean the underlying record is unavailable

Recommended Prompting

For better results:

• Name SiteTrax.io in the prompt.

• Identify the site or project when possible.

• Give a specific date or time range.

• Specify the type of asset.

• Use the exact equipment identifier when searching for one asset.

• Ask for a breakdown when comparing activity.

• Ask for supporting observations when a result will be used operationally.

Example:

Using SiteTrax.io, summarize container and chassis activity at the Utah site for the last seven days and break the results down by status code and asset type.

Known Issues and Limitations

• Access is limited to the SiteTrax.io projects shared with the authenticated account. Connecting an MCP client does not widen SiteTrax.io permissions.

• The server exposes MCP tools and resources. MCP prompts are not exposed.

• The endpoint is remote. A client that only supports local stdio MCP servers cannot connect to it.

• Communication uses Streamable HTTP. Server-Sent Events transport is not supported.

• Detection images and video can be withheld by project configuration, record retention, user permissions or redaction, while permitted operational metadata is still returned.

• An asset record is one stored processing result. It is not necessarily one physical asset or one direct observation, and combined container and chassis processing can add synthetic pair-side rows.

• Sequence and duration results depend on camera placement and on observations that can be paired reliably. Where a required pairing is not available, SiteTrax.io reports the limitation rather than estimating a value.

• Tool names, arguments and response shapes can change between server versions. Ask SiteTrax.io for its current schema rather than assuming a fixed contract.

Support

For SiteTrax.io MCP assistance, contact:

support@sitetrax.io

When reporting a problem, include:

• The MCP client you are using.

• The approximate time of the issue.

• The SiteTrax.io account email.

• The project or site involved.

• The prompt or operation you attempted.

• The error message, if one was shown.

Do not send passwords, OAuth tokens, client secrets, or other credentials by email.

Privacy Policy

https://sitetrax.io/privacy-policy/

Terms of Service

https://sitetrax.io/tos/

About Model Context Protocol

Model Context Protocol is an open protocol that enables AI applications to connect to external tools and data sources.

Remote MCP servers can use Streamable HTTP for communication and OAuth-based authorization for protected resources.

SiteTrax.io implements MCP to make authorized physical-operations data available to compatible AI applications while retaining SiteTrax.io as the source system.

Connect SiteTrax.io to Microsoft 365 Copilot

Use the SiteTrax.io connector to bring live SiteTrax.io operational intelligence into Microsoft 365 Copilot.

Availability. The SiteTrax.io Federated Copilot Connector is in submission to Microsoft and is not yet listed in the Copilot connectors gallery. This page documents how the connector works and how it will be enabled once Microsoft publishes it. Until then, SiteTrax.io operational data is available through any MCP client that supports remote HTTPS servers with OAuth, using the endpoint https://mcp.sitetrax.io/mcp. See the SiteTrax.io MCP Server page for that path.

Overview

The SiteTrax.io Microsoft 365 Copilot Connector lets authorized users query SiteTrax.io operational data directly from Microsoft 365 Copilot.

SiteTrax.io is implemented as a Microsoft Federated Copilot Connector using Model Context Protocol (MCP).

Unlike a synced connector, the SiteTrax.io federated connector does not copy or index SiteTrax.io operational data into Microsoft 365. When Copilot needs SiteTrax.io information, it requests the authorized information from SiteTrax.io in real time.

Access remains tied to the user's SiteTrax.io permissions.

What You Can Do

After SiteTrax.io is connected, users can ask Microsoft 365 Copilot questions such as:

What SiteTrax.io sites do I have access to?

Summarize SiteTrax.io asset activity for the last seven days.

Where was container SITU 123456 7 last observed?

Show today's detections at the Utah site by status code and asset type.

Which SiteTrax.io records may require review today?

Were there any unusual volume gaps across my sites this week?

Compare SiteTrax.io activity this week with last week.

Copilot can use SiteTrax.io to retrieve and summarize authorized operational information without requiring the user to manually navigate through individual SiteTrax.io records.

Requirements

Before using the SiteTrax.io connector, you need:

• An active SiteTrax.io account.

• Access to at least one SiteTrax.io project, yard, facility, or site.

• A work or school Microsoft account in an organization where the SiteTrax.io connector has been enabled.

• A Microsoft 365 Copilot license that supports federated connectors.

• Permission from your Microsoft 365 administrator to use the SiteTrax.io connector.

Your Microsoft 365 administrator controls whether SiteTrax.io is available in your organization.

Your SiteTrax.io account controls which SiteTrax.io data you can access.

For Microsoft 365 Administrators

SiteTrax.io must be enabled for your Microsoft 365 organization before users can access it through Copilot.

Enable SiteTrax.io

Sign in to the Microsoft 365 admin center with an account that has the required Microsoft 365 administrative permissions.

Go to:

Copilot connectors → Connectors gallery

Find SiteTrax.io in the connectors gallery.

Review the connector information, including:

• Publisher

• Connector description

• Permissions

• Privacy policy

• Terms

• Support information

Approve or enable SiteTrax.io for the appropriate users or groups in your organization.

Microsoft can make connectors available through a staged rollout before organization-wide deployment. Your Microsoft 365 administrator determines who can use the connector.

If SiteTrax.io does not appear in the gallery, confirm that:

• The connector is available to your Microsoft 365 tenant.

• Federated connectors are enabled for your organization.

• Your administrator has the appropriate Microsoft 365 role.

• Any Microsoft release or tenant restrictions have been satisfied.

Changes to connector availability can require time to propagate through Microsoft 365.

Enabled connectors are managed under Copilot connectors → Your connections. To pilot SiteTrax.io with a limited group before a wider release, use Add staging and target a Microsoft Entra ID group. The Staged Rollout column shows which connectors are currently staged. Third-party federated connectors are a preview capability, so labels and placement can change.

For SiteTrax.io Users

After your administrator enables SiteTrax.io, you must connect your own SiteTrax.io account.

The SiteTrax.io federated connector uses user-level authentication. It does not use one shared SiteTrax.io account for the entire Microsoft 365 organization.

Connect Your Account

Open Microsoft 365 Copilot with your work or school account.

When Copilot asks to connect to SiteTrax.io, select the option to connect or sign in.

You will be redirected to the SiteTrax.io authorization process.

1. Sign in to your SiteTrax.io account.

2. Review the SiteTrax.io access requested for Microsoft Copilot.

3. Approve the connection.

4. Return to Microsoft 365 Copilot.

After authorization, Copilot can use the SiteTrax.io connector when your prompt requires SiteTrax.io information.

You do not need to provide your SiteTrax.io password to Microsoft Copilot.

Read-Only Copilot Access

The SiteTrax.io Federated Copilot Connector is read-only.

Microsoft enables only MCP tools that carry the read-only annotation, so the connector surfaces SiteTrax.io search and retrieval capabilities and nothing else. Write capabilities are additionally gated behind the separate sitetrax:notifications:write scope, which is not granted to the Copilot connection.

The Copilot connector does not expose SiteTrax.io tools that:

• Create operational records.

• Modify SiteTrax.io data.

• Create notification automations.

• Cancel notification automations.

• Create recurring digest automations.

• Perform other cross-service write actions.

Microsoft Copilot can query authorized SiteTrax.io information, but the federated connector cannot use the connector to modify SiteTrax.io or create external automations.

This restriction is enforced by SiteTrax.io authorization in addition to the MCP tool configuration used by the Microsoft connector.

What Data Can Copilot Access?

Copilot can only access SiteTrax.io data that the signed-in SiteTrax.io user is authorized to access.

Depending on the customer's configuration, this can include:

Projects and Sites

• Sites

• Yards

• Facilities

• Projects

• Cameras

• Project activity

Asset Observations

• Intermodal container IDs

• Chassis IDs

• Trailer IDs

• USDOT numbers

• Other supported operational identifiers

• Observation timestamps

• Site and project information

• Camera information

• Direction information

• Processing status

• Available capture metadata

Operational Intelligence

• Activity totals

• Distinct asset counts

• Trends

• Status breakdowns

• Asset-type breakdowns

• Site comparisons

• Camera activity

• Potential anomalies

• Review candidates

• Observed asset movement history

• Supported sequence and duration metrics

Supporting Evidence

Where permitted and available:

• Detection images

• Thumbnail information

• Capture metadata

• Asset record details

Project redaction policies and SiteTrax.io permissions continue to apply.

SiteTrax.io Data Stays in SiteTrax.io

SiteTrax.io uses Microsoft's federated connector architecture.

SiteTrax.io operational data is requested from SiteTrax.io in real time when Copilot needs it.

The connector does not operate as a Microsoft 365 synced connector and does not create a separate Microsoft 365 index of SiteTrax.io operational records.

SiteTrax.io remains the source system.

Permissions

There are two separate levels of access.

Microsoft 365 Access

Your Microsoft 365 administrator determines whether the SiteTrax.io connector is available to you.

SiteTrax.io Access

Your SiteTrax.io account determines which projects and operational data you can access.

Enabling the connector in Microsoft 365 does not grant additional SiteTrax.io project permissions.

For example, if your SiteTrax.io account can access three projects, Copilot can query those authorized projects. It cannot use the connector to access another customer's projects or a SiteTrax.io project that has not been shared with you.

Using SiteTrax.io in Copilot

Be specific when asking Copilot to use SiteTrax.io.

Name the Source

Instead of:

What happened today?

Use:

Using SiteTrax.io, summarize activity at the Utah site today.

Include a Time Period

Instead of:

Show container activity.

Use:

Show SiteTrax.io container activity for the last seven days.

Identify the Facility

Instead of:

How many assets were scanned?

Use:

Using SiteTrax.io, show asset activity at the Norfolk yard yesterday.

Identify the Asset

For an individual asset, use the complete identifier:

Where was SITU 123456 7 last observed in SiteTrax.io?

Ask for a Breakdown

Using SiteTrax.io, break today's detections down by asset type and processing status.

Ask for Comparisons

Compare SiteTrax.io activity at my sites this week with last week.

Example Workflows

Morning Operations Review

Using SiteTrax.io, summarize activity across my sites since yesterday morning. Identify unusual volume changes and records that may require review.

Asset Lookup

Find the latest SiteTrax.io observation for SITU 123456 7 and tell me where and when it was observed.

Site Performance

Using SiteTrax.io, show daily asset activity at the Utah site for the last seven days.

Exception Review

Using SiteTrax.io, show today's results by status code and asset type and identify the categories I should investigate.

Camera Health

Using SiteTrax.io, summarize camera activity and scan health for my sites today.

Equipment Flow

Using SiteTrax.io, analyze observed trailer movement between the configured inbound and outbound gates this week.

Troubleshooting

Symptom	Likely cause	What to do
SiteTrax.io does not appear in Microsoft 365 Copilot	Your organization has not enabled the connector, or it is staged to a group you are not in	Ask your Microsoft 365 administrator whether the SiteTrax.io connector is enabled for your account or group. Availability is controlled by your organization, not by SiteTrax.io
SiteTrax.io appears but the connection fails	SiteTrax.io sign-in, the browser, or an organizational security control is blocking the authorization flow	Confirm you have an active SiteTrax.io account and can sign in normally, that your browser permits the authorization redirect, and that your organization allows the connection. If it persists, contact SiteTrax.io support
Copilot says you need to authenticate	First use, expired authorization, revoked access, or a changed connector configuration	Complete the SiteTrax.io OAuth sign-in. No SiteTrax.io password is given to Microsoft
Copilot cannot find a project	The project is not shared with your SiteTrax.io account	Sign in to SiteTrax.io and confirm the project is shared with you. Microsoft Copilot cannot widen your SiteTrax.io permissions
Copilot cannot find an asset	A partial identifier, or the prompt did not name SiteTrax.io	Use the complete identifier and name SiteTrax.io in the prompt. Add the site or an approximate observation date if needed
Two users see different results	Expected. SiteTrax.io access is scoped per user	Nothing to fix. Two users with different SiteTrax.io project permissions correctly receive different answers
Copilot cannot create an alert or change SiteTrax.io data	Expected. The connector is read-only	Write and automation capabilities require the sitetrax:notifications:write scope, which the Copilot connection does not receive. Use the SiteTrax.io Service Portal or another MCP client for those operations
Results need more context	The prompt is too broad for the data available	Specify the site or project, a date range, the asset type, the identifier, the camera, the status, or the comparison you want

Disconnecting or Revoking Access

Your organization can disable the SiteTrax.io connector through Microsoft 365 connector administration.

Users or administrators can also revoke the applicable authorization according to the SiteTrax.io and Microsoft 365 account controls available to them.

After authorization is revoked, Microsoft Copilot can no longer retrieve protected SiteTrax.io data through that connection.

Known Issues and Limitations

• The connector is in submission to Microsoft and is not yet listed in the Copilot connectors gallery. Third-party federated connectors are a preview capability.

• The connector is read-only. Microsoft enables only MCP tools carrying the read-only annotation, and the SiteTrax.io write scope is not granted to the Copilot connection. Creating alerts, cancelling alerts and creating recurring digests are not available through Copilot.

• Availability is controlled by your Microsoft 365 administrator and can be staged to selected Microsoft Entra ID groups. Changes to connector availability can take time to propagate through Microsoft 365.

• Access is limited to the SiteTrax.io projects shared with the signed-in account. Enabling the connector grants no additional SiteTrax.io permission.

• Each user authorizes individually. There is no shared organizational SiteTrax.io login, so two users can correctly receive different answers to the same prompt.

• Detection images and video can be withheld by project configuration, record retention, user permissions or redaction, while permitted operational metadata is still returned.

• An asset record is one stored processing result. It is not necessarily one physical asset or one direct observation, and combined container and chassis processing can add synthetic pair-side rows.

• Sequence and duration results depend on camera placement and on observations that can be paired reliably. Where a required pairing is unavailable, SiteTrax.io reports the limitation rather than estimating a value.

• A Microsoft 365 Copilot licence that covers federated connectors is required. The surfaces and regions where approved federated connectors appear are determined by Microsoft and can vary by tenant and rollout ring.

Security and Privacy

SiteTrax.io access through Microsoft Copilot follows the authenticated user's SiteTrax.io permissions.

Do not include passwords, OAuth tokens, secrets, or other authentication credentials in Copilot prompts.

For information about how SiteTrax.io handles data, see:

SiteTrax.io Privacy Policy

https://sitetrax.io/privacy-policy/

SiteTrax.io Terms of Service

https://sitetrax.io/tos/

Support

For problems with your SiteTrax.io account, SiteTrax.io permissions, SiteTrax.io data, or the SiteTrax.io connector, contact:

support@sitetrax.io

When contacting support, include:

• Your SiteTrax.io account email.

• Your Microsoft 365 organization, if relevant.

• The site or project involved.

• The approximate time of the problem.

• The prompt you attempted.

• The error message shown by Copilot.

Do not include passwords, access tokens, OAuth secrets, or other credentials.

For Microsoft 365 tenant configuration or connector availability, contact your organization's Microsoft 365 administrator.

Frequently Asked Questions

Does SiteTrax.io copy my operational data into Microsoft 365?

The SiteTrax.io connector is a federated connector. Copilot requests authorized information from SiteTrax.io when it is needed rather than using a synchronized Microsoft 365 index of SiteTrax.io operational data.

Can Copilot see every SiteTrax.io customer?

No.

Copilot can only retrieve data available to the authenticated SiteTrax.io user.

Does enabling SiteTrax.io give a user additional SiteTrax.io permissions?

No.

SiteTrax.io project permissions remain authoritative.

Can Microsoft Copilot modify SiteTrax.io through this connector?

No.

Microsoft enables only read-only MCP tools in a federated connector, and the write scope is not granted to the Copilot connection.

Can Copilot create SiteTrax.io notifications or scheduled email digests?

Not through the Federated Copilot Connector.

Those capabilities require the SiteTrax.io write scope, which the connector does not receive.

Do users share one SiteTrax.io login?

No.

Federated SiteTrax.io access is authenticated at the user level.

Does a Microsoft administrator have to enable SiteTrax.io?

Yes.

The SiteTrax.io connector must be available and enabled for the user's organization before it can be used.

What Microsoft license is required?

Users querying federated data sources must have an applicable Microsoft 365 Copilot license.

Where can SiteTrax.io be used?

Microsoft can surface approved federated connectors in Microsoft 365 Copilot experiences supported by the connector platform. Availability can vary by Microsoft product, tenant configuration, and rollout.

Related SiteTrax.io Documentation

SiteTrax.io Documentation

https://docs.sitetrax.io

SiteTrax.io MCP Server

https://mcp.sitetrax.io/mcp

Privacy Policy

https://sitetrax.io/privacy-policy/

Terms of Service

https://sitetrax.io/tos/

Support

support@sitetrax.io