Supported AI Platforms
Choose an assistant or agent platform your organization approves, then use that provider’s dedicated documentation section. Each section owns its connection status, setup instructions, platform limits and vendor references.
What every connection must support
- Remote HTTPS access to
https://mcp.sitetrax.io/mcp. - Streamable HTTP transport and SiteTrax.io OAuth authorization.
- The tools and permissions required for your intended task.
A provider’s MCP support alone does not establish that its connection to SiteTrax.io has been validated. A directory listing or setup button also does not prove a completed connection.
How to read availability
| Status | Meaning | Next step |
|---|---|---|
| Documented connection | A SiteTrax.io setup route is published. | Follow the provider guide and verify your account’s project access. |
| Validation required | A technical route exists but SiteTrax.io end-to-end behavior has not been established. | Coordinate a scoped pilot before relying on it. |
| Pending release | The provider-specific guide reports a release or listing dependency. | Use that section for availability and next steps. |
| Custom implementation | A business workflow needs design, configuration and acceptance. | Agree scope, hosting, permissions and support. |
Verify the first result
Using SiteTrax.io, list the projects I can access. Do not create or change anything.
Compare the result with the same account in the application, then query a known observation and open its record. Read access and notification-write permission are separate. Connecting an assistant does not expand project access.
Use the provider sections in this book for setup. For the shared technical contract, see MCP Server.
No comments to display
No comments to display