Sanctris MCP integration
Sanctris exposes a remote MCP server over Streamable HTTP. It is not a local stdio server or a legacy SSE URL.
Endpoints
| Purpose | Main-origin URL |
|---|---|
| MCP | https://app.sanctris.com/mcp |
| Protected resource discovery | https://app.sanctris.com/.well-known/oauth-protected-resource/mcp |
| Authorization metadata | https://app.sanctris.com/.well-known/oauth-authorization-server |
| Dynamic client registration | https://app.sanctris.com/oauth/register |
| Authorization | https://app.sanctris.com/oauth/authorize |
| Token exchange and refresh | https://app.sanctris.com/oauth/token |
Tenant-origin endpoints use the same paths under https://WORKSPACE.t.sanctris.com. Prefer OAuth discovery instead of hard-coding all endpoints.
Authentication
The implemented flow is OAuth authorization code with PKCE S256 and dynamic client registration. Public clients use token endpoint authentication method none. Supported grants are authorization_code and refresh_token. A configured connection represents the authenticated workspace user.
Discover the metadata, register the exact redirect URI, generate PKCE and client-side state, open authorization in the browser, then exchange the code with the verifier. Set the MCP resource to the exact endpoint. Never send the user's password through an AI tool.
Refresh credentials belong in the client's secure credential store, not a shared JSON file. Revoke a connection from the product's AI workspace to stop future access.
Scopes and toolsets
sanctris: read/write access, subject to roles and the chosen purpose.sanctris:read,sanctris:write: access restrictions.sanctris:design,sanctris:analytics,sanctris:admin: purpose selectors; these do not grant access by themselves.- Without a purpose marker, the daily toolset is selected.
Inspect tools/list after authentication. Never rely on a globally fixed tool count.
Protocol compatibility
The server uses the TypeScript MCP SDK v2 handler with the 2026-07-28 protocol path and stateless legacy negotiation for 2025-era clients. Actual wire version depends on the client; this is not a certification of every client or optional protocol feature.
MCP Apps interfaces are optional. Hosts without rendering support should follow returned browser links.
Write operations
Use the human confirmation flow. Approval automatically executes stored input. Retrieve the outcome using execute_approved_operation({ "operation_id": "ID_FROM_FIRST_RESULT" }). Do not copy long confirmation tokens, mutate parameters on retry, or report success from an HTTP 200 alone: inspect MCP isError and tool content.